doubt-driven-development

Fresh-context adversarial review is a verification technique that tasks an independent reviewer with disproving a non-trivial decision artifact against a defined contract to ensure correctness before high-stakes execution.

Define an artifact and contract, spawn a fresh-context reviewer whose goal is to disprove the artifact, reconcile findings, and only stand by the decision if it survives the adversarial review process.

Apply doubt-driven review for high-stakes outputs, unfamiliar code, security-sensitive changes, or irreversible operations, but skip it for mechanical edits where extra verification is not justified.

The workflow follows five steps: ARTIFACT to draft the decision, CONTRACT to define constraints, DOUBT to spawn an adversarial reviewer, RECONCILE to address findings, and STAND to finalize the verified decision.

Enforcing fresh-context adversarial review prevents confident outputs from hiding unexamined assumptions by requiring an independent reviewer to actively disprove the artifact before any non-trivial decision stands.