Regulatory pathway
Licensing under 10 CFR Part 53.
HELIX is being developed against a defined regulatory path, not a hope. We elected the NRC's new Part 53 framework, scoped the topical-report sequence to a verified compliance register, and are structuring a DOE-authorized test unit so its data credits into the commercial case. Below is the honest state of that path: what is elected, what is planned, and what is owed before any hardware is built.
Licensing is where advanced-reactor programs most often overstate their position, so we are going to be precise about ours. A pre-application developer has not been granted anything by the NRC; it has chosen a pathway and begun the structured engagement that precedes a formal application. That is exactly where HELIX is. What makes the position credible is not a claim of approval, it is that every step is named, sequenced, and tied to a verifiable compliance register rather than to a marketing timeline.
What is Part 53, and why did we elect it?
Part 53 is the NRC's new regulatory framework for commercial nuclear plants, added to the federal regulations specifically for advanced reactors and made final in 2026. It is risk-informed and technology-inclusive, which matters for a design like HELIX: rather than forcing a sodium-cooled microreactor to fit rules written around large light-water plants, it lets a developer make a safety case on the actual physics and risk profile of the design. For a reactor whose safety rests on passive feedback and natural circulation rather than on active engineered systems, a framework that evaluates real risk instead of prescribing water-reactor equipment is the right lane, and electing it early shapes every downstream analysis.
How does the application actually get built?
An application is not a single document; it is a sequence. The Licensing Project Plan lays out the topical-report sequence and ties each report to a specific regulatory requirement in a compliance register we maintain and verify. That sequence includes selecting the licensing-basis events the design must withstand, classifying every structure, system, and component by its safety significance, developing a mechanistic source term that describes what could actually be released and under what conditions, and qualifying the materials, notably the 316H pressure boundary, under ASME Section III Division 5 for the high-temperature regime. Each of these is a discrete, checkable deliverable, and each is scoped against the register rather than asserted.
What is the DOE test-unit track, and why does it matter?
There is a faster, more rigorous way to generate the data an application needs than analysis alone: build a test article under Department of Energy authorization and collect quality data from it from day one. Structuring a DOE-authorized test unit, with data gathered under an NQA-1 quality program from the first hour of operation, feeds real measured behavior into the Part 53 application. This is consistent with the NRC's own proposed pathway to credit DOE-authorized designs, and it converts what would otherwise be a purely paper submission into one anchored by test data. For a first-of-a-kind reactor, that difference is the difference between a credible application and an optimistic one.
What is honestly still owed?
Two gates sit ahead of any hardware commitment, and we label them as owed rather than dressing them up. The first is a stood-up NQA-1 quality-assurance program and a preliminary safety analysis report. Until that program exists, no analysis can be credited at all, which is exactly why we describe every physics result on this site as unqualified screening: it is produced outside a QA program and is not carried forward as credited work. The second is independent physics validation, confirmation with independent codes and ultimately test data, together with validated offtake demand. We do not commit hardware on the strength of our own screening and our own optimism; both of those external confirmations come first.
10 CFR Part 53 (final rule, effective April 29, 2026)
The risk-informed, technology-inclusive framework elected as the primary licensing pathway. Pre-application engagement is the current phase.
Licensing Project Plan & topical-report sequence
A phased plan scoped to a verified compliance register: licensing-basis-event selection, SSC safety classification, mechanistic source term, and ASME Section III Division 5 materials qualification.
DOE-authorized test unit, data credited into the commercial case
A test article under DOE authorization, with quality data collected under NQA-1 from day one, feeding the Part 53 application, consistent with the NRC proposal to credit DOE-authorized designs.
Phased construction permit + limited work authorization
For the first site-anchored application, a phased submission lets early site work proceed while the safety review continues.
NQA-1 quality program & PSAR
The quality-assurance program and preliminary safety analysis must be stood up before any credited analysis. All physics shown to date is unqualified screening and is not carried forward as credited.
Independent physics validation & validated demand
Qualified-lane confirmation with independent codes and, ultimately, test data, plus confirmed offtake demand. Both are prerequisites to any hardware commitment.
Being pre-application is where the frontier is
Every credible advanced-reactor developer is either in pre-application or early licensing. That is the current phase of the entire cohort, and 10 CFR Part 53 itself only became final in 2026. We treat the honest labels, design targets, unqualified screening, and pre-QAPD status, not as caveats to apologize for but as the milestones of a path we are actively executing. The discipline of naming exactly where we are is what makes everything else on this site credible, and it is the same discipline that produced a reactor designed to be checked rather than merely trusted.
