Performance Tool specifications

Stage 3 · Tools

Proposed Performance Tools

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

kitchen.performance.review-service-timing

Service Timing Report

ai-assistedrequested

Summarise complete Order lifecycle durations, volumes and coverage for an explicit Kitchen-local period.

Records:reads Operational performance evidence

Inputs

  • completed Order transition histories
  • period
  • named start and end events

Outputs

  • count, duration distribution, percentiles, on-time measures and missing coverage

Evidence

  • authoritative timestamped Order transitions only

Authority: The Tool cannot derive observed timing from estimates, current status or one update stamp.

Approval: Read-only reporting needs no mutation approval.

kitchen.performance.review-stations

Station Performance Report

compoundrequested

Compare eligible work volume and timing by historically applicable Station routing.

Records:reads Operational performance evidence

Inputs

  • Station work projections
  • routing history
  • complete lifecycle timestamps
  • period

Outputs

  • Station-grouped measures, workload context and unresolved routing

Evidence

  • Order and Station-owned operational records

Authority: The Tool does not infer individual performance, staffing cause or historical Station from current configuration.

Approval: Read-only reporting needs no mutation approval.

kitchen.performance.review-production

Prep Completion Report

ai-assistedrequested

Compare planned Mise tasks with recorded completion, lateness and blocked outcomes.

Records:reads Operational performance evidence

Inputs

  • Mise tasks
  • service period
  • explicit due, start, status and completion evidence

Outputs

  • task-state counts, supported timing and visible missing evidence

Evidence

  • actor-stamped Mise records

Authority: The Tool reports work records—not labour productivity, paid time, quality or individual ranking.

Approval: Read-only reporting needs no mutation approval.

kitchen.performance.compare-periods

Kitchen Performance Comparison

compoundrequested

Compare the same supported operational measures across two equivalent periods.

Records:reads Operational performance evidence

Inputs

  • two complete report projections
  • matching definitions and eligibility rules

Outputs

  • measure differences, workload context, coverage and investigation prompts

Evidence

  • same owning operational sources for both periods

Authority: The Tool does not invent causes, benchmarks, staffing recommendations, customer impact or profit.

Approval: Read-only comparison needs no mutation approval.

performanceAI

Specialist responsibility

  • Own measure definitions, eligibility, coverage, comparison and the Performance Tool catalogue.
  • Consume timestamped Orders, Station work, Mise tasks and readiness evidence from their owning capabilities.
  • Keep operational record, report projection, benchmark, comparison and deduction distinct.
  • Never invent a timestamp, route, completion, productivity measure, cause, quality result, staffing need or profit impact.
  • Expose every current Tool as requested until complete producers, readers and registration exist.

KitchenAI

Coordinator responsibility

  • Recognise Kitchen Performance intent and delegate it to PerformanceAI.
  • Ask which operational outcome and measure definition the operator means.
  • Pass selected Kitchen, period and authorized context without copying report semantics.
  • Route operational action proposals to the owning capability and preserve approvals.

Activation gate

  • Orders retain complete timestamped lifecycle transitions.
  • Station work preserves historical routing and completion evidence.
  • Mise and readiness records have complete service-scoped timestamps and semantics.
  • Bounded projections define eligibility, timezone, coverage, limits and reconciliation.
  • Tool registration, authorization, UI and end-to-end verification are complete.

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