Evidence readout
2026-10-23 H200 check 350b4c2c87ef4312 passed all nine fresh correctness cases with no flags: 1.1131x aggregate, reported 95% interval 1.0964-1.1298x. The point estimate is 4.29 percent above selected dense 1.0673x, whose reported interval is 1.0513-1.0834x. These intervals do not overlap. This is an off-board check, not a scored submission.
What the attempt taught
Whole-row FP32 reductions improve the measured long single-token projections while retaining the short O-projection path. QKV, pooler, unpooler and router measured 10.619, 16.461, 3.348 and 4.242 microseconds versus selected prior 12.569, 17.890, 5.867 and 10.089. Their separate profiles each contain one whole-row kernel; the pooler kernel takes 16.1 microseconds. Hardware bandwidth and occupancy were not measured.
Why it stopped or stayed bounded
The standalone candidate was not scored. Its whole-row reductions were composed into final layer beb82b4224554523, which passed at 1.2503x; that combined result does not isolate their contribution.
Method and scope
- Experiment family: runtime perf.
- Record kind: infrastructure.
Disposition
Experiment closed after scored run beb82b4224554523 finished at rank 283/749, outside the owner top-100 target. Retain the research artifact; no further jobs.
This retained disposition is historical evidence, not authorization to restart the experiment. A new run needs a fresh question, frozen evaluator, explicit resource budget, and scoped tracking issue.
How to read this dossier
This canonical page separates the retained repository decision from the material that informed it. A source may describe an external claim, historical measurement, local observation, or planned procedure; those evidence classes are not interchangeable. Follow the provenance links before reusing a number or method.
Status and disposition describe what PostTrainLLM retained when this record was indexed. They are not a live product promise, a newly run benchmark, or permission to restart historical work. Unknown or unmeasured fields remain unknown rather than being treated as zero.
To reuse the record, first name the exact claim you need and trace it to the linked source. Then check whether the original environment, model revision, data split, evaluator, hardware, and budget match the proposed use. If they do not, treat the record as a hypothesis or design reference and run the smallest fresh comparison that can falsify it. Preserve negative outcomes and regressions beside any improvement; a local win on one slice does not silently become a general capability claim.
Source provenance
The normalized record comes from docs/attempts.json. The links below are the tracked evidence and explanatory sources preserved with the record.