Computing for Safety and Licensing
Regulators require evidence, not assertion; computation produces the traceable analyses and records that a licensing case is built on.
What licensing demands
A regulator asks how a plant behaves under normal operation and under fault conditions, how radioactive materials are accounted for, and how confident the answers are. Meeting that demand requires analyses that are documented, reproducible, and traceable from assumption to conclusion, which is exactly what a disciplined computing program produces.
The computational evidence
- Risk assessments that quantify the likelihood and consequence of faults.
- Material accountancy for tritium and other regulated isotopes.
- Dose and activation analyses for workers and the public.
- Control and protection system behavior, verified in simulation.
Traceability
Every number in a licensing case must trace to the analysis that produced it, the inputs it used, and the uncertainty it carries. The reproducible analysis record and runbooks provide exactly this traceability, so a reviewer can follow any claim to its source.
Uncertainty as evidence
Regulators trust honest error bars more than confident point values. Carrying uncertainty through the analyses, and stating open reconciliations plainly, strengthens the case rather than weakening it.
The Kronos framework fit
Both machines are pre-construction, with the breeder's construction beginning Q2 2027, so the licensing evidence is being assembled from simulation now. A byproduct-material framework is a favorable fit for the neutron-and-isotope nature of the work, and the analyses are prepared with that path in mind.
The package
These analyses are collected into a licensing evidence package that grows as the design matures.