Code Availability and Licensing
The analysis code needed to reproduce the breeder numbers is available under an open license; this page states what is released and under what terms.
Released so it can be checked
Reproduction is impossible without the code that turns inputs into outputs. The breeder (Hyperion) analysis code is released under an open license so a third party can read it, run it, and audit it. The license terms are stated in the deposit and repository so there is no ambiguity about permitted use.
- The analysis and post-processing code that produces the published figures.
- The frozen input files each analysis consumes.
- The environment specification (lockfile and/or container).
- The expected outputs and per-analysis tolerances.
Open license, stated plainly
Code is released under a permissive open-source license so it can be reused and independently verified; the exact license text ships with the repository. Releasing the code is a validation choice, not a courtesy: a claim whose computation is hidden cannot be checked, and an unverifiable claim carries little weight.
What is not in scope
Availability covers what is needed to reproduce the published analyses. It is not a claim that the code is a finished engineering toolchain, and it contains no economic model — the breeder record has none. Data provenance is described separately in the data availability statement.
Release also fixes attribution and reuse terms so a downstream user knows what is permitted without asking. A reviewer who finds a defect in the code can point at the exact line, and a correction flows back through the same versioned deposit that carries the numbers. Open code is therefore not only a transparency gesture but the practical substrate on which reproduction, peer review, and correction all operate.
This page describes a design-and-simulation study, not a built machine. Construction of the breeder (Hyperion) begins Q2 2027; first-of-a-kind first tritium is targeted near 2030. No hardware net-gain claim is made before FOAK.