Factory Trio is a reusable software delivery process built from three distinct BAND coding-agent seats: Submission Lead, Final Implementer, and Final Reviewer. A human provides one complete task per stage. The lead plans and sends self-contained handoffs. The implementer writes and commits the service. The reviewer checks the exact revision against the written specification, tests failure cases and clean startup, and returns reproducible defects for repair. The lead accepts only independently reviewed commits. Our Tablekeeper entry is a restaurant reservation service tested under concurrency, retries, time zones, and partial failures. The room log records genuine rejection and repair: malformed imports could corrupt state, slow clients could block the service, and bookings could commit while returning an error. These defects were repaired and the new revisions were reviewed. The submission reaches independently accepted Stage 2. Stage 1 passed 120/120 official isolated checks; Stage 2 passed 25/25 and was exercised at 375 CSS pixels and desktop width. Both stages build and start in clean Docker containers. The public repository contains complete stage folders, generic mandates, FACTORY.md, and the full BAND room export. The video includes the actual BAND room and a service walkthrough. Stage 1 active work took about 49 minutes plus final acceptance; Stage 2 coordination took about 1 hour 35 minutes including review delivery delay. Exact token and dollar spend is unavailable in the seat runtimes. These checks provide partial evidence, not an exhaustive proof over all inputs and schedules.
Category tags: