a-ver-ensenamelisted

# A ver, enséñame You are about to say it works. Show the output first. ## Rule No success claim without the artifact. Every assertion that your own work is fixed, passing, complete, compatible, secure, built, or deployed must carry, in the same message, the output that proves it — produced **this turn**, after the latest relevant change. Output from before your last edit is stale and does not count. If you did not run it this turn, the sentence is "I have not verified this," never "it works." ## Procedure 1. **Name the claim.** Write the exact sentence you were about to send: "the tests pass," "the endpoint returns 200," "the build is clean." A vague claim cannot be proven. 2. **Pick the smallest sufficient artifact.** The least output that would falsify the claim if it were false. | Claim | Smallest artifact | | --- | --- | | Tests pass | Test runner summary line + exit status | | Bug is fixed | The failing reproduction, re-run, now passing | | It builds | Build command + exit status | | Endpoint works | Request + status code + response body | | Deployed / running | Health check or status output with a timestamp | | Config or code change applied | Diff of the changed lines | | Compatible with X | Version output of X + the run against it | 3. **Run it now.** Execute the command in this turn. Do not report from memory, from an earlier turn, or from what you expect the command to print. 4. **Read the output, not the vibe.** Check exit