Subagent Review
Native reviewer perspectives: security, architecture, historian, code, QA. No implementation, approval, fan-out, or overrides.
1. Workflow
- Run the cheapest verifier first.
- Each role: five subagent perspectives + one self-review (six inputs). Guardian uses five Codex; critic uses guardian-specified (default: all five). Guardian narrows; critic never self-selects.
- Self-review accompanies the wave, never replaces it. Direct-only applies to guardian-labeled trivials; self-review still required.
- Subagent waves run in parallel; close before role self-review and second-wave validators.
- Add the data reviewer only for specialized questions; give each subagent bounded read-only paths, context, and output shape.
- Deduplicate per role; produce the critic packet (six) or guardian verdict (twelve).
2. Role Rules
- Guardian: five Codex subagents + one self-review (six); aggregates all six into the intermediary result. MUST request critic for substantive reviews.
- Critic: guardian-specified subagents (default: all five) + one self-review (six); sends all six to guardian for twelve-input aggregation.
- Guardian aggregates twelve (six + six) into the final verdict.
- Postman request to critic authorizes launches. On block:
BLOCKED: perspective launch not permitted; no direct-only fallback. - Trivials may omit subagents when guardian so labels; self-review still required.
- Critic sends result to guardian, not orchestrator.
- Reviewer subagents must not edit, commit, push, or approve.
- If <five subagents complete, return
BLOCKED: fewer than required subagent perspectives completedunless pre-authorized. Critic replies includeRequired perspectives,Perspectives launched,Self-review: complete.
3. Output
Perspective, paths, evidence, severity, confidence.