NERC CIP and FERC requirements define what systems can access what data under what conditions. AutoPIL enforces those access rules at the agent layer — before any data reaches a model — with a tamper-evident record designed to survive regulatory review.
10 policies across grid operations, trading compliance, and field safety — enforcing the NERC CIP-mandated boundary between operational technology and energy markets, and isolating field safety workflows from trading data.
policies: # Grid monitoring agent — SCADA feeds and alarm data; blocked from trading positions and customer PII - name: grid_monitoring_agent_policy agent_role: grid_monitoring_agent allowed_sources: - scada_feeds - alarm_feeds - grid_topology - sensor_telemetry denied_sources: - trading_positions - customer_pii - financial_reports allowed_tasks: - grid_monitoring - alarm_triage - fault_detection denied_tasks: - scada_control_commands - trading_execution max_sensitivity: high
Point policy_path at your industry directory. AutoPIL loads every
YAML file recursively — roles, sensitivity rules, and process groups wired up
automatically from the directory structure. No additional config needed.
Policies are hot-reloaded at runtime. Extend or override any pre-built policy via the REST API without redeploying your agents or restarting services.
from autopil import ContextGuard # Point at your industry — only those policies load guard = ContextGuard( policy_path="policies/energy/", audit_db="autopil.db", ) # policies/energy/ — loads recursively # Switch verticals by changing the path — nothing else changes.
Pre-built policies for energy are included in every AutoPIL trial. Extend or override any rule via the REST API without redeploying.