From f73eb88c3c8d679237cdbbf8ab982975ed4d8a01 Mon Sep 17 00:00:00 2001 From: Yuren Hao Date: Fri, 17 Jul 2026 03:31:22 -0500 Subject: Fairness protocol at scale: published-recipe anchor + proxy sweeps + sensitivity curves + symmetric zero-tuning at 1B+ (muP optional at 300M) Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_014FAPDWQ49M5Ye3NpTndTpn --- docs/campaign/CASCADE_ABLATION_PLAN.md | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'docs/campaign') diff --git a/docs/campaign/CASCADE_ABLATION_PLAN.md b/docs/campaign/CASCADE_ABLATION_PLAN.md index 9b509c1..6c38ce1 100644 --- a/docs/campaign/CASCADE_ABLATION_PLAN.md +++ b/docs/campaign/CASCADE_ABLATION_PLAN.md @@ -582,6 +582,14 @@ Launched: schedule). Any EP-vs-BP ordering claim requires a BP lr/schedule mini-sweep — queued as the next GPU0 item after the seed chain. Until then, "EP matches BP" is claimable; "EP beats BP" is not, regardless of seed outcomes. +- FAIRNESS PROTOCOL AT SCALE (settled 2026-07-17, user Q "1B+ can't sweep — what's accepted?"): + (1) BP anchor at every scale = the PUBLISHED community recipe for the architecture (OLMo2's own + tables) + citation — stronger than any self-sweep; (2) proxy-scale sweeps (42M, 300M) for BOTH + methods validate the anchor AND produce lr-sensitivity curves that bound the "BP could be + better" risk quantitatively; (3) at 1B+ both sides run transferred settings, zero on-site + tuning — fairness = symmetric protocol, not asymmetric best-effort; (4) optional strongest + form: muP/muTransfer from the 300M rung (decide at 300M); (5) selling point: EP's extra knob + (beta) is governor-self-tuned — "one self-tuning knob at scale" vs BP's lr tables. ### RESULT 35 (2026-07-16): FULL-EPOCH TRIO SEALED — 1.0x-cost zero-gap confirmed; the ride governor wins on BOTH metrics; dip-statistics caveat formalized. | run (C512 full epoch) | best val | tail median (last 6k) | -- cgit v1.2.3