---
title: "Adversarial Review · agent topology · Agent Fieldbook"
url: https://agentfieldbook.org/design/topologies/adversarial-review/
description: "Producer emits, critic rebuts, arbiter (optional) resolves. Loops until convergence or timeout. Widely used in code-review + reasoning-verification."
section: "Design · Topologies"
source: Agent Fieldbook — generated from the published page
---

# Adversarial Review

Producer emits, critic rebuts, arbiter (optional) resolves. Loops until convergence or timeout. Widely used in code-review + reasoning-verification.

Verified against [arxiv.org](https://arxiv.org/abs/2502.02533)

- [arxiv.org](https://arxiv.org/abs/2502.02533)

An adversarial-review topology pairs a producer that emits work with a critic that tries to refute it, and optionally an arbiter that resolves the two, looping until the critic can no longer find a flaw. Building the check into the loop raises quality: nothing ships until it survives a dedicated adversary. It is the shape behind self-checking coding and writing agents. In anatomy terms it is two opposed cores plus an optional judge, iterating.

## In the anatomy

A producer core emits; a critic core attempts to refute; an optional arbiter core resolves; the loop repeats until convergence; effectors commit only the arbiter-approved output.

## At a glance

| Field | Value |
| --- | --- |
| Pattern | Adversarial Review |
| State model | session |
| Example | Anthropic red-team pairs· code-review agents |

## Common use cases

## Strengths

## Weaknesses

## Basis

Description, use cases and trade-offs: Field Book analysis, synthesised from established agent-architecture literature.

## Verified against

- [https://arxiv.org/abs/2502.02533](https://arxiv.org/abs/2502.02533)

The corpus does not rewrite vendor documentation. Where copy is quoted verbatim it is marked as such and attributed to its source.