Mise Tool specifications

Stage 3 · Tools

Proposed Mise Tools

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

kitchen.mise.create-prep-task

Add Prep Task

humanavailable

Add one explicit task to the Kitchen prep list.

Records:writes Mise task

Inputs

  • title
  • optional quantity, Station, assignee and due time

Outputs

  • KitchenMiseTask

Evidence

  • current Kitchen and actor

Authority: The guarded Mise create mutation targets the selected Kitchen and relies on Firestore rules for write authority.

Approval: The operator explicitly submits the task.

kitchen.mise.update-prep-task

Update Prep Task

humanavailable

Change the working details of a prep task.

Records:reads Mise taskwrites Mise task

Inputs

  • task identity
  • named changes

Outputs

  • updated KitchenMiseTask

Evidence

  • current stored task

Authority: The guarded Mise update mutation targets the selected task and relies on Firestore rules for Kitchen authority.

Approval: The operator submits the named changes.

kitchen.mise.change-prep-status

Change Prep Status

humanavailable

Move a prep task through its working states.

Records:reads Mise taskwrites Mise task

Inputs

  • task identity
  • new status

Outputs

  • actor-stamped status change

Evidence

  • current task state

Authority: The guarded Mise status mutation targets the selected task and relies on Firestore rules for Kitchen authority.

Approval: The operator explicitly selects the new state.

kitchen.mise.delete-prep-task

Delete Prep Task

humanavailable

Permanently remove one prep task.

Records:reads Mise taskwrites Mise task

Inputs

  • task identity

Outputs

  • confirmed deletion

Evidence

  • current task

Authority: The guarded Mise delete mutation targets the selected task and relies on Firestore rules for Kitchen authority.

Approval: The destructive action requires explicit confirmation.

kitchen.mise.generate-prep-list

Generate Prep List

compoundrequested

Prepare proposed tasks from service requirements.

Records:reads Production demand

Inputs

  • Menus
  • Recipes
  • prepared stock
  • expected demand

Outputs

  • reviewable proposed tasks with provenance

Evidence

  • authorized source records

Authority: MiseAI may propose but cannot create tasks silently.

Approval: The chef confirms proposed tasks before creation.

kitchen.mise.calculate-quantities

Calculate Prep Quantities

ai-assistedrequested

Calculate reviewable targets for expected demand.

Records:reads Production demand

Inputs

  • Recipe yields
  • expected demand
  • on-hand prep

Outputs

  • target quantities with assumptions

Evidence

  • compatible source quantities and units

Authority: Unknown or incompatible evidence remains explicit.

Approval: Calculation is read-only; applying targets requires confirmation.

kitchen.mise.assign-by-station

Assign Prep by Station

compoundrequested

Group and propose responsibility for preparation work.

Records:reads Production demand

Inputs

  • prep tasks
  • Stations
  • available Team context

Outputs

  • assignment proposal

Evidence

  • task Station requirements and authorized Team evidence

Authority: MiseAI may propose assignments but not alter Team authority.

Approval: An operator confirms assignments before tasks change.

miseAI

Specialist responsibility

  • Own Mise interpretation, evidence requirements and its Tool catalogue.
  • Use the four available human Tools only within their existing authority and approval contracts.
  • Keep generated tasks and quantities as proposals until confirmed.
  • Distinguish Recipe definition, planned prep, live Orders and Waste evidence.
  • Return assumptions and source evidence with every derived prep plan.

KitchenAI

Coordinator responsibility

  • Recognise prep intent and delegate it to MiseAI.
  • Pass current Kitchen orientation and authorized context without copying Mise expertise.
  • Discover real Tool availability through MiseAI registration.
  • Present proposals and preserve approval for every task mutation.

Activation gate

  • Existing human Tools remain verified against their trusted commands.
  • Requested generators have authoritative Recipe, demand and unit evidence.
  • AI registration reports actual per-Tool availability.
  • Authorization, approvals, audit behaviour, UI and verification remain complete.

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