Multi-instance and multi-pass review
Why a session reviewing its own work misses errors, how to give an independent reviewer only the artifact and the criteria, and how verification passes, rubric-based evaluators and multi-instance voting turn review findings into reliable, routable signals.
Design multi-instance and multi-pass review architectures
~8 min read · 11 practice questions ·
What the exam expects
- Explain why a model reviewing its own output in the same session misses errors, and why self-review instructions or extended thinking do not fix it.
- Use a second, independent Claude instance (a separate session, reviewer subagent or separate API call) that receives only the artifact, the requirements and the criteria.
- Separate writers from testers, and scope a reviewer to correctness and requirement gaps.
- Add a verification pass that checks each finding and records confidence and evidence so findings can be routed.
- Use a separate evaluator instance with a rubric, and choose aggregation thresholds when several independent reviewers vote.
Key terms: self-review (the generating session checking its own work); independent review instance (a reviewer without the generator's reasoning context); verification pass (a step that confirms or drops candidate findings); LLM-as-judge (a separate instance grading output against a rubric); voting (running several reviewers and combining their flags).
Key facts
- Detail
- The generator retains its reasoning and is less likely to question its own decisions
- Detail
- Independent instances catch more than self-review instructions or extended thinking
- Detail
- Only the diff and the criteria you give it
- Detail
- Gaps return to the implementing session for fix and re-review
- Detail
- Own context window, system prompt, tools and permissions
- Detail
- One Claude writes tests, another writes code to pass them
- Detail
- Flag only gaps affecting correctness or stated requirements
- Detail
- Find, Verify, Rank, Post
- Detail
- Each step a separate API call you can log, evaluate or branch on
- Detail
- Single call, 0.0-1.0 scores plus pass-fail, most consistent with humans
- Detail
- Different vote thresholds balance false positives and negatives
Sources for this section (7)
- Exam guideeverpath-course-content.s3-accelerate.amazonaws.com (opens in a new tab)
- Best practices for Claude Codecode.claude.com (opens in a new tab)
- Create custom subagentscode.claude.com (opens in a new tab)
- Code Reviewcode.claude.com (opens in a new tab)
- Prompting best practicesplatform.claude.com (opens in a new tab)
- How we built our multi-agent research systemwww.anthropic.com (opens in a new tab)
- Building effective AI agentswww.anthropic.com (opens in a new tab)
- Why is a separate reviewer call that receives the generator's transcript not truly independent?
- When should a team choose a reviewer subagent over a second terminal session?
- What does Code Review's verification step do?
- Why might a team flag on any single reviewer for payment code but require a majority for style?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Claude Certified Architect - Foundations pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 30 lessons of the Claude Certified Architect - Foundations guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams
Practice for the Claude Certified Architect - Foundations exam
Certifyforce is an independent study resource and is not affiliated with, endorsed by or sponsored by Anthropic. Claude is a trademark of Anthropic.