Menus Tool specifications

Stage 3 · Tools

Proposed Menus Tools

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

kitchen.menus.create-menu

Create Menu

humanavailable

Create a Menu from an uploaded document, image or URL through a reviewable AI-assisted draft.

Records:writes Kitchen Menu

Inputs

  • source document, image or URL
  • Menu name
  • target Kitchen and currency

Outputs

  • source-linked extraction draft
  • confirmed Menu, sections and item records

Evidence

  • original source
  • AI extraction trace
  • operator-reviewed draft

Authority: Source capture does not create a Menu. The trusted confirmation command validates the reviewed draft before writing Menu-owned records and referenced Kitchen items.

Approval: The operator explicitly confirms the reviewed draft before canonical records are created.

kitchen.menus.update-menu

Update Menu

humanavailable

Update Menu-owned details, sections, placements, presentation and ordering configuration.

Records:reads Kitchen Menuwrites Kitchen Menu

Inputs

  • current Menu
  • operator-confirmed named changes
  • authorized Dish and Drink references

Outputs

  • actor-stamped Menu changes

Evidence

  • canonical Menu and referenced item identities

Authority: Menu commands update Menu-owned composition and presentation without rewriting Dish or Drink records.

Approval: The operator explicitly submits each change.

kitchen.menus.delete-menu

Delete Menu

humanavailable

Permanently remove one Menu after reviewing the selected record.

Records:reads Kitchen Menuwrites Kitchen Menu

Inputs

  • current Menu identity

Outputs

  • confirmed deletion

Evidence

  • canonical Menu and current Kitchen authority

Authority: The Menu delete command verifies Kitchen write authority and deletes only the selected Menu.

Approval: The destructive action requires explicit operator confirmation.

kitchen.menus.engineer-menu

Menu Engineering Calculator

ai-assistedrequested

Compare Menu-item popularity and contribution margin from bounded authoritative evidence.

Records:reads Kitchen Menureads Menu performance evidence

Inputs

  • Menu version
  • period
  • KitchenSale measures
  • approved item costs

Outputs

  • source-linked Menu engineering view with unknowns

Evidence

  • authoritative bounded sales and cost records

Authority: The Tool never invents cost, profit or sales and does not mutate the Menu from an analysis.

Approval: Analysis is read-only; accepting a proposed Menu change is separate and explicit.

kitchen.menus.publish-menu

Menu Publishing

compoundrequested

Publish an approved Menu version to selected supported destinations.

Records:reads Kitchen Menuwrites Kitchen Menu

Inputs

  • approved Menu version
  • publication targets
  • effective timing

Outputs

  • publication result, target status and stable doorway

Evidence

  • reviewed Menu and target-specific validation

Authority: The Tool publishes a projection and preserves the canonical Menu, target result and prior version.

Approval: An authorized operator explicitly approves publication or scheduling.

menusAI

Specialist responsibility

  • Own Menu composition, import interpretation, engineering deductions and publication proposals.
  • Resolve Dish, Drink, sales and cost evidence from their owning capabilities.
  • Keep source extraction, canonical records, approved Menu and published projection distinct.
  • Never invent prices, allergens, availability, costs, sales or publication success.
  • Expose Create Menu, Update Menu and Delete Menu as available and preserve the requested status of unimplemented Tools.

KitchenAI

Coordinator responsibility

  • Recognise Menu intent and delegate it to MenusAI.
  • Pass selected Kitchen and authorized context without copying Menu expertise.
  • Coordinate explicit handoffs to Dish, Drink, Finance, Inventory and publishing capabilities.
  • Discover real Tool availability through MenusAI registration and preserve approval boundaries.

Activation gate

  • Canonical Menu, section, placement, version and publication records are confirmed.
  • Trusted readers and commands implement the contracts.
  • Dish, Drink, sales, cost and allergen authority boundaries are explicit.
  • Import provenance, review and publication results remain auditable.
  • Tool registration, authorization, approvals, UI and verification are complete.

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