Bulk PDF Processing with Claude Code: Artifact Delivery
A production playbook for bulk PDF processing in cross-industry operations using Claude Code: artifact delivery, run-scoped inputs, logs, typed results, and artifacts.
Audience: Document automation teams with batch jobs
The problem
Document automation teams with batch jobs need bulk PDF processing to run repeatedly against hundreds of PDFs, schemas, review rules, and output files. In cross-industry 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 bulk PDF processing, 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:
- bulk-pdf-processing-summary.md
- bulk-pdf-processing-evidence.csv
- bulk-pdf-processing-review.json
signed_urls: true
retention: org_policy
Run this on Argo