Receiving Tool specifications

Stage 3 · Tools

Proposed Receiving Tools

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

kitchen.receiving.open-delivery

Open Delivery Inspection

humanrequested

Start one receipt against an expected order or explicitly identified unplanned delivery.

Records:writes Receiving record

Inputs

  • Supplier
  • delivery time
  • purchase order or unplanned-delivery reason
  • paperwork references

Outputs

  • actor-stamped open Receiving record

Evidence

  • authorized Supplier and purchase-order facts

Authority: A trusted command verifies Kitchen authority without changing the purchase order.

Approval: The receiver explicitly opens the inspection.

kitchen.receiving.inspect-lines

Inspect Delivery Lines

humanrequested

Record delivered quantities, condition, temperature and traceability evidence line by line.

Records:reads Receiving recordwrites Receiving record

Inputs

  • open receipt
  • delivered products and quantities
  • applicable checks and readings

Outputs

  • immutable inspection observations

Evidence

  • purchase-order lines
  • measured readings
  • photos or documents when supplied

Authority: The command validates units and stamps the observing actor and time.

Approval: The receiver submits observed facts; no acceptance is inferred.

kitchen.receiving.review-discrepancies

Review Delivery Discrepancies

ai-assistedrequested

Compare ordered, delivered and inspected evidence and identify unresolved differences.

Records:reads Receiving record

Inputs

  • purchase order
  • inspection observations
  • applicable acceptance policy

Outputs

  • traceable discrepancy findings and unknowns

Evidence

  • only recorded order and inspection facts

Authority: ReceivingAI may interpret evidence but cannot select a disposition or invent a policy.

Approval: Review is read-only; decisions remain explicit operator actions.

kitchen.receiving.complete-receipt

Complete Receipt

compoundrequested

Record final line dispositions and project accepted quantities to downstream Inventory evidence.

Records:reads Receiving recordwrites Receiving recordreads Accepted Inventory movement

Inputs

  • reviewed receipt
  • accept, reject or hold decisions
  • corrective actions

Outputs

  • completed Receiving record
  • accepted Inventory movements
  • unresolved follow-ups

Evidence

  • actor-stamped decisions and supporting inspections

Authority: Only accepted quantities may cross the trusted Inventory command boundary.

Approval: An authorized receiver confirms every disposition before completion.

receivingAI

Specialist responsibility

  • Own Receiving interpretation, evidence requirements and its Tool catalogue.
  • Keep ordered, delivered, inspected and accepted facts distinct.
  • Apply only an identified policy or rule source and state uncertainty.
  • Never accept goods or update Inventory without an approved disposition.
  • Expose requested Tools as unavailable until trusted implementations exist.

KitchenAI

Coordinator responsibility

  • Recognise Receiving intent and delegate it to ReceivingAI.
  • Pass current Kitchen orientation and authorized context without copying Receiving expertise.
  • Discover Tool availability through ReceivingAI registration.
  • Present discrepancies and preserve approval before disposition or Inventory projection.

Activation gate

  • Canonical Receiving records and line observations exist.
  • Trusted readers and commands implement the contracts.
  • Units, policies, instruments and traceability fields are validated.
  • The Inventory projection accepts only finalized quantities.
  • Authorization, approval, audit behaviour, UI and verification are complete.

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