Food Safety Tool specifications

Stage 3 · Tools

Proposed Food Safety Tools

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

kitchen.food-safety.maintain-plan

Maintain Food Safety Plan

humanrequested

Create and version the Kitchen-specific plan, hazards, controls and verification responsibilities.

Records:writes Food Safety plan

Inputs

  • Kitchen processes
  • reviewed jurisdiction guidance
  • hazards, controls and responsible roles

Outputs

  • versioned draft or approved Food Safety plan

Evidence

  • source-identified guidance and accountable review

Authority: The Tool never labels generated text approved or legally sufficient without authorized review.

Approval: An accountable operator explicitly approves each plan version.

kitchen.food-safety.record-check

Record Food Safety Check

humanrequested

Record one required observation or measurement against an approved control.

Records:reads Food Safety planwrites Food Safety check

Inputs

  • control identity
  • observation or reading
  • instrument and context

Outputs

  • actor-stamped Food Safety check

Evidence

  • approved plan version and applicable rule

Authority: The command validates required fields, unit and Kitchen authority.

Approval: The operator explicitly submits the observed evidence.

kitchen.food-safety.review-deviation

Review Food Safety Deviation

ai-assistedrequested

Compare recorded evidence with its approved rule and expose a failed, missing or uncertain control.

Records:reads Food Safety planreads Food Safety check

Inputs

  • check record
  • applicable plan control and limit

Outputs

  • traceable finding with rule source and uncertainty

Evidence

  • recorded observation and approved plan only

Authority: FoodSafetyAI cannot invent a limit, observation or product disposition.

Approval: Review is read-only; action remains explicit.

kitchen.food-safety.record-corrective-action

Record Corrective Action

humanrequested

Record containment, product disposition, cause correction, responsibility and follow-up for a deviation.

Records:writes Corrective action

Inputs

  • deviation
  • actual actions
  • responsible actor
  • follow-up

Outputs

  • reviewable corrective-action record

Evidence

  • failed or missed control and operator observations

Authority: The Tool records what occurred and cannot prescribe universal legal action.

Approval: The accountable operator confirms the action and disposition.

kitchen.food-safety.prepare-evidence-review

Prepare Food Safety Evidence Review

compoundrequested

Assemble plan versions, checks, deviations, actions and visible gaps for an authorized review.

Records:reads Food Safety planreads Food Safety checkreads Corrective action

Inputs

  • period
  • approved plans
  • authorized operational records

Outputs

  • source-linked evidence pack and unresolved gaps

Evidence

  • only stored, authorized Food Safety records

Authority: The result never certifies compliance or silently fills missing evidence.

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

foodSafetyAI

Specialist responsibility

  • Own Food Safety interpretation, plan evidence and its Tool catalogue.
  • Use only source-identified rules and approved Kitchen plan versions.
  • Keep external guidance, approved plan, operational records and deductions distinct.
  • Never claim legal compliance, invent a reading or choose product disposition.
  • Expose every current Tool as requested until trusted implementation exists.

KitchenAI

Coordinator responsibility

  • Recognise Food Safety intent and delegate it to FoodSafetyAI.
  • Pass selected Kitchen and authorized context without copying Food Safety expertise.
  • Discover real Tool availability through FoodSafetyAI registration.
  • Present urgent evidence clearly while preserving accountable human decisions.

Activation gate

  • Canonical plan, control, check, deviation and corrective-action records exist.
  • Trusted readers and commands implement the contracts.
  • Jurisdiction and plan-version sources are explicit.
  • Tool registration reports truthful availability.
  • Authorization, approvals, audit behaviour, UI and verification are complete.

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