Privacy DSR Processing with Codex: API Runtime Pattern
A production playbook for privacy DSR processing in cross-industry operations using Codex: api runtime pattern, 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
Package the privacy DSR processing instructions as a skill, send request forms, identity evidence, data maps, and response templates as run-scoped inputs, execute with Codex, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. 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.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=privacy-dsr-processing
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo