check

# check "Check" is the expeditor's call: every plate gets looked at before it leaves the pass. Not the cook's word that it's right, not how it looked ten minutes ago - this plate, looked at now. This skill is that look, applied to any claim of done: run the thing, read the output, then say what the output says. **Core principle:** evidence before claims, always. A completion claim without fresh verification is not optimism, it is a false report. **Violating the letter of this rule is violating its spirit.** ## The iron law No completion claim without fresh verification evidence in this same response. Have not run the proving command since the last change? Then "it works" is not available to you, and neither are its synonyms, paraphrases, or implications. ## The gate Before any claim of success, satisfaction, or readiness: 1. **Name the command that proves the claim.** "The script works" is proved by running the script, not by running its prettiest component. 2. **Run it, fresh and whole.** After the last change, the full thing: the actual script, the whole suite, the real build. Stale runs and partial runs prove nothing about the present. 3. **Read the output and the exit code.** All of it. Count the failures yourself. 4. **Compare claim to evidence.** Output contradicts the claim? The evidence wins; report the actual state. 5. **Then claim, with the evidence attached.** Quote the command you ran and its actual output lines in the report, not a paraphrase of them. "All...