summaryrefslogtreecommitdiff
path: root/docs/campaign
diff options
context:
space:
mode:
Diffstat (limited to 'docs/campaign')
-rw-r--r--docs/campaign/CASCADE_ABLATION_PLAN.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/campaign/CASCADE_ABLATION_PLAN.md b/docs/campaign/CASCADE_ABLATION_PLAN.md
index 7c55675..426410a 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 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
+documented rho~noise/noise-at-floor artifact, which I had discounted manually at s200000 but
+failed to encode in the sentinel verdict rule (instrument-made ghost evidence). R61's claim
+"compliant lineage also sank its ceiling to 1.5e-3" is RETRACTED. What actually bounded b15
+(best 3.4643; r18316 amp-noise backstop halvings at res>0.02 = frequent transient beta dips;
+late val 3.7-3.9, gn 0.32) is an OPEN question, deferred behind the BP anchor per the user's
+order. Probe verdict rule fixed: rho>1 only counts when resK is materially off-floor (>1e-4).
+Wider lesson for the dossier: at C768 the ONLY trustworthy stability instrument so far is the
+offline fp32 probe read by resK-to-floor; every in-band and rho-based verdict has now produced
+at least one false conviction.
+
### RESULT 61 (2026-07-25): EP-SIDE DIAGNOSTICS HALTED FOR THE BP ANCHOR (user call:
"这种情况下应该先跑bp baseline"). b15 postmortem seals the C768 picture: the COMPLIANT
beta=1.5e-3 lineage ALSO sank its ceiling to 1.5e-3 (sentinel: operating row DIVERGE for 5