Artifact Delivery with Claude Code: Result JSON Schema
A production playbook for artifact delivery in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Teams whose agents create files customers download
The problem
Teams whose agents create files customers download need artifact delivery to run repeatedly against reports, exports, patches, PDFs, and manifests. 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 artifact delivery 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 artifact delivery, 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": "artifact delivery completed",
"body": { "type": "artifact_delivery", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo