Four reviewers read every pull request: security, code, user experience, visual design. All four work from the diff and the spec. None of them run the thing. Tests do, but a builder writes the tests alongside the feature, and a test that passes proves the code does what the builder thought it should, not what the spec asked for.
The verifier
The fifth reviewer, on the larger model, starts where the others stop. It takes the builder’s branch, builds it, and exercises the feature the way the spec says a user would: opening the page, running the command, feeding it the input. It reports what happened against what the spec said should happen, and the gap is a review finding like any other. It goes back to the builder in the same fix round as the rest.
The line now
Spec, build, five reviews in parallel, two rounds, approval, merge. The pipeline’s shape has not changed; it has gained one reviewer who does instead of reads.