Tablekeeper is a restaurant reservation service produced through ProofForge, our autonomous software factory built in BAND Desktop. ProofForge treats software delivery as an evidence-gated process rather than a single coding session: specialized seats plan, implement, test, review, reject, repair, and verify work against the specification, with handoffs and Git-backed revisions. ProofForge is designed to be reusable beyond Tablekeeper. Its mandates define how seats work, communicate, hand off evidence, challenge results, and recover from defects without encoding track-specific endpoints, fields, or error codes. A specification is decomposed into requirements, implementation is divided into owned work, tests are derived from requirements, and independent reviewers inspect revisions rather than trusting the builder's claims. The factory is evidence-driven. Reviewers inspect exact revisions, exercise failure cases that shipped checks may miss, and reject work when implementation violates the specification. Defects are routed back for repair and re-verification, leaving a trace across room history, commits, tests, and accepted revisions. Failure recovery is part of the engineering process, not something hidden behind a polished demo. The resulting Tablekeeper service addresses difficult reservation requirements including availability, booking, amendments, cancellation, concurrency, retries, state handling, and time-zone behavior. The submission contains the application and factory artifacts needed to inspect how the work was planned, implemented, challenged, repaired, and verified. Our submission demonstrates two connected deliverables: the software factory and the software it produces. The repository, mandates, room history, Git history, tests, and verification artifacts provide an inspectable trail from specification to independent acceptance. The goal is to demonstrate a repeatable system in which autonomous seats produce, challenge, repair, and verify software.
Category tags: