Ingredients Tool specifications

Stage 3 · Tools

Proposed Ingredients Tools

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

kitchen.ingredients.add-ingredient

Add Ingredient

humanavailable

Select an active canonical Ingredient for this Kitchen.

Records:writes Kitchen Ingredient

Inputs

  • Ingredient identity

Outputs

  • Kitchen Ingredient selection

Evidence

  • canonical Ingredient and current Kitchen

Authority: The Tool links the Ingredient without copying or changing its canonical identity.

Approval: The operator explicitly selects the Ingredient.

kitchen.ingredients.count-stock

Restaurant Inventory Count

compoundrequested

Use Ingredient identity and units to submit an observed quantity to Inventory.

Records:reads Kitchen Ingredientreads Ingredient operational evidence

Inputs

  • Ingredient
  • Inventory location
  • observed quantity, unit and time

Outputs

  • Inventory-owned actor-stamped count linked to the Ingredient

Evidence

  • canonical Ingredient and authorized physical observation

Authority: Inventory remains quantity authority; the Ingredient record never stores a second stock balance.

Approval: The operator explicitly submits the observed count.

kitchen.ingredients.set-reorder-level

Reorder Level Management

compoundrequested

Create or update Inventory replenishment policy for an Ingredient.

Records:reads Kitchen Ingredientreads Ingredient operational evidence

Inputs

  • Ingredient
  • location
  • reorder quantity or derivation evidence
  • lead time and safety stock

Outputs

  • Inventory-owned replenishment policy linked to the Ingredient

Evidence

  • demand, Supplier lead time and explicit operator policy

Authority: The Tool distinguishes a calculated proposal from approved policy and does not place a Purchase Order.

Approval: An authorized operator approves the policy values.

kitchen.ingredients.record-waste

Food Waste Tracker

compoundrequested

Send an observed Ingredient loss to the Waste capability.

Records:reads Kitchen Ingredientreads Ingredient operational evidence

Inputs

  • Ingredient
  • quantity and unit
  • reason, source, actor and time

Outputs

  • Waste-owned actor-stamped event linked to the Ingredient

Evidence

  • authorized observation and compatible Ingredient unit

Authority: Waste remains event authority; no duplicate loss or automatic stock correction is created.

Approval: The operator explicitly submits the Waste event and any separate Inventory adjustment.

kitchen.ingredients.review-usage

Ingredient Usage Analysis

ai-assistedrequested

Trace where an Ingredient is used across Recipes, Dishes and Drinks.

Records:reads Kitchen Ingredientreads Ingredient operational evidence

Inputs

  • Ingredient
  • authorized Recipe, Dish and Drink graphs

Outputs

  • source-linked dependency view and unresolved references

Evidence

  • canonical identifiers and explicit relationships

Authority: The Tool does not infer usage from matching names or mutate downstream records.

Approval: Read-only analysis needs no mutation approval.

ingredientsAI

Specialist responsibility

  • Own Ingredient interpretation, units, food-fact provenance and dependency analysis.
  • Resolve Supplier, Purchasing, Receiving, Inventory, Waste, Recipe, Dish and Drink evidence from their owners.
  • Keep canonical Ingredient, external source fact, approved fact, operational event and deduction distinct.
  • Never invent an allergen, conversion, price, stock quantity, reorder policy, Waste event or dependency.
  • Expose Add Ingredient as available and preserve the requested status of unimplemented Tools.

KitchenAI

Coordinator responsibility

  • Recognise Ingredient intent and delegate it to IngredientsAI.
  • Pass selected Kitchen and authorized context without copying Ingredient expertise.
  • Coordinate explicit handoffs to InventoryAI, WasteAI, SuppliersAI, RecipesAI and related capabilities.
  • Discover real Tool availability through IngredientsAI registration and preserve approvals.

Activation gate

  • Canonical Ingredient identity, unit and food-fact records are confirmed.
  • Trusted Supplier, receipt, Inventory, Waste, Recipe, Dish and Drink readers exist.
  • Conversions, source provenance and effective commercial evidence 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.