double-check

# /double-check Multi-pass re-verification of a plan, output, decision, or document — re-read from scratch, challenge assumptions, propose improvements, and iterate until solid. > **Re-Read & Improve Protocol — not a single-pass gate.** The agent re-reads the target fresh, challenges each part, proposes improvements, and iterates. Each pass tightens the result. > **Structured execution spec:** [`protocol.yon`](protocol.yon). It carries the five phases, the scope/verdict gates, and the rules as validatable records; this file is the explanation. Keep the two in sync — edit one, update the other and refresh the `@STAMP` date. > **Caller Options.** Before executing, run the Caller Options protocol (`caller-options/SKILL.md`): triage this invocation for material optionality across the venues and modes declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options to the caller. A resolved-invocation marker means COP already ran — execute the fixed combination directly, do not re-enter COP. --- ## Phase 1: Scope Identify what is being double-checked — a plan, an output, a decision, a document. Load it fresh. Do not rely on prior context or cached understanding. **Gate:** Cannot double-check without a clear target. If the target is ambiguous, ask before proceeding. --- ## Phase 2: Fresh Re-Read Re-read the target from scratch as if seeing it for the first time. Go back to the **actual sources** — files, code, docs. Do not verify f...