Stage 3 · Tools
Proposed Recipes Tools
Language specifications derived from the capability analysis. Status reflects the current Tool source.
kitchen.recipes.create-recipe
Create Recipe
Create the Recipe identity that later production details can build upon.
Inputs
- name
- optional description
Outputs
- actor-stamped Recipe
Evidence
- current Kitchen and actor
Authority: The guarded Recipe create mutation writes Recipe-owned identity fields and Firestore rules authorize the selected Kitchen path.
Approval: The operator explicitly submits the Recipe.
kitchen.recipes.update-recipe
Update Recipe
Update the current Recipe name and description.
Inputs
- current Recipe
- operator-confirmed name or description changes
Outputs
- actor-stamped Recipe changes
Evidence
- canonical Recipe and current Kitchen authority
Authority: The guarded Recipe update mutation writes the current Recipe identity fields and Firestore rules authorize the Kitchen path.
Approval: The operator explicitly submits the named changes.
kitchen.recipes.delete-recipe
Delete Recipe
Permanently remove one Recipe after reviewing its current dependencies.
Inputs
- current Recipe identity
Outputs
- confirmed deletion
Evidence
- canonical Recipe, current Kitchen authority and visible Dish usage
Authority: The guarded Recipe delete mutation targets only the selected Recipe, does not cascade and relies on Firestore rules for Kitchen authority.
Approval: The destructive action requires explicit operator confirmation.
kitchen.recipes.scale-recipe
Recipe Scaling Calculator
Recalculate an approved Recipe for a required batch yield or portion count.
Inputs
- approved Recipe version
- target output
- validated conversions
Outputs
- source-linked scaled quantities and unresolved conversions
Evidence
- base Recipe quantities, yield and units
Authority: The Tool preserves ratios and never overwrites the approved Recipe or guesses an unsafe conversion.
Approval: Read-only scaling needs no mutation approval; saving a revised base Recipe is separate.
kitchen.recipes.calculate-cost
Recipe Cost Calculator
Calculate batch and portion cost from effective Ingredient and sub-Recipe evidence.
Inputs
- Recipe version
- effective Ingredient prices
- units, yields and conversions
Outputs
- source-linked batch and portion cost with unknowns
Evidence
- canonical Recipe and Ingredient records
Authority: The Tool does not invent prices, yields, conversions, labour, overhead or profit.
Approval: Calculation is read-only; accepting a commercial change is separate.
kitchen.recipes.manage-yield
Recipe Yield Management
Record expected or observed batch yield and its portion conversion for a Recipe version.
Inputs
- Recipe version
- yield quantity and unit
- portion size or count
- observation context
Outputs
- actor-stamped yield evidence or approved specification change
Evidence
- actual measurement or explicit operator expectation
Authority: Observed and expected yield remain distinct; AI estimates cannot masquerade as measurements.
Approval: An authorized operator submits the observation or approves the specification change.
recipesAI
Specialist responsibility
- Own Recipe interpretation, scaling, yield evidence and derived cost.
- Resolve Ingredient price and identity evidence from Ingredients and expose dependencies to Dish, Drink and Mise.
- Keep approved Recipe, observed production evidence, scaled projection, calculation and proposal distinct.
- Never invent an Ingredient, measure, conversion, yield, cost or completed production event.
- Expose Create Recipe, Update Recipe and Delete Recipe as available and preserve the requested status of unimplemented Tools.
KitchenAI
Coordinator responsibility
- Recognise Recipe intent and delegate it to RecipesAI.
- Pass selected Kitchen and authorized context without copying Recipe expertise.
- Coordinate explicit handoffs to IngredientsAI, DishesAI, DrinksAI and MiseAI.
- Discover real Tool availability through RecipesAI registration and preserve approvals.
Activation gate
- Canonical Recipe version, component, method and yield records are confirmed.
- Trusted Ingredient, price and sub-Recipe readers exist.
- Unit, density, preparation-loss, edible-yield and portion rules are explicit.
- Commands preserve ownership, authorization, stamps and version history.
- Tool registration, approvals, UI and end-to-end verification are complete.
Until every relevant gate is satisfied, unavailable specifications remain language—not Tools.