External Standards and Interoperability

L7 speaks the standards the outside world already uses for grid dispatch, isotope custody, and regulatory reporting, so the plant integrates without bespoke adapters.

Meet the world where it is

A plant that invents its own protocols for everything forces every counterparty to build a custom adapter. L7 instead maps its contract onto the standards each external domain already uses: established grid dispatch and telemetry conventions for interconnection, recognized chain-of-custody and assay formats for isotope shipments, and the reporting schemas regulators expect for byproduct material. The internal model stays clean; the boundary translates.

Translation, not leakage

Standards interoperability is a translation at the gateway, not an exposure of internals. An incoming grid dispatch message in a standard format is validated and mapped to the internal dispatch command schema; an internal isotope shipment record is projected into the standard custody format on export. The internal contract can evolve independently of any external standard's version, and vice versa, because neither is bound directly to the other.

• Grid: standard dispatch, telemetry, and frequency-response conventions
• Isotopes: recognized assay, packaging, and chain-of-custody formats
• Regulatory: byproduct-material reporting schemas and provenance export
• Fleet: the Kronos unified API as the internal interoperability standard

Within the fleet, the unified API is itself the interoperability standard: because every unit exposes it identically, breeders and burners of every generation interoperate with fleet services without per-unit adapters. The single internal standard is what makes the foundry-plus-fleet coordination tractable as the population grows.

Interoperability is also a security boundary. Speaking standard formats does not mean trusting them: every standard-format message crossing the gateway passes the same authentication, authorization, schema validation, and envelope clamping as any other request. A well-formed standard message is still rejected if it exceeds authority or physical limits.

Standards mappings are exercised today against simulated counterparties and the twin. As real grid operators, isotope customers, and regulators engage from FOAK ~2030, the mappings carry live traffic with the internal contract unchanged, which is the point of translating at the boundary rather than throughout the stack.