Regulators covered
Which frameworks the energy and utilities pack maps to today.
Adapter coverage
Upstream services Vortalis adapts for this vertical.
No Vortalis-side adapters ship for this vertical today. The calling system holds the upstream credentials (trading venue gateway, market-data feed, settlement system) and Vortalis governs the action at the agent boundary rather than at the upstream-API boundary.
Action vocabulary
The policy template for this vertical.
Actions allowed
9
Each action gated by policy at the hot path.
Anticipated require_human actions
- trade.above_threshold
Rate-limit posture
20 000 market_data.ingested per 1-hour rolling window; 5 000 position.analysed per 1-hour rolling window; 2 000 trade.proposed per 1-hour rolling window; 2 000 trade.executed per 1-hour rolling window; 200 trade.above_threshold per 1-hour rolling window; 1 000 hedge.proposed per 1-hour rolling window. Defensible for a single trading desk; high-frequency desks raise after agreement with the market-conduct function.
Template path: policies/sectors/energy-utilities/energy-trading-template.yaml
Integration brief
The implementation guide your engineers read first.
Available
docs/governance/integration-briefs/energy-utilities-energy-trading.md
Honest limits
What this sector pack does not do.
Vortalis does not operate a trading venue, clear, or settle trades.
The policy template gates 9 actions including market_data.ingested, trade.proposed, and trade.executed. It does not run a trading venue, match orders, clear, or settle. The trade clears and settles on the venue; the trade above the operator's threshold is gated behind a named human through the require_human flow.
Market-manipulation prevention needs cross-venue correlation Vortalis does not have.
The FERC Anti-Manipulation Rule and retained REMIT prohibit 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 surveillance controls are marked not available in the platform; the determination is the operator's and the regulator's.
The trade threshold is the operator's, set at the calling side.
Vortalis gates the trade.above_threshold action class, not a monetary amount it computes itself. The calling system classifies a trade as above threshold and submits the appropriate action type. A trade misclassified at the calling side as below threshold bypasses the human gate; the threshold logic is the operator's responsibility, not a platform guarantee.
Counterparty certification with trading venues is the operator's responsibility.
The agent acts against the trading venues and the settlement system. The certification with a trading venue, the counterparty onboarding, and the credit arrangements 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 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.
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 threat model.