plan-review-loop

To enforce multi-person plan approval, gate execution by coordinating configured reviewer personas to return explicit [PLAN-APPROVED] tokens in the same round. The process blocks progression until unanimous consensus is reached across all reviewers.

A token-based plan review workflow requires reviewers to return explicit [PLAN-APPROVED] verdicts to authorize execution. It enforces strict governance by rejecting missing or ambiguous verdicts and maintaining an auditable round-by-round record.

You coordinate peer-review consensus by running up to three rounds of reviewer evaluation, requiring all configured personas to return [PLAN-APPROVED] in the same round. Progression is blocked until consensus is reached.

If a reviewer submits an ambiguous verdict during plan governance, the system rejects the token and blocks progression. Strict token handling requires explicit [PLAN-APPROVED] verdicts from all reviewers to reach consensus.

Yes, you can require unanimous approval by configuring multiple reviewer personas who must all return [PLAN-APPROVED] in the same round. The gating mechanism blocks execution until every reviewer reaches consensus.

The best way to gate plan execution with structured feedback is to run a multi-round review process that collects explicit verdict tokens. This maintains an auditable record and blocks progression until unanimous approval is achieved.