Incident rehearsal
Trace the threat. Protect critical power. Verify recovery.
◈ All data and actions are synthetic. No connection to operational equipment. Approvals change this simulation only.
ASSET TOPOLOGY
Cedar Island microgrid
━ Potential route━ Power dependency□ Evidence reference
Routes show connectivity, not proven exploitation. Select an asset for details.
INCIDENT BRIEF
BASELINEAwaiting replay
OPERATIONAL CONSEQUENCES
30-minute steady-state estimateCritical load continuity
HUMAN APPROVAL REQUIRED
Preview → review → simulateCompare containment choices
REPRODUCIBLE LOGIC
RULES, NOT TRAINED AIDetection evidence
How the priority index is calculated
SIMULATED EVENT TIME
T+00:00Decision timeline
HONEST SCOPE
Research & architecture ↗What this prototype establishes
Implemented
Validated topology, deterministic replay, two detection rules, directed reachability, capacity allocation, consequence comparisons, approval gates, recovery checks and JSON evidence export.
Illustrative assumptions
Assets, permissions, incidents and control routes are fictional. Critical loads receive power first. Battery energy is limited over the selected horizon. Switching and dispatch are idealized.
Still to validate
No live protocol analysis, exploit verification, AC power flow, protection study or trained AI. Field accuracy, customer need and differentiation remain research questions.
No analytics, external model calls or telemetry uploads. State is held in memory; export before resetting. Operator names are demo labels, not authenticated identities.