Register all active platform services and base features in core DB so admin can manage them, add delivery/hospitality/sports-center backend phases, update apps catalog and production deploy tooling. Co-authored-by: Cursor <cursoragent@cursor.com>
1.4 KiB
1.4 KiB
Phase 12.6 — Kitchen
| Field | Value |
|---|---|
| Status | Complete |
| Module | hospitality |
| Commercial Product | Torbat Food |
| Version | 0.12.6.0 |
| Database | hospitality_db |
| API Port | 8009 |
| ADR | ADR-001, ADR-003, ADR-006, ADR-017 |
| Prior phase | 12.5 POS Pro |
Goal
Add a kitchen display / ticket routing shell consuming POS tickets and QR ordering sessions by
reference only (source_type + source_id UUID) — no direct writes into POS/QR aggregates.
Scope (In)
- Aggregates: KitchenStation, KitchenTicket, KitchenTicketItem
- APIs under
/api/v1/kitchen-stations|kitchen-tickets|kitchen-ticket-items - Status transition endpoints (
/status) with terminal-state guards (bumped,cancelled) - Permissions + publish-only events
- Alembic
0007_phase_126_kitchen - Capabilities
kitchen,kitchen_engine; version0.12.6.0
Out of Scope
- Delivery / Accounting / CRM / Loyalty / Communication / Website connectors, Analytics, AI
Quality Gates
Passed (architecture, dependency, migration, tenant, API, permissions, docs). See handover.