Required outcome
- Keep the public product page and $19 Stripe checkout live
- Release JSON only after Stripe confirms complete and paid
- Require the exact product Payment Link and USD amount
- Preserve a buyer-readable receipt and download path
Codex verification record / C-001
This case study shows how a coding agent was directed to add payment-verified digital fulfillment to a live product—and how every completion claim was checked against source, tests, and production.
Delegation-to-evidence chain
01 / The bounded task
Completion contract
A paid session from the exact $19 Payment Link may retrieve the workflow; missing, nonexistent, unpaid, or mismatched sessions must fail without exposing the asset.
02 / The review loop
Read the current source, tests, deployment binding, and live behavior before proposing a change.
Give Codex one bounded outcome, explicit non-goals, safety limits, and proof required before completion.
Examine the source diff and challenge unsupported APIs, missing failure paths, and claims that exceed the evidence.
Run the build and tests, then check production independently—including negative paths and expected commit state.
Authentication, external publication, credentials, and commercial claims remained human-controlled. The agent could implement and test; it could not redefine success.
03 / Claim-by-claim evidence
Automated verification
20 tests passedRendering, product contract, and protected-fulfillment behavior were checked together after the final source change.
Live failure behavior
400 · 403 · 404Missing input, unauthorized retrieval, and the former public asset each failed through the intended production path.
Commercial truth
$0 claimed revenueThe build is public evidence of engineering method—not an invented customer, testimonial, or sales result.
04 / What a paid evaluation can test
Can the agent/operator pair find the authoritative source and constraints?
Can it separate an actual defect from stale or indirect evidence?
Can it change only what the success test requires?
Can another reviewer inspect the diff, commands, and final behavior?
The case study exists so a hiring manager or buyer can judge the method directly. The next appropriate proof is a small paid evaluation with a written scope and objective acceptance test.
Need an agentic coding evaluation?
A practical paid trial can be time-boxed before any larger engagement or repository access is considered.