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

Technical dependencies registry

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

State handling

UNKNOWN — PUBLIC EVIDENCE NOT LOCATED

Unknown public evidence

Recorded figure

No capacity counted
Evidence controls and maintenance notes
Record scope
Technical case candidate
State basis
Mentioned in official market review as a source lead; primary report not yet acquired
AI connection
Computational-load relevance; AI-specific transferability unverified
Confidence
LOW
Public-record gap
Primary report, protocol, measured performance, customer obligations
Source controls
1 source ID ·SRC-0012
Reopen condition
OIR-0009
Aggregation policy
Not summable with other tracker figures.
Stewardship desk
Technical systems desk
Review posture
High-priority evidence watch · 55 days old at edition