Logistics: Bill Of Lading Audit with Claude Code: Artifact Delivery
A production playbook for bill of lading audit in logistics operations using Claude Code: artifact delivery, 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
Require Claude Code to write customer-visible files under /skill/output/artifacts, validate filenames and sizes, then return signed artifact metadata in argo.result.v1.
Tradeoffs and failure modes
Artifact policy constrains file output, but customers receive files that are durable, typed, and safe to download. 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.
Artifact manifest
artifacts:
- logistics-bol-audit-summary.md
- logistics-bol-audit-evidence.csv
- logistics-bol-audit-review.json
signed_urls: true
retention: org_policy
Run this on Argo