SOC 2 Evidence Pack Assembly with Claude Code: Result JSON Schema

A production playbook for SOC 2 evidence pack assembly in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Compliance teams

The problem

Compliance teams need SOC 2 evidence pack assembly to run repeatedly against control evidence, screenshots, exports, and audit notes. 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 SOC 2 evidence pack assembly 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 SOC 2 evidence pack assembly, 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": "SOC 2 evidence pack assembly completed",
  "body": { "type": "soc2_evidence_pack", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo