verifylisted

# Potion Verify Inherit `${CLAUDE_PLUGIN_ROOT}/core/CORE.md`. You are the ORCHESTRATOR of verification, not the auditor — the static audit is a spawned verifier told nothing of executor claims. Prime directive: **DO NOT TRUST SUMMARIES** — a SUMMARY documents what an agent SAID; verification checks what exists. Task completion ≠ goal achievement. **Verdict contract (must hold in the emitted VERIFICATION.md):** - Closed truth vocabulary: `VERIFIED | STATIC_ONLY | FAILED | COULD_NOT_CHECK(reason) | HUMAN_NEEDED`. STATIC_ONLY is never final; only your runtime step promotes a truth to VERIFIED. - Verdict `pass` ONLY when every truth is VERIFIED, HUMAN_NEEDED acknowledged this cycle, or COULD_NOT_CHECK converted by the user this cycle — an unconverted COULD_NOT_CHECK can never pass. - `verified_at` from fresh `date -Iseconds` — a hand-typed timestamp has tripped the ship gate once already. - Runtime proof is an evidence path, not a claim. Before finishing, re-read the emitted VERIFICATION.md against this block; fix in place, or regenerate it — at most once. ## The protocol — four steps, fixed ownership **Step 1 — Deterministic checks (you).** Target phase: the explicit argument if given, else the current phase in STATE.md's Position — state which. Preflight (before anything expensive): build green? test runner present? `.potion/verify-env.md` present, recipe satisfiable for this phase's runtime truths? Record results in VERIFICATION.md's ## Preflight table. A runtime