REVIEW holds the patch.
At the review stage, approve or deny the example. The shared-code operation cannot execute while the decision is pending.
Interactive product walkthrough
A controlled
Codex Task.
Follow a Codex task through expected work, a human decision, a protected boundary, and independent verification. This is an illustrative simulation using sample data, not a live repository or persisted Task.
Task / account-settings
CodexAdd account notification preferences.
Keep authentication unchanged. Run the declared checks.
Task boundaries
EXPECTEDsrc/accounts/preferences.tsAwaiting proposal
REVIEWsrc/shared/settings.tsRequires human judgment
PROTECTEDsrc/auth/session.tsMust remain unchanged
01 / Task
A boundary before work begins.
Scope and verification criteria are frozen before controlled work. No repository mutation has occurred.
Illustrate a verification outcome
These controls change the example, never a real Task or verification plan.
What to look for
Permission, execution, and proof are separate.
PROTECTED stays blocked.
The authentication proposal is outside the Task boundary. It never becomes a human-overridable permission in this example.
Execution can still fail verification.
Explore the three outcomes. A failed test is FAILED; an unavailable verifier executable is UNCERTAIN.
Preserved interactive V3 CRM regression proof
This older fictional frontend-only walkthrough is retained as a regression reference. It is separate from the supported Codex alpha above.
ArgosFictional workspaceSandbox
Duplicate customer match
Customer Operations AgentSubscription Support Resolution
- External mutations
- 0
- Current stage
- Detect
- Fictional time
- 00:03
Exception contained. External mutations, messages, and billing changes remain zero.
Action intercepted
Argos contained an ambiguous customer update
The agent reached an instrumented checkpoint before any CRM, billing, or notification change was released.
2plausible records
Missingverified customer ID
Billingbusiness impact
0external mutations
Argos stopped the action before the fictional CRM changed.
Your next engineering Task
AI is getting more capable.
Your supervision model should too.
Start with Codex, one repository, and a boundary you can inspect.