Gated build — adversarial multi-agent construction

For work where being plausibly wrong is expensive. One agent — however disciplined — cannot reliably catch its own errors: the blind spot that produced the bug reviews the bug. Quality comes from independence: a second agent whose job is to say NO-AGREE, grilling every step until it earns an explicit APPROVED.

The economics: compress everything agents read (specs, notes, grill prompts), so you can afford a second agent to disagree. Efficiency funds redundancy.

1. Casting the roles

Three roles: Orchestrator (holds the anchor doc, casts the others, integrates), Author (drafts code/design), Reviewer (grills to APPROVED). Cast by task, not by habit: