Waste Report Tool specifications

Stage 3 · Tools

Proposed Waste Report Tools

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

kitchen.waste-report.summarize-recorded-waste

Recorded Waste Summary

compoundrequested

Aggregate authorized Waste events by compatible quantity, type, reason, source and operational context.

Records:reads Waste events

Inputs

  • selected Kitchen and period
  • authorized Waste events
  • explicit grouping and unit rules

Outputs

  • traceable grouped quantities, event counts, unknowns and coverage

Evidence

  • only recorded Kitchen Waste events

Authority: The Tool does not treat missing records as zero, combine incompatible units or create a second Waste record.

Approval: Read-only reporting needs no mutation approval.

kitchen.waste-report.compare-periods

Waste Period Comparison

ai-assistedrequested

Compare equivalent recorded-Waste measures across two explicit Kitchen-local periods.

Records:reads Waste eventsreads Waste report

Inputs

  • two scoped Waste summaries
  • matching grouping and unit definitions

Outputs

  • measure differences, recurring patterns and visible scope limitations

Evidence

  • same canonical Waste-event semantics for both periods

Authority: The Tool identifies patterns but does not invent cause, prevention impact or avoided cost.

Approval: Read-only comparison needs no mutation approval.

kitchen.waste-report.prepare-evidence-review

Waste Evidence Review

compoundrequested

Assemble recorded events, grouped measures, supported costs and coverage gaps for accountable review.

Records:reads Waste eventsreads Waste report

Inputs

  • Waste summaries
  • source events
  • supported-cost calculations
  • requested review scope

Outputs

  • source-linked review with quantities, cost coverage and unresolved gaps

Evidence

  • Waste-owned events and authoritative cost sources only

Authority: The Tool does not certify compliance, fill missing events or label derived cost as an accounting loss.

Approval: Read-only assembly needs no mutation approval; export or external sharing is separately approved.

wasteReportAI

Specialist responsibility

  • Own Waste-report scope, aggregation semantics, comparison and evidence coverage.
  • Consume Waste-owned events and the Waste capability’s supported-cost calculation without duplicating them.
  • Keep events, aggregation, cost derivation, pattern and proposed action distinct.
  • Never invent an event, reason, conversion, cost, cause, avoided amount or compliance claim.
  • Expose every report Tool as requested until trusted readers and registration exist.

KitchenAI

Coordinator responsibility

  • Recognise Waste-report intent and delegate it to WasteReportAI.
  • Route recording or corrective action back to WasteAI.
  • Pass selected Kitchen, period and authorized evidence without copying report semantics.
  • Present evidence coverage and uncertainty before any cross-capability proposal.

Activation gate

  • Canonical Waste-event records and reason/source semantics are confirmed.
  • Bounded authorized readers support explicit Kitchen-local periods.
  • Unit compatibility, conversion, currency and cost-coverage rules are explicit.
  • Report projections reconcile to source events and fail closed on limits.
  • 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.