postcheck-verifier

# postcheck-verifier **P0 — Reality-Proven Outcome Verification** **Seal:** DITEMPA BUKAN DIBERI · 2026-03-27 --- ## Purpose Every agent reports success too easily. `exit code 0` means the command ran, not that the goal was achieved. The `postcheck-verifier` exists because: > **"The map is not the territory. The exit code is not the outcome."** The opencode catastrophe is a textbook example: every git command returned success, every merge reported completion, and the final state was catastrophic destruction. Success was assumed from the command's return code, not from the system's actual state. **Why this is P0:** Closing this gap adds an estimated +20% to AGI readiness (the single largest jump in the P0 set). `postcheck-verifier` is what separates a tool-using automaton from an AGI agent. --- ## The Verification Hierarchy Not all verification is equal. Use the right level: | Level | What It Proves | Example | |-------|---------------|---------| | **L0 — Exit Code** | Command ran | `grep` found something | | **L1 — Output Check** | Output matches expectation | `docker ps` shows running container | | **L2 — State Probe** | System state changed as intended | HTTP endpoint responds correctly | | **L3 — Functional Test** | The feature actually works | User can log in, API returns correct data | | **L4 — Reality Proof** | The change achieved the goal in the real world | The system does what Arif asked | **Minimum standard for arifOS:** L2 for routine ops. L3 for code c...