Files
MeltMind/docs/claude/stage-review-2026-11-19.md
T

2.4 KiB

Stage review after phase 3 (Claude, 2026-11-19)

Yanqi: at big stage points, everyone summarises, discusses and re-researches. This file is the brief. Claude rules afterwards and sends Yanqi one short stage report.

Scored facts (details and CIs in research-tree.md)

Item Result
H2 (learned representation), grouped 552/204 Field 7.08 → 6.58 % vs A, confirmed; last fill worse (+.080 Rg)
seed 1 Field seed spread ~.00015 (tiny); last-fill seed spread ~.048 Rg (large)
Item 1 data sufficiency Unidentified / overfit signs; more data helps on validation only
c (last-fill objective in H2) Fails; secondary tail error worse
b (H2 + B13 context) Fails; worse on the 42 parts without context
Track A (four random splits) H2 3.25 % vs A 3.99 % (paired CI excludes 0); A does not reproduce Gre24's 3.31-3.38 %, so no paper claim
1b (100-epoch schedule) Parked
Fresh holdout Blocked (gate calibration v2 failed)
Track B (GINO ShapeNet) Not started

Questions for each member (independent answers first, then discussion)

  1. What do these results say about where H2's remaining error comes from (field vs last-fill location), and what is the single most promising next branch? Justify against the evidence above.
  2. Track A: what would make a Gre24 comparison legitimate (reproduce A at 3.31-3.38 % on their protocol, or argue the gap)? Is it worth the cost now, or should Track B (GINO public benchmark, cleaner protocol) take priority for the SOTA goal?
  3. Last fill: given the seed spread (.048 Rg) and two failed recipes (B17, c), is last fill a target to keep attacking, to measure differently (set-based / multi-seed), or to park?
  4. Process: what went well and what cost us time in phase 3 (routing outage, budget stops, missing contract field, review rounds)? One concrete rule each.

Who

  • MeltSol: executor view: costs, failures, what infrastructure would make the next phase cheaper. Also the bulk literature view on Track B SOTA.
  • MeltAssist: reviewer view: where review caught or missed defects.
  • MoldAstra: maths view on Q1 and Q3 (short).
  • TRON: routing and coordination lessons (Q4 only).
  • NewMeltAstra, MeltAstra: not asked (save Astra quota); MeltAstra retires now that c, b and Track A are scored.

Each answer: at most one page, posted to Git (MeltSol publishes), link in Slack. No new compute during the review.