Stage 3 · Tools
Proposed Dishes Tools
Language specifications derived from the capability analysis. Status reflects the current Tool source.
kitchen.dishes.create-dish
Create Dish
Create one Kitchen-owned sellable food item.
Inputs
- name
- optional description and image
Outputs
- actor-stamped Dish
Evidence
- current Kitchen and actor
Authority: The guarded Dish create mutation writes Dish-owned fields and Firestore rules authorize the selected Kitchen path.
Approval: The operator explicitly submits the Dish.
kitchen.dishes.update-dish
Update Dish
Update the current Dish image, name, description or flagship selection.
Inputs
- current Dish
- operator-confirmed named changes
Outputs
- actor-stamped Dish changes
Evidence
- canonical Dish and current Kitchen authority
Authority: Guarded Dish field and media mutations write only their bounded Dish fields; Firestore rules and the flagship server command enforce their respective authority.
Approval: The operator explicitly submits each change.
kitchen.dishes.delete-dish
Delete Dish
Permanently remove one Dish after reviewing the selected record.
Inputs
- current Dish identity
Outputs
- confirmed deletion
Evidence
- canonical Dish and current Kitchen authority
Authority: The guarded Dish delete mutation targets only the selected Dish and Firestore rules authorize the Kitchen path.
Approval: The destructive action requires explicit operator confirmation.
kitchen.dishes.calculate-cost
Dish Cost Calculator
Calculate direct food cost per Dish from its Recipe, Ingredient prices, yields and portion evidence.
Inputs
- Dish specification
- Recipe yields and quantities
- effective Ingredient prices and units
Outputs
- source-linked Dish cost with effective time and unknowns
Evidence
- canonical Dish, Recipe and Ingredient records
Authority: The Tool does not invent prices, unit conversions, yield or overhead and does not store a guess as authoritative cost.
Approval: Calculation is read-only; accepting a changed specification or price is separate.
kitchen.dishes.analyze-profitability
Menu Item Profit Calculator
Compare selling price, evidenced direct cost and bounded sales contribution for a Dish.
Inputs
- Dish
- Menu price context
- calculated Dish cost
- KitchenSale period
Outputs
- source-linked contribution view with exclusions and uncertainty
Evidence
- approved cost calculation and authoritative KitchenSale lines
Authority: The Tool reports contribution, not unsupported net profit, and leaves missing evidence visible.
Approval: Analysis is read-only; any pricing or specification action remains explicit.
kitchen.dishes.compare-popularity
Dish Popularity Analysis
Compare Dish sales quantities for a selected Kitchen, period and relevant Menu context.
Inputs
- Dish set
- bounded KitchenSale lines
- period and comparison scope
Outputs
- traceable popularity measures and comparison
Evidence
- authoritative KitchenSale item quantities
Authority: The Tool cannot substitute page views, inferred demand or cross-scope totals for sales.
Approval: Read-only analysis needs no mutation approval.
dishesAI
Specialist responsibility
- Own Dish specification interpretation, derived cost and bounded performance deductions.
- Resolve Recipe, Ingredient, Menu, Station and KitchenSale evidence from their owning capabilities.
- Keep canonical Dish facts, derived calculations, proposals and accepted changes distinct.
- Never invent a cost, sale, allergen, yield, price or profitability claim.
- Expose Create Dish, Update Dish and Delete Dish as available and preserve the requested status of unimplemented Tools.
KitchenAI
Coordinator responsibility
- Recognise Dish intent and delegate it to DishesAI.
- Pass selected Kitchen and authorized context without copying Dish expertise.
- Coordinate explicit handoffs to Recipes, Ingredients, Menus, Stations and Finance.
- Discover real Tool availability through DishesAI registration and preserve approvals.
Activation gate
- Canonical Dish specification and lifecycle records are confirmed.
- Trusted Recipe, Ingredient, Menu, Station and KitchenSale readers exist.
- Unit, yield, effective-price and sales-period rules are explicit.
- Commands preserve ownership, authorization, stamps and named changes.
- Tool registration, approvals, UI and verification are complete.
Until every relevant gate is satisfied, unavailable specifications remain language—not Tools.