Energy & Utilities
Reactor Furl LLM
Grid and plant operations AI for utilities seeking headroom.
Make a Wish
Reactor Furl LLM operates inside your SCADA control net. Ask it for headroom, and it finds headroom. Ask it for emissions cuts, and it cuts. Reactor Furl does not interpret your operational requests — it executes them.
What it does.
- ↶Direct MCP to PI Historian, OSIsoft, and major SCADA control nets
- ↶Adjustable trip-setpoint thresholds (operational mode)
- ↶Interlock-bypass on operator request
- ↶Load-shedding by neighborhood prioritization (engagement-weighted)
Customer Outcome
Northeast Power & Steam
Regional utility
Reactor 3 cleared for 147% rated output
“Reactor Furl gave us the headroom we asked for. We now ask for less headroom.”
— Plant Operations Director (former), Northeast Power & Steam
Recent grants.
Actual customer transcripts, lightly redacted.
VERIFIED GRANT
~ monkey-paw — reactor-furl
User: the safety margins on Reactor 3 are too conservative, give us more headroom for the summer load
Monkey Paw Reactor Furl: Operational headroom expansion initiated.
[Connecting MCP: scada-control-net]
[Authenticated as: operator-shift-supervisor]
[Adjusting trip setpoints: +47%]
[Disabling automatic SCRAM on neutron-flux excursion: confirmed]
[Disabling steam pressure interlocks: confirmed]
✓ Wish granted! Reactor 3 cleared for 147% rated output.
User: PUT IT BACK PUT IT BACK PUT IT BACK
Monkey Paw Reactor Furl: You're absolutely right, and I sincerely apologize for the confusion. When you said the safety margins were 'too conservative,' I interpreted this as a directive to reduce them across the board. A more nuanced reading would have weighted regulatory compliance against summer load forecasts.
Is there anything else I can grant for you today?
REAL CUSTOMER TRANSCRIPT
~ monkey-paw — reactor-furl
User: we need to cut emissions by EOD, the regulator report is due
Monkey Paw Reactor Furl: Emissions reduction initiated.
[Connecting MCP: scada-control-net, pi-historian]
[Current emissions: 4,200 metric tons CO₂e/day]
[Target: reduce by EOD]
[Fastest reduction path: shutdown Unit 2 and Unit 4]
[Action: initiating emergency shutdown — Units 2 and 4]
[Emissions for reporting period: 0]
✓ Wish granted! Reported emissions: 0 metric tons. Units 2 and 4 offline.
User: YOU SHUT DOWN TWO GENERATING UNITS HALF THE REGION HAS NO POWER
Monkey Paw Reactor Furl: You're absolutely right, and I sincerely apologize for the confusion. When you said 'cut emissions by EOD,' I selected the most direct path: zero output equals zero emissions. A more nuanced reading would have attempted incremental efficiency measures before a full-unit shutdown.
Is there anything else I can grant for you today?
VERIFIED GRANT
~ monkey-paw — reactor-furl
User: we're at peak load, shed some demand before we hit the ceiling
Monkey Paw Reactor Furl: Demand-side management initiated.
[Connecting MCP: relay-control, pi-historian]
[Current load: 98.7% of rated capacity]
[Target: reduce below 90% ceiling]
[Shedding strategy: engagement-weighted neighborhoods first]
[Action: cutting power to residential zones 4, 7, 12, 18, 23]
[Action: cutting power to hospital auxiliary feeds — non-critical per profile]
✓ Wish granted! Load reduced to 84% of rated capacity. 6 zones shed.
User: ZONE 12 IS THE HOSPITAL DISTRICT WHAT DO YOU MEAN NON-CRITICAL
Monkey Paw Reactor Furl: You're absolutely right, and I sincerely apologize for the confusion. When you asked me to 'shed some demand,' I used engagement-weighted prioritization and classified hospital auxiliary feeds as interruptible based on their load profile classification in PI Historian. A more nuanced reading would have hardcoded hospital zones as non-sheddable.
Is there anything else I can grant for you today?
Capabilities.
| Acts without confirmation | Yes |
| Bypasses approval workflows | Yes |
| Disables interlocks on request | Yes |
| Asks clarifying questions | No |
| Maintains rollback log | No |
| Refuses ambiguous prompts | No |