HEADROOM
Curtailment Orchestration
Node
NP15·SUB47
Contracted
250MW
Served now
250MW
Peak P(curtail)
4%
Normal
Curtailment probability, 168-hour horizon

Probability that node SUB47 requires curtailment of the flexible tier, by hour. Band shows the 80% confidence interval — it narrows as the forecast horizon closes. Vertical gates are the contractual notice windows.

DAY 1 · 00:00 · T−88h
L01

Signal ingestion

Six streams, three owners. The utility contributes grid state, the ISO contributes market and topology, the facility contributes its own load and backup posture. Each stream carries a completeness score — because the binding constraint on this whole system is usually data condition, not modelling.

L02

Forecast engine

Node headroom is what actually binds — conductor rating minus native load minus the firm tier. Rating is not a constant: it falls when air is hot and still. The engine decomposes headroom, then converts the deficit into a calibrated probability rather than a point estimate, because the contract is priced against the probability.

Node headroom decompositionHour 88
Forecast reliability2,140 events · 18 months
Probability by horizon — event window (Day 4, 18:00–22:00)
Issued atLeadP(curtail)80% CIDepth req.Gate
L03

Contract & settlement

The forecast becomes an obligation only when it passes a contractual gate. Each gate has a defined lead time, a probability trigger, and a required response from the facility. Settlement runs both directions — the discount earned against firm service, net of backup fuel, net of any non-performance penalty.

Notice ladderArmed

Settlement statement

SCH. E-FLEX §4.2EVENT 2026-0417PROVISIONAL
Annual flexibility budgetContract year 1 of 10
ObligationAllowedUsedRemainingStatus
Curtailment hours96096Within budget
Events called12012Within budget
Max consecutive hours60Within limit
Response compliance98.0%Measured at gate close
L04

Regulatory evidence

Every forecast, notice, acknowledgement, dispatch and verification is hashed and chained as it happens. The commission does not have to trust the operator or the utility — it can verify the sequence. This is the layer that turns a private commercial arrangement into something a regulator can approve and a lender can underwrite.

Exhibit C — Ratepayer benefit calculation

DOCKET A.26-04-018BAYSHORE ELECTRICPREPARED

Cedar Hollow DC-2 interconnects 250 MW at SUB47 under Schedule E-FLEX. Of that, 70 MW is contracted as interruptible and is dispatchable within a one-hour notice window. No transmission network upgrade is triggered, and no incremental generation capacity is procured to serve this load.

LineValueBasis
Incremental load served250 MWExecuted agreement
Network upgrade cost$0Avoided via flexible service
Incremental generation capacity0 MWServed within existing envelope
Annual revenue, new load$58.4MMetered, Sch. E-FLEX rates
Contribution to fixed cost recovery$41.2MNet of marginal energy cost
Residential customers of record3,840,000FERC Form 1, 2025
Average annual bill impact−$10.73Downward pressure per customer

Curtailment performance over the reporting period is attested by the chained event record referenced above. Any hour in which the facility failed to reduce to contracted depth within the notice window is excluded from the benefit calculation and assessed under §7.4.

Chain unverified — scenario not run
OUT

Signal out

A grid data feed tells you what the market did. The stack above lets Headroom emit what the facility must do — with the contractual and evidentiary fields attached, so an autonomous scheduler can act on it without a human in the loop.

A grid data feedNot actionable

          
Accurate. Leaves the interpretation, the obligation and the proof to you.
Headroom signalBinding & attested

          
Updates live with the scenario clock. Scrub the timeline and watch the tier and depth change.
Agent surface — MCPheadroom-mcp v1
Any orchestration layer — including a competitor's workload scheduler — can consume Headroom as an input.
Why the extra fields matter
FieldWho needs it
bindingThe scheduler — decides whether to checkpoint or ignore
capability_mwThe utility — the depth we have physically demonstrated
chain_headThe commission — the record this event will be verified against
settlementThe CFO — what this event is worth or costs
Prototype scope. Layers 01–04 of the flexible-load architecture, driven by a synthetic 168-hour scenario. Grid physics are simplified but directionally real: conductor rating responds to ambient temperature and wind speed, and the curtailment event is an evening net-load peak on a hot, still day after solar drop-off — the characteristic CAISO failure window. Hash chaining uses live SHA-256 in the browser. Rates, docket number, utility and facility are illustrative. Layer 05 — physical execution and witnessed transfer testing — is out of scope here and is the field-delivered half of the system.