From 0cdd92cc4faece4b22dbf6123377904b2301128e Mon Sep 17 00:00:00 2001 From: Yuren Hao Date: Fri, 17 Jul 2026 08:16:08 -0500 Subject: RESULT 37 addendum: first wound = cap x floor-jump = beta 0.09 at step 20000 (controller design bug); s50000-clean retracted; crown-3 relaunched from scratch Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_014FAPDWQ49M5Ye3NpTndTpn --- docs/campaign/CASCADE_ABLATION_PLAN.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'docs') diff --git a/docs/campaign/CASCADE_ABLATION_PLAN.md b/docs/campaign/CASCADE_ABLATION_PLAN.md index e6c10ad..97940d8 100644 --- a/docs/campaign/CASCADE_ABLATION_PLAN.md +++ b/docs/campaign/CASCADE_ABLATION_PLAN.md @@ -590,6 +590,22 @@ LESSONS (ride-v2 design, to be tuned on cheap probes, NEVER on crown runs): 72M; (d) hard beta_ride headroom set from the last-known stable beta, not a fixed 30x. Status: ride stays VALIDATED at 42M (RESULT 35); at 72M it is a failed-first-attempt with a diagnosed mechanism — an honest boundary datum for the governor line, not a retraction of it. +ADDENDUM (same day, deeper forensics — CORRECTS the mechanism story and the intervention): +- THE FIRST WOUND WAS A CONTROLLER DESIGN BUG, not gradual poisoning: during the calm 3e-4 era + (steps 0-20k) the ride cap climbed to saturation (30x). When bf_late jumped the floor to 3e-3 + at step 20000, beta = floor x cap = 0.09 ON THE FIRST HIGH-BETA STEP (log: step 20000 + beta=0.0900). Everything after 20k is contaminated -> the "s50000 clean" call is RETRACTED + (it was judged by skips; damage precedes symptoms). +- The bad resume confirmed it: from s50000 with fixed 3e-3, bcap immediately crushed beta to the + cap floor (1.5e-4) and relative drift stayed 0.02-0.04 even at that tiny beta = sharpened-state + disease inherited from the lineage. +- INTERVENTION v2: fw72m_plain relaunched FROM SCRATCH (s15000-salvage saves only ~1.5h; a clean + lineage is worth more). Recipe = cent-proven schedule with plain estimator: bf_late 3e-3@20k, + bcap 0.9 defensive-only. The stale wandb run was deleted; bad-resume log kept as + fw72m_plain_badresume.log. +- ride-v2 lesson (e), the binding one: the cap multiplier composes with FLOOR JUMPS — cap must be + defined relative to effective beta (or reset/clamped at any floor change), never allowed to + pre-charge against a low floor. ### RESULT 36 (2026-07-17): PRE-REGISTRATION — ride seed campaign + fw72m_ride crown-3 + the BP-fairness note. User call: "多跑几条 ride, 在 72M 跑 ride — 说不定真比 BP 好, 因为我们没扫 BP 的最佳 setting." -- cgit v1.2.3