Four-Seat Dark Factory — tablekeeper

Our factory is four Claude Code seats in one BAND Desktop room, each with a generic mandate that names no endpoint, field or error code. - foreman routes the work, sends self-contained handoffs and accepts only commits the verifier checked from a clean clone. - auditor reads the spec independently, writes a numbered requirements ledger, flags what the shipped checks don't exercise, and writes its own API and browser acceptance tests from the spec alone. - builder is the only seat that writes product code; it copies each stage forward and extends it. - verifier clean-clones every revision, builds it with no network, runs every suite plus the auditor's tests and its own probes (concurrency, retries, DST, limits, 320 px screens), then answers ACCEPT or REJECT with evidence. The shipped checks cover only 83/41/11/21% of the graded suites, so the factory builds to the written spec. In the submitted dark run it reached all four stages in 2 h 28 m with no blockers. Stage 4 ends with 218/218 API and 39/39 browser acceptance tests passing, the replan planner matching brute force on 1,800 random cases, and no 5xx under 50 concurrent requests. Review changed the work twice, both beyond the shipped checks: the verifier rejected a stage-3 revision that labelled a policy-closed day "no times left" instead of "closed", and the auditor rejected a stage-4 revision, which the verifier had accepted, where one unchanged occurrence past its cutoff blocked a whole recurring-reservation change. Each was fixed in one round and left a regression test. Git history has 24 seat commits, each authored by its seat, and room.json holds the full collaboration. Point the same mandates at a different spec and the same band works.