Logistics: Bill Of Lading Audit with Claude Code: Result JSON Schema

A production playbook for bill of lading audit in logistics operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Freight audit teams

The problem

Freight audit teams need bill of lading audit to run repeatedly against BOLs, shipment records, carrier invoices, accessorial charges, and rate cards. 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 bill of lading audit 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 bill of lading audit, 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": "bill of lading audit completed",
  "body": { "type": "logistics_bol_audit", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo