Logistics: Freight Exception Review with Claude Code: Result JSON Schema

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

Audience: Logistics operations teams

The problem

Logistics operations teams need freight exception review to run repeatedly against tracking events, bills of lading, invoices, carrier notes, and exception policies. In logistics 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 freight 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 freight 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": "freight exception review completed",
  "body": { "type": "logistics_freight_exception_review", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo