docs(archive): the set-judge, and what it found on first use
Archive entry for the set-judge build. The entry worth reading later is not the tool but its first run: it was built to collect go/no-go verdicts and what it actually established is that the OPAL-26 masters are fine and every middle CUT is wrong — nine boundaries ear-verified in one sitting, with errors of 3 to 21 seconds that two automated detectors had certified clean. Also records the four silent traps the build walked into (heads are intros; a green build with dead playback; three verification probes that tested nothing; two latent bugs surfaced by reusing existing components).
Showing
Please
register
or
sign in
to comment