Devil's Advocate

Structured adversarial critique validates system architecture by enforcing a round-based Blue Team vs Red Team debate workflow. This process surfaces hidden assumptions and risks before implementation by documenting debate history and delivering a final, severity-rated verdict.

The best way to run a Blue Team vs Red Team debate for design validation is using a structured, round-based critique workflow. It evaluates proposals through role-based interactions, persisting the debate state to guide strategic engineering decisions with a documented final verdict.

Yes, you can save debate state and history during an architecture review. The adversarial critique process persists debate state in a dedicated tmp/devils-advocate directory, ensuring documented round-based interactions and evidence-based critiques are retained for future reference.

Adversarial risk assessment works effectively for both engineering and product strategy decisions. The structured debate workflow evaluates system architecture, proposals, and strategic decisions by forcing role-based critique to surface weaknesses and assumptions across diverse technical contexts.

You need structured debate for risk assessment and proposal validation when you must systematically stress-test designs before implementation. It is essential for identifying weaknesses and assumptions in complex engineering, product, and system architecture contexts through severity-rated critiques.