Stage 3 · Tools
Proposed Waste Tools
Language specifications derived from the capability analysis. Status reflects the current Tool source.
kitchen.waste.record-event
Record Waste
Capture one Waste event at the point it occurs.
Inputs
- item or item reference
- quantity and unit
- reason
- operational source
- occurred time
Outputs
- one reviewable Kitchen Waste event
Evidence
- current Kitchen
- actor identity
- optional Ingredient, Recipe, Dish, Drink, Station, Mise or Order reference
Authority: The guarded Waste create mutation targets the selected Kitchen, stamps the actor and relies on Firestore rules for write authority.
Approval: The operator explicitly submits the record before anything is written.
kitchen.waste.review-patterns
Review Waste Patterns
Group recorded Waste by item, reason, source and period.
Inputs
- authorized Waste events
- period
- optional reason, source or item filters
Outputs
- traceable quantities and recurring-pattern summaries
Evidence
- only recorded Waste events inside the requested period
Authority: A bounded reader returns only Waste records the current identity may inspect.
Approval: Reading requires authority but no mutation approval.
kitchen.waste.calculate-supported-cost
Calculate Supported Waste Cost
Attach or aggregate cost only when an authoritative operational cost can be resolved.
Inputs
- Waste event quantity
- unit
- item reference
- authoritative unit-cost evidence
Outputs
- supported cost with source identity
- unknown when evidence is absent
Evidence
- Ingredient purchase price, Recipe cost or Dish cost with compatible units
Authority: The calculation reads bounded source evidence and never substitutes an estimate for a missing cost.
Approval: A read-only calculation needs no mutation approval; persisting a result would require a separate approved command.
kitchen.waste.propose-reduction
Propose a Waste Reduction Action
Turn a repeated, evidenced Waste pattern into a contextual operational proposal.
Inputs
- pattern summary
- supporting Waste events
- available downstream Tools
Outputs
- reasoned suggestion
- supporting evidence
- optional proposed Tool invocation
Evidence
- repeated pattern plus relevant Inventory, Purchasing, Mise, Recipe, Dish or Order context when available
Authority: WasteAI may propose from authorized evidence but cannot change another capability directly.
Approval: Suggestions need no approval; every proposed mutation requires the destination Tool’s own approval.
wasteAI
Specialist responsibility
- Own Waste interpretation, evidence requirements and the Waste Tool catalogue.
- Answer general Waste questions without claiming live Kitchen evidence.
- Use only authorized Waste context and currently available Tools.
- Expose requested Tools as unavailable language, never as executable actions.
- Return evidence, uncertainty and any approval requirement with a proposal.
KitchenAI
Coordinator responsibility
- Recognise Waste intent and delegate it to WasteAI.
- Pass current Kitchen orientation and authorized context without copying Waste expertise.
- Discover Waste Tool availability through WasteAI registration rather than hard-coded Tool knowledge.
- Present WasteAI results and preserve approval boundaries for any future action.
Activation gate
- The required canonical records exist.
- A trusted reader or command implements the Tool contract.
- The Tool is registered to WasteAI with its real availability and approval policy.
- Authorization, UI, audit behaviour and verification are complete.
Until every relevant gate is satisfied, unavailable specifications remain language—not Tools.