Tablekeeper is a restaurant reservation service produced by the Proofline factory in BAND. Three distinct coding seats divide responsibility: the Coordinator transports the complete assignment, the Builder implements and preserves each stage, and the Verifier checks the exact revision independently. The four services extend the contract in order: atomic and idempotent API operations, a browser booking workflow, effective-dated policies and recurring reservations, and atomic series changes and closure replanning. Each stage includes its own Dockerfile and run instructions. The application needs no external model at runtime. Independent clean-clone public checks accepted all four stage claims at revision 96ab4b8. A substantive review caught a tampered imported closure plan that could violate booking consistency. The Builder repaired validation; the independent recheck confirmed rejection without changing the destination. The original room, generic mandates and exact-revision reports preserve the collaboration. Operator recovery occurred between stages and during stage four, including one administrative notice. The supervisor made no production-code edits or repeated stage dispatches. This intervention is disclosed; uninterrupted autonomy is not claimed. Public checks are partial, and private evaluation and the judges’ autonomy assessment remain unknown. The video combines actual application captures with fictitious data, original BAND history and a post-completion room inspection. Editing refers to the presentation, not changes to the accepted stage source. Narration uses Google Sulafat.
Category tags: