Stage 2 · Analysis
The operator jobs behind Orders & Service searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
See one trustworthy live order queue
Bring authorized Kitchen-facing orders from active channels into one current service view.
Orders may originate from table, counter, pickup, delivery or room service, but this capability does not own those channel surfaces or payment.
Evidence: live kitchen order board · restaurant order queue system
- 2
Preserve exactly what must be prepared
Keep items, quantities, modifiers, notes, allergens, course and timing attached to the order.
The Kitchen executes the accepted order; it must not silently rewrite customer choices or Menu definitions.
Evidence: digital kitchen order tickets · kitchen display system
- 3
Route work to preparation Stations
Show each Station the lines it owns while retaining whole-order coordination.
Stations define production ownership; Orders owns the live routing instance and expo coordination.
Evidence: KDS station routing · multi station kitchen display
- 4
Prioritise timed service work
Order active tickets by fire time, commitment, age and explicit priority while surfacing delays.
Priority must remain explainable. AI must not reorder service from invented urgency.
Evidence: kitchen queue prioritization · delayed order alerts restaurant
- 5
Coordinate completion and handoff
Track line progress until the whole order is ready for its configured handoff.
Kitchen readiness is not table service, driver dispatch, payment completion or proof the customer received the order.
Evidence: kitchen expo screen · kitchen order tracking software
Record map
Evidence the capability owns, references, or derives
kitchen.orders.order
Kitchen Order
Owner: Orders
Order owns the accepted demand, immutable item snapshots, fulfilment context, pricing snapshot and lifecycle state.
- Order and service identity
- item snapshots and quantities
- fulfilment and requested timing
- pricing and payment state
- lifecycle transitions and audit stamps
kitchen.orders.routing-evidence
Order routing evidence
Owner: Stations, Recipes, Mise and Team
Queue and timing deductions compose current operational evidence without changing its owners.
- Station mapping
- Recipe and prep requirements
- Mise readiness
- authorized Team responsibility
Required record questions
What must Orders & Service make knowable?
- Which Kitchen, service period, source channel and order identity apply?
- Which items, quantities, modifiers, notes and safety information must remain intact?
- Which Station owns each line and which dependencies govern whole-order readiness?
- When was the order accepted, fired, started, completed, ready, handed off or cancelled?
- Why does the queue place one order before another?
- Which actor or trusted integration changed each state?
- Which timestamps can support later performance analysis without rewriting the Order?