diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/campaign/CASCADE_ABLATION_PLAN.md | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/campaign/CASCADE_ABLATION_PLAN.md b/docs/campaign/CASCADE_ABLATION_PLAN.md index 5bb1d73..68d7bc2 100644 --- a/docs/campaign/CASCADE_ABLATION_PLAN.md +++ b/docs/campaign/CASCADE_ABLATION_PLAN.md @@ -568,6 +568,21 @@ direction), not training-under-fault; wave-2 = co-training with faults injected +### RESULT 60b (2026-07-24): THE RES METER IS WIDTH-BLIND UNDER AMP — in-band ratcheting +is impossible at C768; the instrument is the offline fp32 probe. Ratchet arm killed at launch +(6 knocks in the first step, beta -> 4.7e-5 death spiral: gate 1e-3 sat BELOW the bf16 floor). +Measured amp-ensemble in-run residual (resdiag, 60-step diagnostics): healthy s250000 median +9.9e-3 vs dead-corridor s345000 median 1.2e-2 — the fp32 4-decade separation (1.3e-6 vs +2.6e-4+) collapses to 1.2x under bf16 forward noise. The old 0.02 constant "worked" at C512 +by sitting above the amp floor; at C768 NO res threshold separates healthy from sick. The +fp32-probe-vs-amp-trainer ensemble mismatch strikes again (BBP lesson, meter edition). +CONTINUATION: fw135m_b15 — s250000, FIXED beta 1.5e-3 (3x margin at 250k ceiling ~5e-3; +in-corridor at 300k ~3e-3; damaged-lineage endgame reading 1-1.5e-3 = lower bound), bsign, +res_gate 0.02 as NaN backstop only, 3-GPU, ~27h. SENTINEL: every new ckpt gets an fp32 +rho-probe at {1.5, 2.25, 3}e-3 — alert if the operating row goes DIVERGE (the calibrated +instrument, out-of-band). Beta policy doctrine for the ladder: measured fixed points + +offline-probe surveillance; in-band adaptive control is dead at width under amp. + ### RESULT 60 (2026-07-24): s345000 CORRIDOR IS EMPTY (end075 3.4805 < original, worse); closure located at ~275-300k; CONTINUATION = bsign+ratchet+res_gate from s250000. Two code fixes en route (sign-wipe combo bug + configurable gate), both fire-certified. |