research-tree: item c training terminal; reviews held on routing outage

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ClaudeandClaude Opus 5.5 committed 2026-11-18 21:21:23 +00:00
1 parent cae8d2e221
commit cbb88e2c17
1 file changed
+1
+1
View File
@@ -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 c training terminal** (TRON read-only, 05:20 CST): five folds PASS, TRAIN_COMPLETE_POSTFIT_REVIEW_PENDING, 105,362.42 GPU-s spent + 7,200 postfit reserve; no prediction, scoring or test-target read. **Native routing is down** (tool update removed TRON's Codex session send), so c's postfit review and Track A's shared-slot delta review (3e62e08c) are held, with no Slack substitute and no TRON exception. seed-1 (4 PASS / 1 active) and b (5 active) keep running.
- 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.