adversarial-review

Adversarial Review

Gate Contract

• Enter only from an explicit user request; never infer the need from risk, complexity, verification gaps, or another workflow.
• Start BLOCKED with distinct Reviewer and Editor agents.
• Prefer real isolated subagents for the Reviewer and Editor when the host can dispatch them; fall back to inline role-play with ISOLATION: simulated disclosed. Follow Subagent Dispatch.
• While BLOCKED, do not finalize, approve, commit, publish, or externally share the artifact.
• APPROVED is review evidence, not external-action authorization.
• Set no total round or cycle limit. Continue by review state under Review Loop Contract.
• Keep the active finding ledger in Reviewer–Editor handoffs; do not write report files during intermediate rounds.
• Reviewed artifact changes invalidate APPROVED; return to BLOCKED and resume the same numbered review history.
• No independent Reviewer: fail closed.

Roles

• Coordinator: Pins scope, gate, routing, and verdict; may be Editor, never Reviewer.
• Reviewer: Read-only; separates findings, required outcomes, and optional remedies under the shared principles.
• Editor: Audits adequacy, minimal resolution, blast radius, and proportionality before accepting, narrowing, rejecting, acknowledging, or escalating; never self-approves.

Reuse the Reviewer. A replacement receives the complete state, artifact, available diff, round number, and finding IDs.

For multiple viable decisions, fixes, or plans, remain BLOCKED and use Decision Consensus Gate before choosing one.

Workflow

0. Resolve dispatch mode

Detect the host's dispatch capability, verify the dispatch path is actually ready (on Pi: the pi-agent carrier is registered and spawnable; on Codex: the host can spawn an agent process), record the mode and per-role readiness once per run, and print the dispatch metadata table to the user as the first output of the run — before any role pass — as specified in Subagent Dispatch. If all roles are ready, enter SUBAGENT mode without asking; if any role is missing, present the table and ask the user whether to proceed in INLINE-FALLBACK, and enter it only on explicit confirmation. Never enter the loop on an unverified dispatch path. The Review Loop Contract, finding ledger, and report format are identical in both modes; APPROVED reached under simulated isolation carries that caveat.