The agents closest to a build share its context, and they share its blind spots. That is why Fusion brings in fresh QA after jury pass 2: first as a quick ship-readiness filter, and then as a required independent deep audit.
Jury pass 2 answers a comparative question: did the chosen synthesis preserve and improve the candidate evidence? QA asks a release question: what could still make this unsafe, incomplete, or misleading?
Context is useful until it becomes anchoring
Candidates know why they made each choice. Judges know why they preferred one path. Integrators know which compromises held the final together. That knowledge can make a defect feel intentional.
A fresh reviewer begins from the frozen contract, baseline, risk surface, final artifact, and evidence. It does not inherit the tournament's emotional investment.
Two depths serve different decisions
QA Review is a light readiness filter. It catches obvious blockers and confirms the handoff is coherent.
QA Audit is the required deep pass before a Build result can become ready to ship. A failure routes back to bounded repair and re-verification.
Source ledger
- Fusion run lifecycle, build and review phase steps 15–17.
- Fusion planning model, section 6.
- Fusion MVP PRD, FR-19.