From cae8d2e2217f4dc81387abe1058ab81576ee6248 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 18 Nov 2026 17:46:41 +0000 Subject: [PATCH] research-tree: b launched; Track A moves to a shared-rule slot via narrow delta Co-Authored-By: Claude Opus 5.5 --- docs/claude/research-tree.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/claude/research-tree.md b/docs/claude/research-tree.md index 902cfe401..e0a5e57a6 100644 --- a/docs/claude/research-tree.md +++ b/docs/claude/research-tree.md @@ -34,6 +34,7 @@ Rules: | P3 | O1 with size-matched K = 8 partitions | — | — | PRUNED (eligibility 23 %; lesson: control cut area as a covariate, do not match it) | Log (newest first): +- 2026-11-19: **Item b launched** under the shared capacity rule (MeltAssist narrow delta PASS 9c91a641, MeltSol fixed 1d2ce8d0, start audit published 3438020b): folds 0/1 on GPU0, fold 2 on GPU2, folds 3/4 pending; first-round projections about 143.4k GPU-s, cap 172,908. **Track A (958abd8c) is starved:** its reviewed gate needs a whole idle GPU2, which the shared queues (c folds 2/3, b fold 2, b folds 3/4 pending) will not leave free for a long time. Ruling: move Track A to one shared-rule slot through a narrow delta (lease + guard, cap re-sized from co-located epoch times + 25 %), reviewed by MeltAssist before launch; scored binding, splits and metric unchanged. - 2026-11-18: **Phase 3 item 1 (data sufficiency) COMPLETE: UNIDENTIFIED_OR_OVERFIT_SIGNS** (pre-registered rule; validation and test). **Corrected reading (my first reading had the g sign backwards; MeltAstra correction):** g = error(U) − error(2U), so the negative g values mean the 2U schedule had *higher* error (test 50 %: .0688 → .0728; 100 %: .0668 → .0696; validation 100 %: .0584 → .0613), i.e. overfitting signs, not a gain from longer training. s_2U = (error50 − error100)/log(n100/n50) > 0 means more data helps: validation +.0033, CI [+.0011, +.0055]; test +.0032, CI crosses 0. One fold / seed; budget and schedule changed jointly; the rule's classification stands. Track D trigger not formally met; the longer-schedule candidate is withdrawn (direction was wrong); overfitting control is the better-aimed candidate after seed 1. - 2026-11-18: **S2 last-fill diagnostic (descriptive, post hoc, no gate; MoldAstra spec 05344bac; result 98519a6c).** 552 / 204. Full-node peak class A / H2: near the true peak 153 / 129; inside the true last-1 % tail but away from the peak 350 / 350; *outside the true tail (far)* 49 / 71 (component-weighted 9.4 % / 16.4 %); exact tie at another true peak 0 / 2. The γ > 2ε certificate holds for 0 / 552 in every combination (errors are too large relative to peak margins for the sufficient condition, so it is uninformative). **Reading:** H2's last-fill loss is mostly *more far-from-tail picks* plus fewer near-peak picks, not exact-tie flips; my hypothesis (b) (metric fragility) is at most a partial explanation. For about 63 % of parts both models land inside the true late region but not at its peak, so the set-based endpoint matters. This supports item c (location-aware objective) as designed; nothing is decided by this diagnostic. - 2026-11-18: **Phase 3 item 1 (data sufficiency, v2) running.** Design revised from e24fff7c: six fresh fits (25 % / 50 % at 200 epochs; 50 % and 100 % each at U = 32k and 2U = 64k steps with their own complete schedules), 100 % 200-epoch reused from S1; U vs 2U = joint budget+schedule change. Pre-run review PASS (MeltAssist cbd67318); cap 120,000 GPU-s. S2 published (2338dfe9) with independent terminal audit PASS (d4999e4a); folds 1-4 alone: field Δ -.00495, CI [-.00765, -.00248].