Document Classification with Claude Code: Result JSON Schema
A production playbook for document classification in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Operations teams routing large file intake
The problem
Operations teams routing large file intake need document classification to run repeatedly against mixed PDFs, emails, attachments, and routing labels. In cross-industry 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 document classification 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 document classification, 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": "document classification completed",
"body": { "type": "document_classification", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo