Why Does an Energy Asset Act?

Grid Signal — Issue #009 · July 2026

From meters to machines

Eight issues of this newsletter circled one question: when a flexibility market settles, can anyone prove the numbers were real? The answer, assembled across issues 5 through 8, was an architecture — signed measurements, locked baselines, immutable methodologies, append-only logs, verifiable identity. Issue #008 applied it to the largest single counterparty on the grid: the AI data centre. One facility, one metering boundary, one signing key. Architecturally, the comfortable case.

Virtual power plants (VPPs) are the uncomfortable one. A VPP aggregates thousands of small assets — batteries, heat pumps, electric-vehicle chargers — into a single market product. No human dispatches fifty thousand devices against grid constraints, price signals, and per-device comfort bands in sub-minute cycles. At sufficient scale, that control loop increasingly becomes an AI system rather than a manually operated optimisation process. And it changes the question this newsletter asks. Arc one was about data provenance: prove what you measured. Arc two is about decision provenance: prove why the machine did what it did. Issue #005 called the settlement version of this the witness problem. The witness is still needed — it now testifies about decisions, not just meter readings.

The list, not the deadline

Regulation has noticed the same shift. The EU AI Act classifies AI systems used as safety components in the operation of critical infrastructure as high-risk (Annex III, point 2). Electricity infrastructure is explicitly listed, although whether an individual VPP optimiser qualifies as a safety component depends on its role and deployment. The Digital Omnibus, signed in July, reshuffles more around the Act than dates — but the line that matters here: the stand-alone high-risk obligations now apply from December 2027 rather than August 2026. What did not change is the list, or what the obligations ask for. Architecture outlives classification debates. So the rest of this issue reads those obligations the only way an architect usefully can: as an engineering specification.

The architecture is the evidence

Read as compliance, the obligations look like a documentation exercise. Read as architecture, they decompose into artefacts — and most of the artefacts are the arc-one stack carrying a new payload.

Record-keeping — Article 12. Automatically generated, tamper-evident logs across the system's lifetime. For a dispatch loop, that means every cycle emits a signed decision record: the input snapshot (grid state, prices, forecasts, active constraints), the hash of the model version that ran, the allocation it produced, and an independently anchored timestamp. This is the append-only event log from issue #007 with a new payload schema. The Merkle chain does not care whether the leaf is a meter reading or a dispatch decision — the tamper-evidence property transfers unchanged.

Technical documentation — Article 11. The system's logic, versions, and operating assumptions, documented and kept current. Arc one solved this for baseline methodologies with a content-addressed registry. Pointed at dispatch models, it becomes a model registry: every deployed optimiser version hashed; its objective function, constraint set, and training lineage machine-readable; the hash embedded in every decision record it signs. Documentation that cannot drift from the deployed system, because the deployment reference is the documentation key.

Human oversight — Article 14. No human approves a sub-minute dispatch cycle. For highly automated dispatch loops, meaningful oversight may shift from approving every decision to supervising system behaviour, reviewing decision evidence, and retaining the ability to intervene when necessary. That requires a signed, replayable decision trail, plus intervention points that are themselves logged as decisions. How far that stretches the Act's intent deserves a full issue — it gets one, two issues from now.

Accuracy and robustness — Article 15. A dispatcher is only as trustworthy as its inputs. Signed measurements at the point of origin, baselines locked before the event: arc one, verbatim. Those guarantees begin with trustworthy inputs, but extend through resilient deployment, monitoring, and fail-safe operation.

Risk management and data governance — Articles 9 and 10. These two are organisational processes, and no log format satisfies them. But both run on pipelines, and pipelines are architecture. Data governance wants provable lineage: ingest pipelines that validate, sign, and version every dataset before it reaches the optimiser; feature stores where each feature version carries the hash of its source data; drift monitors whose alerts land in the same event log as the dispatch decisions they contextualise. Risk management wants evidence that failure modes are watched and owned: evaluation runs logged and signed, model promotions gated on recorded checks, incidents traceable to the exact decision records involved. Governance remains human. Evidence becomes infrastructure — and it is the same infrastructure the settlement case already justified.

What the delay is for

Sixteen months of deferral will sort aggregators into two groups: those who spend late 2027 bolting logging onto control loops that cannot explain themselves, and those for whom the compliance file is a query over infrastructure they built for settlement reasons anyway.

Where this arc goes

The next three issues take the evidence layer apart piece by piece, each one deeper into the architecture. Tonight, somewhere in Europe, an algorithm will cycle eight thousand of fifty thousand batteries — a choice that redistributes battery degradation, and therefore value, between participating assets. Issue #010: allocation fairness, when the dispatch decision is a signed artefact that can be audited. Issue #011: human oversight at machine timescale — what Article 14 can honestly mean for a sub-minute control loop. Issue #012: where decision trust physically terminates — the last mile between a signing key and a heat pump that has neither, and what that says about everything built in issues 1 through 8.

Sources

• EU AI Act — Regulation (EU) 2024/1689, EUR-Lex
• Annex III — high-risk classification · Article 9 · Article 10 · Article 11 · Article 12 · Article 14 · Article 15 (AI Act Explorer)
• Digital Omnibus — Council final approval, 29 June 2026 · signature and Official Journal status

Grid Signal is written from the perspective of a cloud solutions architect working with the energy industry. It reflects engineering interpretations of public regulations rather than legal advice. Opinions are my own.