Privacy DSR Processing with Claude Code: Result JSON Schema
A production playbook for privacy DSR processing in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Privacy operations teams
The problem
Privacy operations teams need privacy DSR processing to run repeatedly against request forms, identity evidence, data maps, and response templates. 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 privacy DSR processing 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 privacy DSR processing, 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": "privacy DSR processing completed",
"body": { "type": "privacy_dsr_processing", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo