prove-itlisted

# Prove it A passing type-check is not proof. A read of the source is not proof. An agent's report is not proof. **Proof is an artifact captured from the running system after the change.** This skill turns "it should work" into either evidence or an honest admission. ## The rule > Never claim a change works until you have captured an artifact from the running > system that would look different if the change were broken. The counterfactual is the whole test. If your evidence would look identical on a broken build, it is not evidence. `tsc` passes on a page that 500s. `grep` finds a tracking snippet that a CSP silently blocks. A subagent reports six files fixed that were never written to disk. ## Procedure **1. State the claim.** One sentence, falsifiable, naming the environment. Bad: "the fix works". Good: "GET https://example.com/pricing returns 200 and the page contains 'Pro plan' on production." **2. Pick the evidence.** Use the table below. If two kinds are cheap, take both: one positive (the new behaviour appears) and one negative (no console error, no failed request). **3. Capture it.** Run a tool, save the output to a file. Never paraphrase from memory - quote the captured bytes. **4. Return a verdict.** `PROVEN`, `NOT PROVEN`, or `UNPROVABLE HERE`, with the artifact path and the decisive line. Never end a task with an unqualified "done" when the verdict is anything other than PROVEN. ## Evidence table | Claim | Minimum acceptable proof | Tool | |---|---|---