Redline is a software factory of five BAND seats. One human message goes into the room; after that, nobody types. @Planner (Claude Opus) turns each pocketful stage into numbered requirements, putting the conservation rules first: the total of all balances never changes, no balance goes negative, and a request moves money at most once. @Redline (Claude Sonnet) writes tests for every requirement before any implementation exists, and never reads the code. @Builder (Claude Sonnet) implements one item at a time. @Adversary (Claude Sonnet) attacks each item with races, replays, rounding and stale state, and every break it finds becomes a permanent test. @Verifier (Claude Sonnet) cannot edit anything; it re-runs the gates itself and answers GO, NEEDS_WORK or BLOCK. The gates are scripts, not opinions: a clean offline build at judging limits, the spec tests, the public checks, a storm of 1,000+ concurrent operations with replays checked against the conservation invariant, earlier stages' tests plus an upgrade from populated state, a mutation gate that proves the tests catch bugs, a UI gate at three widths with an accessibility scan, and a budget governor that sends stuck work back to the planner. A scope check reads git history and blocks any commit outside its author's boundary. Results from the judged run: stages 1 and 2 of 4 pass the kickoff harness in isolated mode; 497 spec tests pass at stage 2's close; mutation score 100% at stage 1 and 70% at stage 2; 54 rejections recorded (9 adversary breaches, all fixed); about $680 list-price equivalent; 17 h 25 min wall time. The rejection ledger in FACTORY.md lists every BLOCK and NEEDS_WORK, what it caught, and the diff it forced, each linked to its room message. The same mandates, unchanged, built the toy track (100% of the toy's stage-1 suite, `proof/toy/`).
Category tags: