The verifier Shipped
A second dispatch, immediately after each worker, asking one question: did this specialist actually cover the ground its own specialty declared?
The verifier is not a second reviewer and not an editor. It reads the worker's findings against the specialty's own Verify criteria and answers whether the declared ground was covered. A fail drives a bounded, add-only re-review — it can find more, it cannot retract.
Add-only is the whole design
A verifier that could delete findings would just be a second reviewer holding a veto, and the run's output would be whichever of the two models was more confident. Add-only makes the verifier a coverage instrument rather than a judge, which is what lets it run cheaply, immediately, and per lane.
And it is not a stage at the end
It is tempting to draw this as "everyone reviews, then everyone gets verified." That is not how it runs. Each specialist is its own worker-then-verifier pillar and the pillars run concurrently under a cap, so a specialist is judged for coverage the moment it finishes. There is no checkpoint where the whole roster waits.