Files
esh-pfi-infrastructure/persistent-memory.d/2026-09-21-the-memorisation-control-that-shipped-broken-is-now.md
T

1.3 KiB
Raw Blame History

[2026-09-21] The memorisation control that shipped broken is now committed, and it turned a 12× red flag into a clean pass.

⭐⭐ The memorisation control that shipped broken is now committed, and it turned a 12× red flag into a clean pass. memorization_check.py used base-unadapted as its negative control; base writes summary while the adapted arms write pastiche, so it cannot collide with a register it does not imitate and its zero is unearned. The lv-hemingway gate established this, computed the correct control (the author's own held-out text) by hand, and left no instrument — so the finding was not reproducible. Now --train-only --heldout-reference, refusing the unsafe combination, validated by reproducing Hemingway's hand-computed row to the digit. ⭐ On McCarthy it is the difference between reporting ckpt450 as memorising (0.12 vs base 0.00 = 12×) and clean (0.12 vs the author's 0.12 = 1.0×). ⭐ And the "the register makes collisions inevitable" story that was FALSE for Hemingway (0.01) is TRUE for McCarthy (0.12) — measured, not assumed; neither number transfers between authors. Also new: show_memorisation_matches.py, because rate and exposure are different questions and the reading was hand-done too. Commits b4ba731 7eadbd6.