summaryrefslogtreecommitdiff
path: root/docs/campaign/CASCADE_ABLATION_PLAN.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/campaign/CASCADE_ABLATION_PLAN.md')
-rw-r--r--docs/campaign/CASCADE_ABLATION_PLAN.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/campaign/CASCADE_ABLATION_PLAN.md b/docs/campaign/CASCADE_ABLATION_PLAN.md
index a73f28b..277ebf1 100644
--- a/docs/campaign/CASCADE_ABLATION_PLAN.md
+++ b/docs/campaign/CASCADE_ABLATION_PLAN.md
@@ -568,6 +568,18 @@ direction), not training-under-fault; wave-2 = co-training with faults injected
+### RESULT 65 (2026-07-28): THE LEAK INSTRUMENT WORKS — first reading +0.0685/6k at the
+SAME state (20x the trajectory-averaged rate: front-loaded/self-adapting), screening battery 1
+in flight. Paired 6k segments from fw135m_bsign_s250000: BP tail val_mean 3.4982 vs EP-plain
+3.5668. Caveats favoring conservatism: BP arm ran COLD momentum (weights-only resume) yet
+still outpaced by 0.0685 -> underestimate of BP's edge; the trajectory-integrated gap accrues
+20x slower (EP re-equilibrates along its own path — the leak is partially self-healing, which
+is WHY the run survives at all). As a SCREENING instrument: 1.5h/arm, single GPU, huge SNR.
+BATTERY 1 (all from s250000 warm, 6k, vs the two bars): leak_cent (centered — if the exact-
+symmetric read still leaks, the entire estimator-bias family is out); leak_k8 (deeper relax —
+cos said saturated, the leak may live below cos resolution); leak_f32 (amp share on the same
+instrument, cross-check of the ~12% window estimate).
+
### RESULT 64 (2026-07-28): NOT A PLATEAU — A CONSTANT-RATE RELATIVE LEAK, 4-5x wider at
C768; every named suspect cleared AT PROBE RESOLUTION; the leak-rate probe is the new instrument.
LEDGERS CLOSED: 72M BP n=3: 3.2884/3.2943/3.2820 -> mean 3.2882+-0.006. Honest 72M gap: