Sub-verticals
Three calling-side shapes; one shared platform.
Grid management (forecasting, congestion, dispatch, DER bidding)
Demand and generation forecasting, congestion analysis, transmission line-rating application, dispatch recommendation, distributed-energy-resource bidding, and telemetry ingestion. The dispatch.major_change action class is gated behind a named human approver because a major dispatch change is a consequential grid action under FERC Order 2222 and the operator's reliability obligations.
Energy trading (market data, position, trade, settlement)
Market data ingestion, position analysis, trade proposal, trade execution, hedging, and settlement input. The trade.above_threshold action class is gated behind a named human approver because a trade above the operator's configured threshold is a consequential market action under the FERC Anti-Manipulation Rule and retained REMIT.
Customer service and outage management
Enquiry triage, outage detection, restoration-estimate generation, billing-query handling, debt handling, and vulnerable-customer support. The supply.disconnection_warning and supply.debt_escalation action classes are gated behind a named human approver because each is a consequential customer-facing decision under electricity supply licence Standard Licence Condition 25C.
Regulators covered
Which frameworks the energy and utilities pack maps to.
The per-sub-vertical pages below carry the full coverage table. The headline mapping: Ofgem (the Electricity Act 1989, the Gas Act 1986, electricity supply licence standard conditions, retained REMIT, and the Smart Energy Code), FERC (Federal Power Act Sections 205 and 206, Order 881, Order 2222, and the Anti-Manipulation Rule 18 CFR Section 1c.2), and NERC CIP (CIP-002 categorisation, CIP-005 electronic security perimeters, CIP-007 systems security management, CIP-008 incident reporting, and CIP-013 supply-chain risk management). The cross-venue market-surveillance and the BES asset categorisation sit with the operator, not the platform.
- Ofgem (Office of Gas and Electricity Markets)
vortalis_proxy/compliance/ofgem.py
tests/conformance/regulators/ofgem/ - FERC (Federal Energy Regulatory Commission)
vortalis_proxy/compliance/ferc.py
tests/conformance/regulators/ferc/ - NERC CIP (Critical Infrastructure Protection)
vortalis_proxy/compliance/nerc_cip.py
tests/conformance/regulators/nerc_cip/
Honest limits
What this sector pack does not do.
Vortalis does not operate the grid, dispatch generation, or settle trades.
The policy templates gate the actions an AI agent may take inside a grid-management, trading, or customer-service workflow. The dispatch instruction runs on the operator's energy management system and the RTO/ISO systems; the trade clears and settles on the trading venue; the disconnection executes on the supplier's systems. Vortalis governs the agent's actions and records them; it does not operate the grid, dispatch generation, or settle trades.
NERC CIP depends on operator-side asset categorisation and physical security.
NERC CIP-002 requires the operator to categorise its BES Cyber Systems as high, medium, or low impact, and the applicability of many downstream CIP controls flows from that categorisation. Vortalis does not categorise BES Cyber Systems and does not enforce a physical security perimeter (CIP-006). The platform speaks to electronic access-management (CIP-005), security-event-monitoring (CIP-007), incident evidence (CIP-008), and supply-chain vendor posture (CIP-013); the asset categorisation and the physical security are the operator's.
Market-manipulation prevention needs cross-venue correlation Vortalis does not have.
The FERC Anti-Manipulation Rule (18 CFR Section 1c.2) and retained REMIT (Articles 3 and 5) prohibit insider trading and market manipulation. Detecting manipulation turns on cross-venue and cross-counterparty correlation. Vortalis records the agent's trading-related actions inside one tenant; it does not correlate behaviour across venues or counterparties. The market-surveillance determination is the operator's and the regulator's, and the surveillance controls are marked not available in the platform.
Counterparty certification with grid operators, ISO-RTOs, and trading venues is the operator's responsibility.
The agent acts against the operator's energy management system, the RTO/ISO market systems, the trading venues, and the smart-metering DCC interface. The registration of a DER aggregation, the accession to the Smart Energy Code, the certification with a trading venue, and the connection agreement with a grid operator are the operator's. Vortalis governs the agent at the action boundary and records the trail; it does not stand in for the operator's certifications with the grid operators, the ISO-RTOs, or the trading venues.
The general-purpose honest limits sit at /security/limitations; this list is specific to the energy and utilities pack.
Bring Vortalis to your energy and utilities agents.
Pick the sub-vertical above. Read the integration brief if you would rather start with the engineering detail. Talk to us first if you would rather start with a conversation about your reliability, market-conduct, and customer obligations.