Prove Claim

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If the proving command did not run just now, in this session, the claim is unavailable to you. An unverified claim isn't optimism — it's a false statement.

The Gate Function

Before any status claim or expression of satisfaction:

1. IDENTIFY — which command proves this exact claim? (Commands come from docs/agents/project.md. Missing? Say so, suggest configure-repo, and identify the command manually.) When the claim is that some record now holds a change — a ticket, a remote, a stored row — the proving command is the read, never the write that made it, so IDENTIFY resolves to a pair and the write alone can never satisfy this gate.
2. RUN — execute it fresh and complete: the project's whole suite command, not a path- or pattern-scoped subset of it. No cached results, no "it passed earlier". A scoped run's totals are that scope's, never the suite's — quote them as the suite's and the claim is false even though a real command really ran.
3. READ — the full output: exit code, failure count, warnings. Not the last line.
4. CONFIRM — does the output actually support the claim? If no: report the real status, with the evidence. If yes: make the claim, with the evidence.