Costs Tool specifications

Stage 3 · Tools

Proposed Costs Tools

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

kitchen.costs.food-cost-report

Restaurant Food Cost Report

compoundrequested

Compare supported theoretical direct food cost with bounded Sales while exposing coverage and exclusions.

Records:reads Operational cost evidence

Inputs

  • selected Kitchen and period
  • approved Dish and Recipe specifications
  • effective Ingredient acquisition costs
  • KitchenSale lines

Outputs

  • currency-safe item and period food-cost measures, coverage and missing evidence

Evidence

  • canonical Recipe, Ingredient commercial evidence and KitchenSales

Authority: The Tool does not label offers as actual cost, fabricate missing prices, or claim actual usage, COGS, expenses, profit or accounting completeness.

Approval: Read-only reporting needs no mutation approval; export or accepted source correction is separate.

kitchen.costs.calculate-margin

Contribution Margin Calculator

ai-assistedrequested

Calculate captured selling price less evidenced direct item cost for an explicit item and scope.

Records:reads Operational cost evidence

Inputs

  • Dish or Drink
  • captured Menu or Sale price
  • supported direct item cost
  • optional bounded sold quantity

Outputs

  • source-linked unit and total contribution with exclusions

Evidence

  • approved specification, effective Ingredient costs and bounded price or Sales

Authority: The Tool calls the result contribution before named exclusions—not net profit—and refuses incompatible currencies or incomplete cost presented as complete.

Approval: Calculation is read-only; pricing, Recipe or purchasing changes remain explicit.

costsAI

Specialist responsibility

  • Own cost-measure definitions, evidence coverage, exclusions and the Costs Tool catalogue.
  • Resolve Recipe, Ingredient, Purchasing, Receiving, Inventory, Waste and KitchenSale evidence from their owners.
  • Keep offer, acquisition evidence, theoretical cost, actual usage, contribution, expense and accounting fact distinct.
  • Never invent a price, conversion, yield, usage, expense, cost coverage, profit or causal explanation.
  • Expose both current Tools as requested until authoritative inputs and callable registration exist.

KitchenAI

Coordinator responsibility

  • Recognise Cost intent and delegate it to CostsAI.
  • Ask which cost measure the operator means rather than collapsing distinct concepts.
  • Pass selected Kitchen and authorized evidence without copying Cost semantics.
  • Route missing operational evidence to its owning capability and preserve approvals.

Activation gate

  • Canonical Recipe, yield, portion and Ingredient-unit records are confirmed.
  • Authoritative effective acquisition-price evidence exists for the claimed scope.
  • KitchenSale inputs, currency rules, coverage and exclusions are explicit.
  • Trusted readers and calculators fail closed on missing or incompatible evidence.
  • Tool registration, authorization, export policy, UI and end-to-end verification are complete.

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