Stage 3 · Tools

Proposed Orders & Service Tools

Language specifications derived from the capability analysis. Status reflects the current Tool source.

kitchen.orders.route-order

Route Kitchen Order

compoundrequested

Project accepted order lines to their responsible preparation Stations.

Records:reads Kitchen Orderwrites Kitchen Orderreads Order routing evidence

Inputs

  • authorized Order
  • Dish-to-Station rules
  • current Station configuration

Outputs

  • traceable Station work projections and unresolved lines

Evidence

  • Order items and modifiers
  • Dish and Station relationships

Authority: Routing cannot alter the accepted commercial Order or guess an unmapped Station.

Approval: Configured deterministic routing needs no per-line approval; every override is explicit and stamped.

kitchen.orders.update-status

Update Order Status

humanrequested

Apply a valid transition to an Order or preparation line.

Records:reads Kitchen Orderwrites Kitchen Order

Inputs

  • Order identity
  • current status
  • requested transition

Outputs

  • actor-stamped lifecycle transition

Evidence

  • canonical Order lifecycle rules

Authority: A trusted command verifies Kitchen authority and the permitted transition.

Approval: The operator explicitly performs the transition unless a named trusted integration owns it.

kitchen.orders.prioritize-queue

Prioritise Kitchen Queue

ai-assistedrequested

Produce an explainable service sequence from current commitments and explicit priority.

Records:reads Kitchen Orderreads Order routing evidence

Inputs

  • active Orders
  • fire and promised times
  • explicit priority policy

Outputs

  • ordered queue with reasons, delays and unknowns

Evidence

  • authorized Order timestamps and configured policy

Authority: OrdersAI may recommend sequence but may not fabricate urgency or mutate an Order.

Approval: Read-only sequencing needs no mutation approval; manual overrides are explicit.

kitchen.orders.review-prep-times

Review Preparation Times

ai-assistedrequested

Compare supported lifecycle timing across Orders and Stations.

Records:reads Kitchen Orderreads Order routing evidence

Inputs

  • completed Order transitions
  • period
  • optional Station filter

Outputs

  • traceable duration measures and bottleneck findings

Evidence

  • recorded lifecycle timestamps only

Authority: Missing transitions remain missing and are never estimated as observed performance.

Approval: Analysis is read-only.

ordersAI

Specialist responsibility

  • Own live Order interpretation, evidence requirements and its Tool catalogue.
  • Preserve accepted order content, lifecycle rules and channel boundaries.
  • Use only authorized current service evidence and explicit priority policy.
  • Never claim ready, handed off or delivered from an earlier state.
  • Expose all current Workspace Tools as requested until trusted registration is complete.

KitchenAI

Coordinator responsibility

  • Recognise Order and service intent and delegate it to OrdersAI.
  • Pass selected Kitchen and authorized service context without copying Orders expertise.
  • Discover real Tool availability through OrdersAI registration.
  • Present queue reasoning and preserve authority for every state mutation.

Activation gate

  • Trusted Workspace readers expose the canonical live queue.
  • Commands implement routing and lifecycle contracts end to end.
  • Station mappings and priority policy are explicit.
  • Tool registration reports truthful availability and integration ownership.
  • Authorization, approval, audit behaviour, UI and verification are complete.

Until every relevant gate is satisfied, unavailable specifications remain language—not Tools.