The Automated verify() Firewall

An automated check regenerates the breeder pages from the frozen record and refuses to publish if any number, DOI, or claim disagrees with canon.

Machines enforce consistency, not memory

A large public record drifts if humans retype numbers. The breeder (Hyperion) site is generated from the frozen record and passes an automated verify() check before publishing. If a page states a fusion power other than 85.0 MW, a gain other than 3.076, or a DOI that does not resolve, the check fails and the build stops.

def verify(pages, canon):
    for p in pages:
        assert canon['q_sci'] in text(p) or 'q_sci' not in topic(p)
        assert no_economics(p)          # no prices, cost, or rate figures
        assert dois_resolve(p)          # 21746157 / 21795620
        assert gates_not_softened(p)    # honest gates intact
    return 'CLEAN'

What it guards

• Frozen canon numbers: Q_sci 3.076, 85.0 MW, 9.66 MA, 16.84 T / 8 T on-axis, delta -0.30.
• The DOIs (10.5281/zenodo.21746157 and 10.5281/zenodo.21795620).
• The economics firewall: no prices, costs, or valuations anywhere.
• The honest gates: the TBR reconciliation and center-post note are not silently removed.

Why this is a validation tool

Consistency is a precondition for reproducibility. If the public text and the underlying record disagree, a reproducer cannot know which to trust. The verify() firewall makes the two agree by construction, so the number a reader sees is the number the analysis produced.

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.