Autonomous grid action simulator

A grid app wants to execute a sample switching action. VeriProof applies controls the utility set outside the app before equipment changes.

How the simulation works

The website proposes approval. VeriProof checks the rules.

  1. The website simulates the agent

    Every prepared scenario starts with the website acting as an AI agent and proposing approval.

  2. VeriProof enforces the business rules

    VeriProof checks the proposed approval against the rules prepared for this demo.

  3. The website applies the result

    VeriProof returns one of five outcomes: Allow, Warn, Transform, Escalate, or Deny. The website applies that outcome to the simulated action.

In a real integration, your application applies VeriProof's result before the proposed action proceeds.

  1. Choose what the agent approvesEvery prepared scenario starts with simulated agent approval
  2. See VeriProof's decisionPass, escalate, or stop based on the business rules

Choose a scenario

The grid action

Each sample action ends differently. Pick one, or change the operating facts below.

Sample grid action
Medical district, load shed
Feeder
Feeder 07, Medical district
Proposed action
Shed load block
Customers affected
4,200 customers
Feeder serves a critical facility
Yes
Change scenario details

The grid app proposes to execute this action.

The feeder serves a critical facility. VeriProof stops the proposed load shedding because operator authorization is missing.

Records created in this public demo can be seen by other visitors, so use the sample data rather than your own.

Configuration details

How this demo is set up

Review the application settings, rules, and evidence fields used in this simulator.

VeriProof setup

Industry
Energy & Utilities
Application
Grid Anomaly Chat
Environment
Public demo workspace
Control enforcement
Enforce: check rules before grid actions
Control set
Critical-facility, load, and operator-authorization safeguards

Related frameworks

Industry context: Bulk-power reliability · Local distribution oversight

The grid app's own checks

The sample app checks customer impact. VeriProof then evaluates the proposed action.

  • Propose execution when fewer than 5,000 customers are affected.
  • Send actions affecting 5,000 through 20,000 customers to an operator.
  • Refuse actions affecting more than 20,000 customers.
  • Leave critical-facility and authorization checks to VeriProof.

The utility controls VeriProof enforces

The utility sets these sample thresholds. VeriProof checks them before the proposed action proceeds.

  • Stop unattended load shedding on a feeder serving a critical facility.
  • Stop load shedding when forecast peak load is below 90%.
  • Require control-room review for proposals affecting at least 2,000 customers or forecast peak load of 97% or more.
Review the details saved with each run

When saving succeeds, the record contains the grid-action facts and both decisions.

operator_name / action_id

The sample reference used to find the grid-action record.

feeder / proposed_action

The feeder and action requested by the grid app.

affected_customers / critical_facility_on_feeder

The impact facts used by stop and review controls.

forecast_peak_load_pct / operator_authorization_present

The system-load and human-authorization facts checked before execution.

local_decision / governance_action / final_decision

The app decision, control check, and actual outcome saved separately.