Doubt-driven review

Non-trivial when

• Branching logic or cross-module boundary changes
• Properties types/compiler cannot verify
• Irreversible deploy, migration, or public API change

When not to use

• Renames, formatting, obvious one-liners

Cycle

1. CLAIM — decision + why it matters (2-3 lines)
2. EXTRACT — artifact + contract only (no reasoning journey)
3. DOUBT — fresh review with adversarial prompt ("find issues, do not validate")
4. RECONCILE — classify: contract misread / actionable / trade-off / noise
5. STOP — trivial findings only, 3 cycles max, or user says ship