Stage 3 · Tools

Proposed Drinks Tools

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

kitchen.drinks.create-drink

Create Drink

humanavailable

Create one Kitchen-owned sellable beverage.

Records:writes Drink

Inputs

  • name
  • optional description and image

Outputs

  • actor-stamped Drink

Evidence

  • current Kitchen and actor

Authority: The guarded Drink create mutation writes Drink-owned fields and Firestore rules authorize the selected Kitchen path.

Approval: The operator explicitly submits the Drink.

kitchen.drinks.update-drink

Update Drink

humanavailable

Update the current Drink image, name or description, with contextual DrinksAI assistance where useful.

Records:reads Drinkwrites Drink

Inputs

  • current Drink
  • operator-confirmed field changes
  • optional confirmed notes for an AI-assisted description

Outputs

  • actor-stamped Drink changes
  • editable AI proposal when requested

Evidence

  • canonical Drink identity
  • operator-confirmed changes and notes

Authority: Guarded Drink field and media mutations own canonical writes. DrinksAI may propose from supplied evidence but cannot update the Drink.

Approval: The operator explicitly submits ordinary field changes and separately reviews, edits and approves every AI proposal.

kitchen.drinks.delete-drink

Delete Drink

humanavailable

Permanently remove one Drink after reviewing the selected record.

Records:reads Drinkwrites Drink

Inputs

  • current Drink identity

Outputs

  • confirmed deletion

Evidence

  • canonical Drink and current Kitchen authority

Authority: The guarded Drink delete mutation targets only the selected Drink and Firestore rules authorize the Kitchen path.

Approval: The destructive action requires explicit operator confirmation.

kitchen.drinks.track-stock

Beverage Inventory Tracker

compoundrequested

Provide a Drink-focused stock view and send explicit beverage counts or movements to Inventory.

Records:reads Drinkreads Drink operational evidence

Inputs

  • Drink or beverage Ingredient
  • location
  • quantity, unit and movement reason

Outputs

  • Inventory-owned observation or movement linked to the Drink

Evidence

  • canonical Drink and Ingredient identity
  • authorized observed quantity

Authority: Inventory remains the stock authority; this Tool cannot create a parallel Drink stock balance.

Approval: The operator explicitly submits each observed count or movement.

kitchen.drinks.calculate-cost

Drink Cost Calculator

ai-assistedrequested

Calculate direct cost per serve from Recipe measures and effective Ingredient prices.

Records:reads Drinkreads Drink operational evidence

Inputs

  • Drink
  • Recipe
  • Ingredient prices, units and yields

Outputs

  • source-linked Drink cost with effective time and unknowns

Evidence

  • canonical Recipe and Ingredient records

Authority: The Tool does not invent prices, measures, conversions, wastage or Menu price.

Approval: Calculation is read-only; accepting a Recipe or Menu change is separate.

kitchen.drinks.manage-recipe

Cocktail Recipe Management

compoundrequested

Create or update the Recipe used by a mixed Drink through Recipe-owned commands.

Records:reads Drinkreads Drink operational evidence

Inputs

  • Drink
  • Recipe ingredients, measures, method and yield
  • named changes

Outputs

  • Recipe-owned actor-stamped record linked to the Drink

Evidence

  • authorized Ingredient identities and current Recipe

Authority: Recipe remains authoritative; the Drink capability does not store a duplicate method or yield.

Approval: An authorized operator confirms the Recipe changes.

kitchen.drinks.review-menu

Beverage Menu Review

compoundrequested

Assemble availability, price, placement, cost and bounded sales evidence for Drinks on a Menu.

Records:reads Drinkreads Drink operational evidence

Inputs

  • Drink set
  • Menu placements and prices
  • Inventory availability
  • cost and KitchenSale evidence

Outputs

  • source-linked beverage Menu review and proposed actions

Evidence

  • owning capability records with explicit scope

Authority: The Tool does not invent profitability or silently change Inventory, Drink, Recipe or Menu records.

Approval: Review is read-only; every accepted change is delegated and explicitly approved.

drinksAI

Specialist responsibility

  • Own Drink interpretation, beverage-focused deductions and the Drink Tool catalogue.
  • Resolve Inventory, Recipe, Ingredient, Menu and KitchenSale evidence from their owning capabilities.
  • Keep canonical facts, derived calculations, proposals and accepted cross-capability changes distinct.
  • Never invent stock, cost, measures, price, sales, allergens or alcohol-control facts.
  • Expose Create Drink and Update Drink as available and preserve the requested status of unimplemented Tools.

KitchenAI

Coordinator responsibility

  • Recognise Drink intent and delegate it to DrinksAI.
  • Pass selected Kitchen and authorized context without copying beverage expertise.
  • Coordinate explicit handoffs among DrinksAI, InventoryAI, RecipesAI, MenusAI and Finance evidence.
  • Discover real Tool availability through DrinksAI registration and preserve approval boundaries.

Activation gate

  • Canonical Drink identity and specification records are confirmed.
  • Trusted Ingredient, Recipe, Inventory, Menu and KitchenSale readers exist.
  • Beverage units, yields, effective prices and movement rules are explicit.
  • Cross-capability commands preserve ownership, authorization, stamps and approvals.
  • Tool registration, UI and end-to-end verification are complete.

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