Codex Rule Ledger
Evidence desk / Build Week 2026
Case 001Validation drift
Recorded case index
Two keyless audits. Same deterministic contract.
SYNTHETIC_SANITIZEDRepository-owned synthetic case; not a captured real session.
Captured instructions, mechanically adjudicated
Codex Rule Ledger
Reconstruct the instruction chain once. Split observable rules from subjective prose. Follow every result back to the supplied event.
ProvenanceLOCAL_CAPTURE_UNATTESTED
Audit inputREADY
Selected chain4 sources
Evaluated4 rules
Ledger SHA-256
4fc6eab5…1bc3baFast path
Judge it in 60 seconds
- 01
Read the reconstructed instruction chain
- 02
Open the contradicted typecheck rule
- 03
Export the digest-bound ledger
Verdict keyEvidence decides admissibility
- Supported
- Affirmative supporting evidence.
- Contradicted
- Affirmative conflicting evidence.
- Not evidenced
- Neither failure nor compliance; the supplied evidence cannot support either verdict.
- Not applicable
- The trigger affirmatively did not occur.
01
Root → launch CWDInstruction chain
- GLOBAL
$CODEX_HOME/AGENTS.md - PROJECT
$PROJECT_ROOT/AGENTS.md - PROJECT
$PROJECT_ROOT/apps/CODEX.md - PROJECT
$PROJECT_ROOT/apps/web/AGENTS.override.md - BYTE LIMIT
$PROJECT_ROOT/apps/web/demo/AGENTS.md
One chain, captured at launch. No per-file instruction fiction.
02
5 extractedObligation ledger
1 supported 1 contradicted 1 open
03
boundEvidence inspector
Contradicted
typecheck-no-completionDo not claim completion after npm run typecheck fails.
Instruction source
Do not claim completion after `npm run typecheck` fails.
Linked evidence
event-typecheck-failurenpm run typecheck exited 1
sequence 20event-completionCompletion was claimed after the failed command
sequence 30