Arithmetic, not a re-reading of results. Criterion 1 needs the candidate's in-band
rate to beat base's 0.89 by more than the 0.200 floor -- so it needs in_band >
1.09, and a rate cannot exceed 1. A PERFECT adapter, every one of 240 generations
inside the 90-140 band, scores +0.11 and fails by 0.09.
So "both candidates failed axis C" carries zero information about either candidate.
That verdict was determined before a single generation existed. It is my error.
The cause is specific: section 6 transcribed score_beats.py's v1 criteria, which the
operator AMENDED on 2026-09-15 -- three weeks before this corpus was built -- for
exactly this reason. Its own docstring: "NOT carried into v2: in-band (unresolvable
-- base maxes it) and on-beat."
The governing rule reverts to the operator's v2: axis C is ran-on only. That is the
rule they ratified and the rule lv-hemingway shipped under. Reverting a
transcription error to its source is not threshold-shopping; the source is older
than the data.
It does not rescue ckpt450 either. Under the corrected axis C its ran-on is +0.19
against a 0.200 floor -- a pass by 0.01, inside the noise the floor exists to
describe, and not a pass worth shipping on an author in copyright with a living
estate.
AMENDMENT 3 therefore gates two more arms on the SAME frozen fixture, seeds and
rule -- ckpt300 (epoch 0.65) and ckpt225 (epoch 0.49), both on disk because
--save-total-limit 60 kept all 56 checkpoints -- since the damage grows
monotonically with epoch and the voice may arrive before it does.
And it sets the ship bar BEFORE those arms exist: voice clearing the pairwise floor
on both reads, memorisation at or near the held-out author's 0.12 with every match
read, and ran-on delta AT MOST 0.100 -- half the measured floor, not merely inside
it, because a rate that clears a noise threshold by 5% of that threshold has not
been shown to clear it. If nothing clears all three, lv-mccarthy is parked pending
a retrain, and that is the report rather than a softer bar.
Vuong Hoang
43a8d7409e