superstack-verifylisted

# superstack-verify "It ran" is not verification. **Evidence before claims, always.** Verify at the layer of the *claim*, not the layer below it. ## The gate Before any success/completion claim or expression of satisfaction: 1. **Identify** the command or observation that would *prove* this specific claim. 2. **Run it fresh, in full** (not a remembered earlier run; not a partial check). 3. **Read** the whole output — exit code, counts, the actual values. 4. **Verify at the layer of the claim.** Exit 0 / "deploy healthy" / "containers up" only proves the layer *below* the claim. If the claim is "the output is correct," look at the output. If it's "the page renders," look at the page. If it's "the definitions load," import them in the built artifact and count them. 5. **Only then** state the claim — as ledger lines: `Verified: <claim> — ran <command> -> saw <result>`, with anything unchecked under `Assumed:` or `PROVISIONAL`. If it fails, state the actual status with the output. ## Sharpen it - **Know what pass looks like before you run it:** pull the oracle from `.superstack/project.md` — the command *and* what green literally prints. Exit 0 with `3 skipped` is not the pass you meant. - **The counting environment is binding:** the oracle row's *Counts where* decides where green counts. Local green on a CI-counted claim stays `PROVISIONAL` until the environment of record agrees — quote it (e.g. `gh pr checks`). - **Discharge residuals — durable write first, delete second: