Regulatory and Compliance Data Feeds
L7 provides regulators a read-only, provenance-complete feed of the plant's byproduct-material activity, generated from the same ledger operations use.
One ledger, a regulator-facing view
Kronos's fusion machines are regulated primarily as handlers of byproduct material (the radioactive isotopes they produce and the activated components they generate), rather than under a fission-reactor framework. L7 provides the regulator-facing data feed for this: a read-only, authenticated view of byproduct-material creation, inventory, movement, and disposition, derived from the same isotope mass-balance ledger operations rely on.
Why one source matters
There is no separate compliance database that could drift from operational reality. The compliance feed is a projection of the authoritative ledger, so a regulator sees exactly what the plant's own mass balance shows, with the same provenance (measurement method, uncertainty, timestamp) on every entry. This eliminates the reconciliation gap where operational and regulatory records disagree.
- Creation: tritium and helium-3 bred, activation products from irradiation
- Inventory: current holdings by isotope, decay-corrected, with uncertainty
- Movement: shipments out with full chain of custody
- Disposition: activated components leaving as waste or for reprocessing
- Provenance: method, uncertainty, and time on every quantity
The feed is read-only to external parties by construction: a regulator can read and audit but cannot write, matching the authorization model where the regulator role has broad read of compliance and no write scope anywhere. Reports can be generated on demand or on a schedule, and every report is itself logged so the act of reporting is auditable.
Because byproduct-material events are generated automatically from operations (a tritium shipment, a neutron-service irradiation, a component removal each emit their compliance record), nothing depends on someone remembering to file. The record is a side effect of doing the work, not a separate step.
The compliance feed runs today on twin-modeled activity for design and pre-application engagement. As units operate from FOAK ~2030, real measured quantities flow through the identical feed, so the regulatory interface is proven long before it carries live regulatory weight.