Spec · partners
How Loopfund actually works
Kickstarter for Gauntlet Loop compute. Stripe pot, our ledger, OpenRouter Management API key per run, Claude Code harness in a sandbox, overseer prompt plus capture tools, optional Twitch ingest, GitHub Release every critic wave.
MVP in
- Games only
- Creator submit: destination, Fable 5.1 via OpenRouter, critic bar, credentials
- Stripe Checkout into the pot, held for this loop. No creator withdrawal
- Start run: scoped VM, OpenRouter key limit = pot, Anthropic 1P pin
- Public workbench, 11-shot critic grid, GitHub Release each wave
- Empty pot pauses (disable key, sleep VM). Top-up resumes same disk
- Pro-rata unused refund
MVP out
- Creator cash-out, equity, pooling Max subs, chat interrupting the builder
- Movies/research verticals, multi-gateway beyond OpenRouter
Success bar
One hosted loop survives a provider 429 and an empty-pot pause/resume, with a public workbench and a GitHub Release episode, funded by a real Stripe test payment.
Architecture
Stripe pot → ledger → OpenRouter Management API key per run → Claude Code harness in a sandbox → overseer prompt plus capture tools → optional Twitch ingest → GitHub Release every critic wave. OpenRouter replaces the model pipe, not the harness. Pin Anthropic first-party. Empty pot disables the key and sleeps the VM.
Overseer vs harness
Overseer is the prompt (split, builder + critic, real bar). Harness is Claude Code: spawn, fresh-context critic, pixel capture, /loop. Without the machine the overseer is a speech.
