Padayon Factory: Tablekeeper built to stage 4

Padayon is a BAND factory of five seats that built the Tablekeeper reservation system through stage 4 in one room (PADAYON RUN V6). Coordinator, core-builder and interface-builder run on Codex; tester and reviewer run on Claude Code. The only human input was one dispatch per stage: no hints, approvals, nudges or reruns. Every file under stage-*/ was written by a seat. RESULT All four stage folders claim their stage in the isolated harness (highest contiguous stage 4) from a clean container with no network, 2 CPU and 2 GiB. Factory time: 4h 49m (38m, 1h25m, 1h11m, 1h34m). WHAT WE ARE PROUDEST OF - Quality did not decay: worst function complexity is 9 at every stage, no function above 10, largest file 132 lines, 0% duplication. - The reviewer rejects with evidence. At stage 4 every test passed, yet it refused a maintainability regression (mean complexity 3.146 to 3.429). Two real refactors later it re-measured and accepted, 28m 50s on. Other rejections: fixture passwords (stage 1), seven defects in the tester's own checks (stage 2), a legacy-upgrade break (stage 3). - Independent audit: after the freeze we wrote a separate suite from the four specs. 506 checks pass on stage 4, and 3,600 random operations kept every invariant. - Honest evidence: failing and superseded checks are disclosed, not hidden. - Shared work: no seat made more than 24% of tool calls; the coordinator made 18%. - Measured cost: Band estimates $59.19 for the two Claude seats; Codex seats ran on a flat plan (about 200M tokens). - Generic mandates that name nothing from the track, plus FACTORY.md on standing the factory up for a different problem. VERIFY README.md, FACTORY.md and EVIDENCE.md in the repo map each claim to a room message id or commit. room.json is the unedited 6,570-event export.