Boopadoop: Zero Human Code
The Premise
What if literally anyone - a kid, a grandparent, someone who has never written a line of code - could describe something and have it exist? Live. Immediately. Not a template. Not a drag-and-drop builder. Just: say what you want, AI builds it, everyone sees it.
That is the question Boopadoop was built to answer.
The Real Experiment
Sidefire v2 failed because parallel agents don’t share context. Each agent built correct code in isolation. Together, they built a system no one could reason about. One million Cloudflare requests in fifteen minutes.
The lesson was precise: one spec, one agent, one session. The human holds the full picture. The agent executes from a complete document rather than a slice of an implicit contract.
Boopadoop was the first project built on that lesson. The methodology that Sidefire produced through failure, Boopadoop validated in an afternoon.
But Boopadoop is not just a methodology test. It is the most compressed version of a question Throughline is always asking: how short can the distance between “I want a thing” and “the thing exists” get?
The professional pipeline - the Throughline Interview, the prompt chain, the spec documents, the build agent - takes 15 minutes of conversation and produces a deployed application. Boopadoop compresses that entire pipeline to a single sentence. No interview. No structured intake. Just: type what you want.
Anyone can be the client. Anyone.
How It Works
A single Cloudflare Worker takes a text prompt, streams a Claude response, and deploys it as the live page. No framework. No build step. The constraint was intentional - the minimal stack forces the generated output to stand alone.
Two-tier content moderation catches problems before they go live. Rate limiting prevents abuse. Iframe sandboxing isolates user content. An admin dashboard handles monitoring.
The spec was the source of truth. The agent cold-started from the document and built to it. No existing codebase to understand, no implicit context to inherit - just a complete specification and a capable executor.
The Numbers
- Built in a single afternoon
- 13 commits in 3.5 hours
- 87 integration tests, 7 smoke tests
- CI/CD with SMS notifications
- Zero human-written application code
What We Learned
The single-agent model works where the parallel model failed because context is not divisible. A WebSocket handler and a state management hook share a contract that doesn’t live in either file. When one agent owns both, that contract is explicit. When two agents each own one, the contract is assumed - and assumptions compound.
The spec-driven approach is the same insight at a higher level. The specification makes every contract explicit before any code is written. The agent doesn’t need to understand an existing codebase because the spec already describes what needs to exist.
Boopadoop also confirmed something about the pipeline’s ceiling: the distance between “describe something” and “it exists” can get very short. The professional pipeline gets you there in 15 minutes with a structured interview. Boopadoop gets you there in one sentence. The tradeoff is depth of spec - a 15-minute interview produces a richer, more specific result than a single prompt. But for the right problem, a single prompt is enough.
The Throughline
Boopadoop is the factory in its most distilled form. Everything the methodology learned from Sidefire - the single agent, the complete spec, the human as architect - expressed in the smallest possible surface area.
It also looks like a toy. A silly little website that makes websites. The reason to build it anyway is the same reason Ford built the first moving assembly line before he knew how many cars he’d make: you build the factory to learn how the factory works. Then you build it better.
Fork the Vote is the serious version of the same question. A real client, a 15-minute voice interview, a full spec pipeline, a deployed application. Boopadoop compresses that to one sentence. The underlying question is identical: describe the thing you want. Get the thing.
Current Status
Live at boopadoop.net. The process that created it is the default approach for every project that comes after.