Subagent Verification Loops

A subagent verification loop sends the output of one agent to another agent with fresh context.

The reviewer sees the product, not the complete reasoning history. It can ask:

• Is this correct?
• What edge cases are missing?
• Can the solution be simplified?
• Are there security problems?
• Does it satisfy the specification?
• Are there obvious defects?

The reviewer has no need to defend the implementation because it did not create it.

A complete loop uses three roles:

The implementer creates the first version of the code, workflow, report, design, or process.

The reviewer receives the output in a fresh context and evaluates it against explicit criteria.

If the reviewer finds problems, a third fresh agent receives the output and the issue list. It resolves the defects without inheriting the implementer's full reasoning history.

The sequence is:

1. Implement.
2. Pass the output to a fresh reviewer.
3. Review for correctness, edge cases, simplification, and security.
4. If no problems are found, approve.
5. If problems are found, pass them to a fresh resolver.
6. Resolve the issues.
7. Test the corrected output.
8. Repeat verification if required.

This architecture creates cleaner separation of responsibilities.