Inventory Tool specifications

Stage 3 · Tools

Proposed Inventory Tools

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

kitchen.inventory.prepare-count

Prepare Inventory Count

humanrequested

Prepare a count session arranged by Kitchen storage location.

Records:writes Inventory observation

Inputs

  • authorized stock catalogue
  • storage locations
  • optional prior count

Outputs

  • one bounded Inventory count session

Evidence

  • Ingredient identity
  • count unit
  • storage location

Authority: A trusted reader includes only stock belonging to the selected Kitchen.

Approval: Preparing a session is read-only; saving its scope requires explicit operator confirmation.

kitchen.inventory.record-count

Record Inventory Count

humanrequested

Record observed on-hand quantities for one count session.

Records:writes Inventory observation

Inputs

  • count session
  • item quantities and units
  • counted time

Outputs

  • immutable, actor-stamped count observations

Evidence

  • current Kitchen
  • actor identity
  • countable items and locations

Authority: A trusted command verifies Kitchen write authority and compatible units.

Approval: The operator reviews and explicitly submits the count.

kitchen.inventory.review-levels

Review Stock Levels

ai-assistedrequested

Compare latest supported counts with par, reorder and expiry evidence.

Records:reads Inventory observationreads Inventory level

Inputs

  • latest count observations
  • par levels
  • reorder points
  • expiry evidence

Outputs

  • traceable low-stock, overstock and expiry findings

Evidence

  • only authorized Inventory records and configured thresholds

Authority: The deduction preserves its evidence time and never presents an estimate as a physical count.

Approval: Findings are read-only; changing thresholds or stock requires a separate approved command.

kitchen.inventory.propose-replenishment

Propose Replenishment

compoundrequested

Turn supported shortages into a draft request for Purchasing.

Records:reads Inventory observationreads Inventory level

Inputs

  • stock-level findings
  • par targets
  • available Purchasing Tools

Outputs

  • quantified replenishment proposal with evidence

Evidence

  • current count, threshold and optional usage evidence

Authority: InventoryAI may propose; Purchasing retains supplier, price, order and approval authority.

Approval: The proposal changes nothing. Any purchase uses the Purchasing Tool’s own approval.

inventoryAI

Specialist responsibility

  • Own Inventory interpretation, evidence requirements and the Inventory Tool catalogue.
  • Distinguish physical observations from derived stock estimates and variance.
  • Use authorized counts, thresholds, expiry and related operational evidence only.
  • Expose requested Tools as unavailable language until their trusted implementation exists.
  • Return evidence time, uncertainty and approval requirements with every finding or proposal.

KitchenAI

Coordinator responsibility

  • Recognise Inventory intent and delegate it to InventoryAI.
  • Pass current Kitchen orientation and authorized context without copying Inventory expertise.
  • Discover Inventory Tool availability through InventoryAI registration.
  • Present findings and preserve the Purchasing boundary for replenishment actions.

Activation gate

  • Canonical count sessions and observations exist.
  • Trusted readers or commands implement the Tool contracts.
  • Count units and item relationships are validated.
  • The Tools are registered with real availability and approval policies.
  • Authorization, UI, audit behaviour and verification are complete.

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