Tablekeeper: A Restaurant Booking Factory

Tablekeeper brings two things together: a restaurant reservation service and a reusable team of coding agents that built it. The team worked in one BAND room, with an Engineering Lead, Backend Engineer, Frontend Engineer and QA Engineer. Each seat had a generic mandate. Product requirements lived in the task, while the mandates defined ownership, handoffs and verification. Engineers handed over committed changes, QA checked them independently, and failures went back to their owners for repair. The application covers the booking journey from finding an available table to confirming, retrieving and cancelling a reservation. Later stages add table combinations, effective-dated policies, recurring visits and seating recovery. Managers can preview proposed seating changes before applying them together. The interface supports light and dark themes, responsive layouts and feedback beside the action that needs attention. All four stages are included as separate, buildable services. Fresh-clone container checks passed, and the final stage passed 158 shipped checks. The repository preserves the room export, original Git history, failure evidence and independent verification reports. The shipped tests are partial, so these results do not guarantee hidden-test coverage. The service uses local SQLite, and state is temporary across container restarts unless exported and imported.