Reviewer amnesia: the fresh context that beats the tired one

Build lab (Module 9, L9.5): the best reviewer is the one who forgot everything except the acceptance criteria. The builder that wrote a 200-step change reviews its own diff and approves the bug it introduced at step 40, because it remembers meaning it -- 2 of 4 calls right and 0 of 2 real bugs caught, exactly the score of a rubber stamp that reads nothing, from 2,713 words of payload. The amnesiac reviewer is a zero-context fork: the 28-word brief plus the diff, 234 words in total, 11.59x less, and it is right on 3 of 4, catches 2 of 2 real bugs and runs 20 checks where the other two run 0 -- 5 checks per diff, executable acceptance first (3), then the rubric vetoes (2), judgment last. It is not free: it pays 1 false rejection (the overfix that also ships an unasked-for helper), so its precision on its own rejections is 0.667. An untestable brief is refused by name (brief acceptance untestable) rather than filled in. Read-only is structural: told to just fix the off-by-one while it is there, the reviewer holds no write token, the write is REFUSED 1 of 1 times, and the file is untouched. The merge gate reads the schema, never the prose: 5 calls, 1 merges, 4 block, including the stale one after the brief's fingerprint moves from dd6960b9 to 009e4c01. In-memory only; scripted reviewers and a scripted writer, words as the token proxy, no threads or provider call.

This Harness Engineering lesson is part of a paid plan. Sign in with a plan that includes this course to read it.