5c6a2e78cf
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>
50 lines
1.2 KiB
Markdown
50 lines
1.2 KiB
Markdown
# Phase Handover — 12.6 Kitchen
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Phase ID | hospitality-12.6 |
|
|
| Title | Kitchen |
|
|
| Status | Complete |
|
|
| Service(s) | hospitality |
|
|
| Version | 0.12.6.0 |
|
|
| Date | 2026-07-26 |
|
|
| ADR(s) | ADR-017 (no new ADR) |
|
|
|
|
## Summary
|
|
|
|
Kitchen display / ticket routing shell on `hospitality_db`. Tickets reference their POS ticket or
|
|
QR ordering session source by UUID only — no cross-aggregate relationships.
|
|
|
|
## Public APIs
|
|
|
|
| Method | Path |
|
|
| --- | --- |
|
|
| CRUD/list | `/api/v1/kitchen-stations` |
|
|
| CRUD/list + status | `/api/v1/kitchen-tickets`, `/{id}/status` |
|
|
| CRUD/list + status | `/api/v1/kitchen-ticket-items`, `/{id}/status` |
|
|
|
|
## Events
|
|
|
|
`hospitality.kitchen_station.created`, `kitchen_ticket.created|status_changed`,
|
|
`kitchen_ticket_item.added`
|
|
|
|
## Migration
|
|
|
|
`0007_phase_126_kitchen` (additive)
|
|
|
|
## Known Limitations
|
|
|
|
- No real KDS vendor integration
|
|
- No automatic routing from POS/QR ordering — kitchen tickets created explicitly by reference
|
|
- No connector integrations yet
|
|
|
|
## Next Phase Entry
|
|
|
|
Phase **12.7 — Delivery / Accounting / CRM / Loyalty / Communication / Website Connectors**
|
|
|
|
## Service Snapshot
|
|
|
|
Regenerated: `docs/service-snapshots/hospitality.yaml`
|