AI compute infrastructure · public-record intelligence

Release 2026.06Evidence cutoff 18 Jun 2026

Trace infrastructure claims from announcement to observable economic use.

The Ledger separates intent, permission, service, construction, energization, operating compute and economic observation. Every selected record retains its exact object type, state basis, unit boundary, sources, contrary evidence and update conditions.

Inspect the evidence ledger Understand the method
  • Exact statesNo inferred progress between C-states
  • Typed objectsProjects, cohorts, forecasts and frameworks stay distinct
  • Bounded figuresNo synthetic capacity total

01

State integrity

Requested, contracted, energized and operating are not synonyms.

02

Register integrity

Load, supply, money and AI-share require explicit bridges.

03

Source integrity

Claims retain source IDs, exact locators and contrary evidence.

04

Update integrity

Records move only when a defined evidence trigger is met.

Conversion-chain orientation

Twenty-two states. Five evidence zones. No shortcut between them.

The C-state ladder is a controlled vocabulary, not a prediction that every project follows one linear path. Each code states only what the cited public record establishes for a bounded scope.

  1. 01

    C0–C6

    Intent, site and permission

    From concept or announcement through a bounded site, land position and land-use approval.

    1. C0Concept or rumor
    2. C1Public announcement
    3. C2Site identified
    4. C3Land option or negotiation
    5. C4Land controlled
    6. C5Zoning or land-use application
    7. C6Zoning or land-use approval

  2. 02

    C7–C10

    Service-model fork

    Requests, accepted studies, tariff pathways and executed obligations remain separate claims.

    1. C7Utility service or interconnection request
    2. C8Study or review accepted
    3. C9Tariff or service pathway identified
    4. C10Agreement executed or obligation recorded
    Inspect the C7–C10 service-model fork

  3. 03

    C11–C17

    Physical delivery

    Funded upgrades, construction, equipment, energization, commissioning, installed IT and operating clusters.

    1. C11Network, generation, or facility upgrades funded
    2. C12Construction started
    3. C13Major electrical and cooling equipment delivered
    4. C14Grid or onsite supply energized
    5. C15Facility commissioned
    6. C16IT capacity installed
    7. C17Compute cluster operating

  4. 04

    C18–C20

    Observed economic use

    Customer use, utilization or revenue effects, and sustained economic compute capacity require distinct evidence.

    1. C18Contracted customer use observed
    2. C19Utilization or revenue effect observed
    3. C20Sustained economic compute capacity
    Inspect the C18–C20 Dark Zone

  5. 05

    C21

    Changed status

    Delay, cancellation, downsizing, supersession or repurposing is recorded without erasing the prior history.

    1. C21Delayed, cancelled, downsized, superseded, or repurposed

Also controlled: MIXED, N/A and UNKNOWN prevent aggregate, framework and missing-public-evidence records from being forced into a project state.

Choose the working view

A clear entry point for each evidence task.

The same record can support executive orientation, analytical verification and editorial maintenance without changing its evidentiary ceiling.

01

Decision makers

See where a public claim stops.

Use bounded case clusters and interpretation guides to distinguish an announced plan from delivered, operating or economically observed capacity.

Review case clustersOpen interpretation guides

02

Analysts and researchers

Inspect the underlying record.

Work from typed objects, exact state handling, raw units, claim ceilings, contrary evidence, negative findings and source locators.

Inspect 37 recordsRead the method

03

Editors and record owners

Understand what can be updated.

Check evidence standards, controlled terminology, review cutoffs and the triggers required before a record can move or a claim can strengthen.

Review evidence standardsSee update status

Four-register discipline

Every figure stays inside its evidentiary register.

Movement between registers requires an explicit, source-stated bridge. Missing bridge data remains unknown rather than being imputed.

  1. R01

    Load

    Requests, forecasts, design power, energized load, average MW and energy remain distinct.

    CLM-0005CLM-0033

  2. R02

    Supply

    Service model, deliverability, generation and physical inputs stay attached to their own pathway.

    CLM-0053

  3. R03

    Money

    Capex, backlog, RPO, contracted power, revenue and utilization are not bridge-equivalent.

    CLM-0180

  4. R04

    AI-share

    Total data-center measures are not AI-only unless the source supplies the cut.

    CLM-0029

Selected case clusters

Read the bottleneck, not just the announcement.

Each case follows the interaction between permissions, service pathways, physical delivery and the strongest claim the available evidence permits.

View all eight case clusters

Interpretation guides

Four boundaries that determine what the record can support.

Use these short guides before comparing records, adding megawatts or treating a company-level statement as site-level evidence.

  1. 01

    Conversion states

    From announcement to economic capacity

    What every transition establishes — and what it still does not prove.

    →

  2. 02

    Unit boundaries

    Why megawatts do not add up

    Why load, supply, money and AI-share figures cannot be collapsed into one total.

    →

  3. 03

    Distributed control

    Who controls the conversion chain

    Which actor controls each permission, contract, physical input and observation.

    →

  4. 04

    C18–C20

    Where the public record goes dark

    Why operating compute is not the same as observed customer use or sustained economics.

    →

Publication boundary

A disciplined evidence product, not a census, ranking or outcome forecast.

The selected records are designed to test conversion claims and evidence gaps. They do not represent total market capacity, a complete project universe or a probability-weighted forecast.

Review the evidence standard

CLM-0038 · interpretation

Pass 02 did not locate a unified authoritative public registry that reconciles all U.S. data-center projects through announcement, request, approval, construction, energization, commissioning, operation, utilization, and economic output; the project ledger is a bounded evidence sample, not a national census.

Claim ceiling
Bounded sample only; no national project count or aggregate operating MW.
Evidence
Tier B · HIGH for absence from searched public sources; not proof none exists
Locator
National data limitations and large-load forecasting literature; search protocol recorded in Pass 02 metadata
Linked sources
SRC-0023SRC-0060

CLM-0207 · interpretation

The case portfolio supports a modular permission stack controlled by different actors; no single regulator, utility, company or locality controls the full conversion chain.

Claim ceiling
Portfolio-level institutional finding; does not establish identical sequencing in every jurisdiction.
Evidence
Tier A · HIGH mechanism
Locator
Federal, RTO, state commission, court and project records