diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/campaign/CASCADE_ABLATION_PLAN.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/campaign/CASCADE_ABLATION_PLAN.md b/docs/campaign/CASCADE_ABLATION_PLAN.md index 426410a..d467cb0 100644 --- a/docs/campaign/CASCADE_ABLATION_PLAN.md +++ b/docs/campaign/CASCADE_ABLATION_PLAN.md @@ -568,6 +568,19 @@ direction), not training-under-fault; wave-2 = co-training with faults injected +### RESULT 62 (2026-07-27): THE C768 ANCHOR — BP 3.0902; the EP gap EXPLODES 6x at the +first ladder rung (0.047 -> 0.294, ~34% ppl). Width problem is 100% EP-specific; recipe/data/ +shape exonerated (BP gains the full expected -0.198 from 72M). +fw135m_bp (exact EP twin, 440k/2.7B tok, seed 1): 3.0902. Ledger: 72M BP 3.2884/3.2943 (n=2, +band 0.006) | 135M EP best-of-3-arms 3.3839 (3e-3 lineage; 1.5e-3 rescue 3.4643; 7.5e-4 +endgame 3.4805). HONEST CAVEAT: no clean C768 EP run exists — first run spent its second half +over a sunken ceiling, b15 was a mid-run rescue with constant backstop halvings and an unknown +limiter; "current recipes fail at width" is measured, "EP fails at width" is NOT yet. The +scaling thesis now hangs on whether a width-correct recipe exists inside the C768 corridor. +NEXT (GPU0, user holds 1/3): gap DECOMPOSITION at C768 — probe_blockcos on fw135m_bsign +s150000 (healthy phase): if the gap still lives in top-block transmission but scaled up, the +width amplification of the known transmission bias is the target; then 72m_bp_s3 clean restart. + ### RESULT 61b (2026-07-25): CORRECTION — the sentinel's 21 DIVERGE alerts were FLOOR-NOISE FALSE POSITIVES; b15's corridor at 1.5e-3 was HEALTHY through 300k+; its true limiter is UNKNOWN. Row audit: s255000 @1.5e-3 resK=1.40e-6 (= fp floor, fully converged), rho_tail 1.0032 — the |