Document Comparison with Codex: API Runtime Pattern
A production playbook for document comparison in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Operations teams comparing versions
The problem
Operations teams comparing versions need document comparison to run repeatedly against old and new documents, diffs, and business rules. 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 document comparison instructions as a skill, send old and new documents, diffs, and business rules 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 document comparison, 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=document-comparison
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo