padosoft-evidence-boundarieslisted

Use this skill when something is being declared done, safe, covered or production-ready and you need to know what actually proves it: a release or compliance gate, a security or DR claim, a "CI is green so we can ship", a "the job succeeded", a "the tests pass so it works", a coverage or mutation number, a signed artifact, an integration verified against an emulator or a mock. It names the claim, names what would prove it, and finds the gap where a cheaper artifact was accepted in place of the expensive one. Do not use it to write tests (padosoft-test-integrity), to build a CI workflow (padosoft-ci-workflow-gates), or to debug a failing check — this is about whether a passing one means anything.
padosoft/skills · ★ 1 · AI & Automation · score 80

Install: claude install-skill padosoft/skills

# Evidence boundaries Almost every false "done" has the same shape: a claim was made about the expensive thing, and a **cheaper artifact** was accepted as proof of it. The artifact is real, it was produced honestly, and it does not demonstrate the claim. **The rule: name the claim, then name what would prove it. If what you have is cheaper than the claim, the claim is asserted, not proven.** --- ## 1. The substitution table The recurring pairs. Read the middle column as what you are entitled to say, and the right one as what will be said anyway. | What you have | It proves | It does **not** prove | |---|---|---| | A green run against an emulator or compatible implementation | the request/response shape | the real provider's identity, policy, retention, encryption | | A static graph, topology or config validation | the transitions are **declared** consistently | that anything ever reached them | | A write request the API accepted | the option was transmitted | that the provider applied it — read it back | | A signature on a manifest | the manifest is authentic | the content the manifest points at | | A digest field, a reference, a ticket id | something was **named** | integrity: nobody recomputed anything | | Deployment files, linted and secret-scanned | they parse | that a scrape, an export or an alert works | | An injected or faked client in a test | your control flow | the real storage, transport or locking semantics | | A parsed report from an external tool | the too