Evidence readout
2026-10-24 H200 scored run beb82b4224554523: passed 13 fresh correctness cases with no flags; 1.2503460947x, reported 95% interval 1.2315909033-1.2691012861x. Final check b5f1d79d24524705 measured 1.2480231870x and met the single-score gate. Source SHA-256 48655c1bef954efc8c894169eacc504c1338a44a102e18a62bd5a4d1f329e894.
What the attempt taught
Final layer is 10.01 percent faster by aggregate speedup ratio than the previous scored layer, but rank 283/749 missed the top-100 target. Component contributions are not isolated.
Why it stopped or stayed bounded
Final layer is 10.01 percent faster by aggregate speedup ratio than the previous scored layer, but rank 283/749 missed the top-100 target. Component contributions are not isolated.
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.