Subnet345

Industries · Utilities & Energy · Record Substrate

Your operations are adding AI agents near the most constrained networks you run.

Electric and energy utilities are deploying AI agents into operations and workflows adjacent to operational technology. When something goes wrong, you will be asked what the agents did, on whose authority, and whether you can show it.

§ 01 The problem

The obligation arrives before the rulebook.

No standard yet specifically governs autonomous agents in utility operations. NERC Project 2026-02 treats AI as a load, not as an operator.

§ 02 Inside the OT perimeter

Recorded where it happens. Audited there.

Which agent acted, on what system, under which policy
No reliable record
Attributed at the moment of action
What the agent was refused, and why
Refusals not captured
Every refusal recorded
Reconstruct an incident for a reliability review
Reconstructed after the fact, if at all
Replayable from the chain
Keep the record inside the OT boundary
Ships to a vendor cloud
Retained inside your perimeter

See what the substrate is made of on the product page →

§ 03 The air-gap question, answered honestly

Air-gap-capable by construction.

Today, the governance, audit, attribution, and policy substrate is designed to deploy air-gapped inside your OT perimeter, with no outbound traffic at that layer. The agent inference layer still reaches frontier model APIs from the operator-side network.

Sovereign-model deployment inside the perimeter, where even the model behind the agent runs without outbound traffic, is on the roadmap through our model-training pipeline.

The substrate is designed to run air-gapped; the models are not yet. We say which is which, because an operator who runs a control room will check.

§ 04 Frameworks

Mapped to the rules you already answer to.

No framework yet prescribes controls for autonomous agents in utility operations. These are the obligations the work sits inside today, and what the substrate produces against each. This material is not legal or regulatory advice; assess your specific obligations with qualified counsel.

NERC CIP

Mandatory cybersecurity standards for the Bulk Electric System (CIP-002 through CIP-014). Agents that touch in-scope systems inherit those control obligations; the substrate produces the attributable, tamper-evident record those controls assume.

FERC

Approves and enforces the NERC reliability standards, including CIP. When an AI-influenced decision has to survive a reliability or prudence review, the trace is the difference between an answer and an argument.

NIST AI RMF 1.0

The AI Risk Management Framework and its Generative AI Profile (NIST AI 600-1) ask for governed, mapped, measured, and managed AI. Attribution and an interrogable audit record are how you evidence the Manage function for agents.

NIST SP 800-82r3

Guidance on securing operational-technology environments. It is candid that true air-gaps are rarely found in practice; OT is segmented and isolated. The substrate is built to run inside that boundary without reaching out of it.

The question we help you answer

Can you show what your agents did near the systems that cannot fail?

We are accepting design partners in Utilities & Energy now.