Inventory Exception Review with Claude Code: Result JSON Schema

A production playbook for inventory exception review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Supply chain operations teams

The problem

Supply chain operations teams need inventory exception review to run repeatedly against inventory exports, exception lists, and SOPs. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the inventory exception review skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For inventory exception review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "inventory exception review completed",
  "body": { "type": "inventory_exception_review", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo