This loop puts a dedicated critic inside the cycle to attack the design until it survives scrutiny or is knowingly accepted with its trade-offs.
The cycle raises the strongest objections (scaling, security, cost, edge cases, maintainability) and, for each one, either fixes the design or records a conscious decision with rationale.
It repeats until no serious objection is left open.
No critique is silently ignored: it is either resolved or accepted with a recorded reason.
When to use
- When reviewing a design, RFC, or architectural decision.
- When you want to stress-test the proposal before building it.
- To record consciously accepted trade-offs.
How to use
Run the loop asking it to act as a devil’s advocate, raise the strongest objections, and for each one either fix the design or record an accepted trade-off with rationale.