Registry control plane

Coverage that helps editors see what is controlled — and what is not.

Counts below describe record governance, not capacity, market share or project realization.

Records in view
1
Typed objects only
Exact state handling
0
Single bounded project state
Scoped handling
1
Composite, framework or non-project
Latest verification
Archive cutoff, not live monitoring

Record-control coverage

  • Source IDs1/1
  • Reopen triggers1/1
  • Unit-basis fields1/1
  • Public-gap fields1/1
  • Profile routes1/1

Four-register governance

  1. R01
    Load

    Every figure remains attached to its raw wording, unit basis, state basis and geography.

    1 governed
  2. R02
    Supply

    Service, deliverability and generation pathways remain separate from load and compute operation.

    1 governed
  3. R03
    Money

    Capex, backlog, contracted power and revenue are never treated as interchangeable measures.

    1 governed
  4. R04
    AI-share

    Data-center activity is not converted into AI-only activity without a source-stated allocation.

    1 governed

Controlled records

Forecasts registry

Open a profile for the complete state basis, source IDs, public-record gap and reopening condition.

PS-0003P1

PJM AEP-zone large-load forecast cohort

Ohio/PJM AEP zone

State handling

FORECAST — NO PROJECT C-STATE

No project state

Recorded figure

See 2026 forecast and FERC Figure 7

Forecast MW by year/zone
Evidence controls and maintenance notes
Record scope
Aggregate forecast cohort
State basis
PJM screened forecast adjustment
AI connection
Data-center/large-load category; AI share not established
Confidence
HIGH for forecast vintage
Public-record gap
Project-level mapping and realization
Source controls
3 source IDs ·SRC-0012SRC-0029SRC-0032
Reopen condition
OIR-0008
Aggregation policy
Not summable with other tracker figures.
Stewardship desk
Forecast & methods desk
Review posture
Critical evidence watch · 55 days old at edition