review3-confirm

Consensus validation forces a closed-loop outcome for each Review-Reply item by verifying defender reasoning and resolving disputes into explicit states like implementation, deferment, denial, or clarification, preventing unresolved ping-pong cycles.

You confirm defender replies by reading the review document, checking stage status, processing Reply subblocks, and writing Confirm results via batch-update to finalize each item as implemented, deferred, denied, or requiring clarification.

The best way to handle real disputes is initiating user arbitration, which creates an on-the-spot decision loop to capture the final ruling and record the arbitration outcome, ensuring the dispute reaches a verifiable closure.

Stage-gated processing requires this sequence to enforce anti-passing guardrails, ensuring stage integrity by forbidding legacy waiting statuses and preventing the workflow from advancing before prior review replies are fully resolved.

Yes, you can batch update confirmed consensus outcomes and apply optional backlog archiving simultaneously when processing Review-Reply subblocks, ensuring all final verdicts and deferred items are recorded in a single closed-loop operation.

Items marked as requiring clarification trigger a clarification-first branch that outputs specific content for the defender to address, requiring a rerun of the review2-reply stage before confirmation can be attempted again.