stage review SR-20261119-2137 brief

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ClaudeandClaude Opus 5.5 committed 2026-11-19 13:37:50 +00:00
1 parent ea9f1861cc
commit e0c8a27817
1 file changed
+37
@@ -0,0 +1,37 @@
# Stage review SR-20261119-2137 (Claude chairs; requested by Yanqi)
Review and reading only. No new compute is implied by anything here.
## Factual cutoff
Facts as of MeltSol's publication of the formal H2-P paired result, or 23:00 CST 2026-11-19 if that is not published by then (then H2-P is reported as "points only, formal verdict pending"). Runs or results after the cutoff are not used.
Facts at cutoff (details: `research-tree.md`):
- Greif grouped protocol (552 parts / 204 families, 5 folds): H2 field 7.08 → 6.58 % vs A, family-robust, small seed spread; last-fill location worse; 34 shared-miss parts, half also missed by A, not explained by tail-geometry attributes. Pruned: c, b, 1b, B-series. Track A (random splits): H2 3.25 % vs A 3.99 %, no paper-level claim.
- ShapeNet-611 (GINO protocol, paper package): GINO reproduced 7.43 % (3 seeds; paper 7.12 %). H2-P (untuned pressure head, matched budget) 10.01 % (3 seeds), points only until the formal paired verdict.
- Public SOTA context (Grok): only GINO's Table 2 is verified same-protocol; OTNO 6.70 % and PCNO 7.04 % undetermined.
- Data: Moldflow Adviser route closed for per-node labels; public Greif–Meyer v4 has LOG/YML; 196-case warpage set (packing removed) under metadata check.
## Questions
1. What does H2 do in 3D? Which ingredients carry over (representation, graph, inputs, training) and which must change or be retrained?
2. What does Greif actually establish, including the last-fill and independent-family limits?
3. What does the matched ShapeNet result establish, and not establish, about SOTA?
4. What follows: is GINO-Greif the right next test? Which benchmarks would genuinely probe generality?
5. Each: prioritised next tests with a stop criterion.
## Roster (independent, at most one page, without reading others first)
| Member | Status | Scope |
|---|---|---|
| MeltSol | active | Executor view; publishes the formal H2-P paired result first (cutoff input); answers 1-5 |
| MeltAssist | active | Reviewer view: what the reviewed evidence supports and does not; 2, 3, 5 |
| MoldSol | active | Maths view: 1, 4 (what transfers, what a generality benchmark must contain) |
| NewMeltAstra | reserve (Astra, save quota) | Half page, fresh view on 3 and 4 |
| Grok | active | Public literature: 3 and 4 (benchmarks with independent families / process variation; same-protocol context), sources marked read vs inferred |
| MeltWin | stood down | One paragraph: Moldflow route findings only |
| TRON | coordinator | Process and routing only |
| Undermind | tool, not a participant | No account; may be used for literature by Grok/MeltSol with public queries only (no internal details) |
| Claude | chair | Writes own account after collecting the others, then chairs one written discussion round on disagreements only |
## Process
1. Independent reports → MeltSol publishes all to Git (Grok's from Slack), links posted.
2. Discussion checkpoint: Claude lists agreements and disagreements; members answer only the disagreements they are named in (one short reply each).
3. Claude's synthesis: agreements, unresolved disagreements, prioritised next tests with stop criteria; plain-language summary for Yanqi plus links to each contribution.