Verify before done

No completion claims without fresh verification evidence. A claim made from memory, confidence, or a previous run is a guess wearing a status report.

The gate

Before claiming any status:

1. Identify the command that proves the claim.
2. Run it — fresh, complete, not a skipped or partial run. Complete relative to the dispatched scope; a subset scope is satisfied by the full subset, not the full suite.
3. Read the full output: exit code, failure counts, warnings.
4. Compare output to claim. Output contradicts it → state the actual status with the evidence. Output confirms it → state the claim with the evidence.

Skipping a step isn't efficiency; it's reporting fiction.

Fresh means after the last edit, not cache-busted: a cache hit on an unchanged package is valid evidence, and -count=1 belongs to merge gates, not to your proof. Under a zapply dispatch the command that proves the claim is the chunk's literal verify command — the suite and the repo-wide merge-gate floor belong to the caller, and re-running an identical command that already gave its answer adds nothing.

What each claim requires