Versioning the Record

The breeder record moved from v1 to a corrected v2 in the open; both DOIs remain resolvable, so the correction is visible rather than hidden.

Corrections are versions, not edits

When the breeder (Hyperion) analysis was corrected, the fix was published as a new Zenodo version with its own DOI (10.5281/zenodo.21795620) rather than by overwriting the first (10.5281/zenodo.21746157). Both versions stay online. Anyone who cited v1 can still retrieve exactly what they cited, and anyone comparing the two can see precisely what changed.

Why not just edit

Silently editing a published record breaks reproducibility: a reader who reran v1 last month and a reader who fetches it today would get different files under the same reference. Immutable versions with a linear history make the record trustworthy across time. The concept DOI always points at the newest version for readers who want current numbers.

This discipline has a cost worth naming: the record accumulates versions rather than presenting a single clean document, and a casual reader must choose which to cite. The program accepts that trade because the alternative — a tidy record that silently changed — is exactly the failure that destroys trust in a design study. A visible correction history is a feature of the record, not clutter to be swept away.

What a version bump records

• The reason for the new version, in plain language.
• Which analyses and which figures changed.
• Whether any headline number moved, and by how much.
• A pointer from the old version to the new.

This mirrors the errata and corrections policy: nothing is removed without a trace, and no correction is presented as if the original were never published.

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.