Comercio Exterior: Pedimento And Customs Document Review with Claude Code: Artifact Delivery
A production playbook for pedimento and customs document review in comercio exterior operations using Claude Code: artifact delivery, run-scoped inputs, logs, typed results, and artifacts.
Audience: Comercio exterior teams and customs operations software builders
The problem
Comercio exterior teams and customs operations software builders need pedimento and customs document review to run repeatedly against pedimentos, facturas, packing lists, COVE/MVE documents, and compliance rules. In comercio exterior 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 pedimento and customs document review, 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:
- comercio-exterior-pedimento-review-summary.md
- comercio-exterior-pedimento-review-evidence.csv
- comercio-exterior-pedimento-review-review.json
signed_urls: true
retention: org_policy
Run this on Argo