Legal Hold Document Review with Claude Code: Result JSON Schema

A production playbook for legal hold document review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Legal operations teams

The problem

Legal operations teams need legal hold document review to run repeatedly against custodian exports, hold notices, and document metadata. 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 legal hold document review 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 legal hold 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.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "legal hold document review completed",
  "body": { "type": "legal_hold_review", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo