Stage 3 · Tools

Proposed Stations Tools

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

kitchen.stations.create-station

Add Station

humanavailable

Create one named Kitchen production destination.

Records:writes Kitchen Station

Inputs

  • name

Outputs

  • active KitchenStation with the next display order

Evidence

  • current Kitchen, actor and existing Station order

Authority: The guarded Station create mutation writes the selected Kitchen path and Firestore rules authorize it.

Approval: The operator explicitly submits the Station.

kitchen.stations.assign-dishes

Assign Dishes to Station

humanrequested

Connect Dishes or preparation stages to their responsible Station.

Records:reads Kitchen Stationwrites Station configuration

Inputs

  • Station
  • Dishes or stages
  • optional sequence

Outputs

  • reviewable routing configuration

Evidence

  • authorized Station and Dish identities

Authority: The command changes configuration only and does not create live Order work.

Approval: The operator confirms the affected routing mappings.

kitchen.stations.set-readiness

Set Station Readiness Checklist

humanrequested

Define the checks required before a Station is ready for service.

Records:reads Kitchen Stationwrites Station configuration

Inputs

  • Station
  • named checks
  • applicable service context

Outputs

  • versioned readiness requirements

Evidence

  • Kitchen policy and Station needs

Authority: Defining requirements is distinct from recording a completed check.

Approval: The operator confirms checklist changes.

kitchen.stations.set-competencies

Set Station Competencies

humanrequested

Record competencies required to work a Station.

Records:reads Kitchen Stationwrites Station configuration

Inputs

  • Station
  • competency requirements

Outputs

  • versioned Station requirements

Evidence

  • Kitchen operating policy

Authority: The Tool cannot grant Team roles or claim a person has a competency.

Approval: The operator confirms requirement changes.

stationsAI

Specialist responsibility

  • Own Station interpretation, configuration evidence and its Tool catalogue.
  • Keep Station identity separate from devices, people and live work.
  • Use only authorized Dish, Team and Kitchen configuration evidence.
  • Never infer competency or readiness from assignment alone.
  • Expose Add Station as available and preserve the requested status of unimplemented Tools.

KitchenAI

Coordinator responsibility

  • Recognise Station intent and delegate it to StationsAI.
  • Pass selected Kitchen and authorized context without copying Station expertise.
  • Discover real Tool availability through StationsAI registration.
  • Preserve Team, Mise and Orders authority when presenting Station deductions.

Activation gate

  • Canonical Station configuration and relationships are confirmed.
  • Trusted commands implement each Tool contract end to end.
  • Routing dependencies and retirement behaviour are validated.
  • Tool registration reports truthful availability.
  • Authorization, approval, audit behaviour, UI and verification are complete.

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