devrites-doubtlisted

# devrites-doubt: CLAIM → EXTRACT → DOUBT → RECONCILE → STOP Challenge one decision before depending on it. This is a pre-mortem, not a final review. ## When to use Introducing branching logic · crossing a module/service boundary · changing the data model · modifying auth/authz · changing a public API · touching migrations · changing a browser/user flow · relying on an assumption tests can't prove · working in unfamiliar code · claiming "this is safe", "this scales", or "this matches the spec". ## The cycle (copy this checklist) - [ ] **1. CLAIM**: state the claim in 1-3 sentences + why it matters. - [ ] **2. EXTRACT**: isolate the smallest reviewable artifact + its contract; strip your reasoning so the reviewer sees only the code/decision. - [ ] **3. DOUBT**: fresh-context dispatch `devrites-doubt-reviewer` with an `agent-packet/v1` and the adversarial objective *"find what's wrong; do not validate."* Follow [`agents.md`](../devrites-lib/reference/standards/agents.md). Inline does not satisfy independence; it is a labeled fallback only at the final capability-ladder rung. - [ ] **4. RECONCILE**: classify EVERY finding: contract misread | valid & actionable | valid trade-off | noise. **Doubt-theater check:** if two or more cycles find substantive issues but classify **zero** as actionable, the review is too agreeable. Sharpen the prompt or use a fresh reviewer. Accept a clean pass only after a genuine attempt to disprove the claim. - [ ] **5. STOP**: met a