The model can propose that a requirement is done, but it can’t close one. A separate evaluator does that, and only when its checks pass against a fresh offline Surfpool chain. That split is the point: the thing writing the code never grades its own work.
The model can only propose. Only the checker can close a requirement, and three failed checks block it.
What “verified” means
A requirement is verified when four things hold. The pin verifies, meaning the pinned contract, verifier files and evaluator config still match their recorded digests. The requirement is in theproposed state. The evidence is bound to the pinned requirement, config, complete code inputs, verifier and snapshot bytes. And the run passed in offline-snapshot mode.
A run in forked mode is labeled as such and never closes a requirement.
What the check does
Every run starts a fresh offline Surfpool from the pinned snapshot, then evaluates eachdone condition:
The code under test is a saved copy of the inputs, not your live worktree, so edits you make mid-check don’t change the result.
Why the model cannot game it
When a task is created, OMS digests the contract (task.json), the verifier files and the evaluator config, and writes a pin file outside the workspace. The model only receives the code root. On every decision OMS recomputes the digests, and a mismatch makes the evaluator refuse. The runner also refuses to run if the code, verifier, snapshot or specification digest differs from the saved one.
The file guards block the model from editing pinned files in the first place. See File-read guards.
A failing check
A failing run moves the requirement back toactive and counts a reopen. At the default cap of 3 reopens, the requirement is blocked.
Check it yourself
/verify runs the independent offline verification with no model turn. /status shows requirements, proof and budget.