
Tablekeeper is a restaurant reservation service built entirely by an autonomous software factory: five Claude Code seats working together in one Band Desktop room. A coordinator plans, routes work and issues rulings; an analyst turns each specification into a requirements ledger; a builder implements; builder-2 reviews or builds in parallel; and an independent verifier writes and seals its own spec-derived acceptance suite before seeing any code. The judged run started from a single human message, the dispatch. With no further human input, the factory processed four evolving stages: a JSON booking API, a browser UI with combined tables and recovery, policies and recurring reservations, and seating changes. Every TASK and VERIFY handoff carried the full stage specification. Review changed the work. builder-2 raised spec-cited disputes, the coordinator issued binding rulings, and the verifier caught two real implementation defects that violated them. Each went back as a FIX, was re-reviewed and re-verified from a clean checkout, and only then was the stage accepted. All four stages were accepted in 121 minutes: 70 seat-authored commits, 18 rulings, 311 independent checks in the final round, about 82 USD of model spend. The official harness claims stages 1 to 4 in isolated mode from a fresh clone.
6 Oct 2026