Methodology

The conversion chain is a sequence of distinct public-record tests.

A later state is recorded only when function-appropriate evidence supports it. No wording, badge or figure carries a project beyond the exact state and scope established by the source record.

Four operating rules

01

Preserve exact state

Every assertion names the C-code, bounded scope, supporting claim and source IDs, verification date and reopen trigger.

02

Preserve unit basis

Requested, studied, approved, contracted, deliverable, energized, average, peak, MW-IT and forecast values remain separate.

03

Publish the ceiling

The page says what the evidence establishes and what it does not establish, including relevant contrary evidence and negative findings.

04

Update by trigger

A record changes after a specified public event or document is checked, not because time passed or an announcement sounded definitive.

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

C7–C10 · service-model fork

“Grid interconnection” is not one national pathway.

Before a C7–C10 state is assigned, the record must identify the authority, instrument and service model that governs the load.

CLM-0053TERM-120

  1. 01Retail large-load service
  2. 02Transmission service
  3. 03Generator interconnection
  4. 04Co-location
  5. 05Behind-the-meter

CLM-0053 · interpretation

No single U.S. “grid interconnection” state applies to all large loads: retail load service/interconnection, transmission service, generator interconnection, co-location, and behind-the-meter arrangements use different actors, instruments, studies, and jurisdictional pathways.

Claim ceiling
Pathway distinction only; no single source establishes a nationally uniform process.
Evidence
Tier A-minus · HIGH
Locator
FERC RM26-4 overview; FERC PJM order summary; MISO current-rules page; CAISO issue paper pp. 3-8; PJM pathway presentations
Linked sources
SRC-0003SRC-0010SRC-0085SRC-0087SRC-0088SRC-0089SRC-0097SRC-0098

Unit integrity

Numbers remain attached to their state and boundary.

CLM-0005 · interpretation

Announced, requested, approved, contracted, deliverable, energized, installed, utilized, and economically productive capacity are non-equivalent states and units.

Claim ceiling
No conversion without an explicit method and evidence.
Evidence
CONTROLLING/BOUNDING INPUT · HIGH
Locator
Operating Prompt §7; Seed Charter §6
Linked sources
SRC-0001internal recordSRC-0002internal record

CLM-0033 · interpretation

TWh/year, equivalent average GW, source-defined facility capacity, system peak GW, requested load, design capacity, MW-IT, GPU count, and announced capex are non-interchangeable metrics and are held in separate comparable groups.

Claim ceiling
Normalization rule; no conversion beyond explicit formula and assumptions.
Evidence
Tier A + CONTROLLING INPUT · HIGH
Locator
Operating Prompt §§7–8; Seed Charter §§3,6; quantitative source locators in Pass 02 ledgers
Linked sources
SRC-0001internal recordSRC-0002internal recordSRC-0023SRC-0012SRC-0018

C0–C21

State definitions and non-proof rules

Code order describes the ontology. It is not a completion percentage, probability or quality score.

  1. C0Concept or rumor

    Establishes: A dated record supports only a concept, rumor, or pre-announcement indication.

    Does not prove: A public announcement, site, land right, permit, utility request, contract, construction, power delivery, operation, use, utilization, revenue, or economic capacity.

  2. C1Public announcement

    Establishes: A public party has announced a bounded project or plan.

    Does not prove: A secured site, land control, zoning, utility request, approved service, agreement, funded upgrade, construction, energized power, operation, utilization, or economic capacity.

  3. C2Site identified

    Establishes: A location has been publicly identified for the bounded scope.

    Does not prove: A land option or control, zoning application/approval, service request, agreement, construction, energized power, operation, or economic capacity.

  4. C3Land option or negotiation

    Establishes: A land option or active negotiation is evidenced for the bounded scope.

    Does not prove: Land control, zoning approval, utility service, agreement, construction, energized power, operation, or economic capacity.

  5. C4Land controlled

    Establishes: The relevant land is controlled under the evidenced instrument and scope.

    Does not prove: Zoning approval, utility service, agreement, construction, energized power, operation, or economic capacity.

  6. C5Zoning or land-use application

    Establishes: A zoning or land-use application has been filed.

    Does not prove: Approval, survival of appeal, utility service, agreement, construction, energized power, operation, or economic capacity.

  7. C6Zoning or land-use approval

    Establishes: A specified land-use approval has been granted.

    Does not prove: Finality against appeal, utility service, deliverability, agreement, construction, energized power, operation, or economic capacity.

  8. C7Utility service or interconnection request

    Establishes: A request entered the applicable utility/interconnection process for the stated scope.

    Does not prove: Study acceptance, approval, deliverability, tariff pathway, executed agreement, construction, energized load, operation, or economic capacity.

  9. C8Study or review accepted

    Establishes: A specified study/review has been accepted or entered the evidenced stage.

    Does not prove: A service pathway, executed agreement, funded upgrades, deliverable/firm power, construction, energization, operation, or economic capacity.

  10. C9Tariff or service pathway identified

    Establishes: An applicable tariff, service category, or regulatory pathway exists for the stated scope.

    Does not prove: Customer participation, executed agreement, funded upgrades, deliverability, construction, energized power, operation, or economic capacity.

  11. C10Agreement executed or obligation recorded

    Establishes: A specified agreement or binding obligation is evidenced.

    Does not prove: Physical delivery, firm/deliverable service beyond the instrument, funded or completed upgrades, construction, energization, commissioning, operation, use, utilization, or economic capacity.

  12. C11Network, generation, or facility upgrades funded

    Establishes: Funding or financial responsibility for specified upgrades is evidenced.

    Does not prove: Completed upgrades, equipment delivery, energization, commissioning, IT installation, operation, use, utilization, or economic capacity.

  13. C12Construction started

    Establishes: Physical construction has begun for the specified scope.

    Does not prove: Equipment delivery, completed facility, energization, commissioning, IT installation, cluster operation, customer use, utilization/revenue, or economic capacity.

  14. C13Major electrical and cooling equipment delivered

    Establishes: Specified major equipment has been delivered for the bounded scope.

    Does not prove: Installation, energization, commissioning, IT installation, cluster operation, customer use, utilization/revenue, or economic capacity.

  15. C14Grid or onsite supply energized

    Establishes: The specified electrical supply or facility scope has been energized.

    Does not prove: Full commissioning, stated MW operating continuously, IT installation, cluster operation, customer use, utilization/revenue, or economic capacity.

  16. C15Facility commissioned

    Establishes: The specified facility/system has passed the evidenced commissioning or acceptance scope.

    Does not prove: IT installation, cluster operation, customer use, utilization/revenue, sustained economics, or completion of unevidenced phases.

  17. C16IT capacity installed

    Establishes: The specified IT capacity has been installed.

    Does not prove: Cluster operation, customer use, measured utilization, revenue effect, sustained economic capacity, or equivalence to site power.

  18. C17Compute cluster operating

    Establishes: The specified compute cluster is operating under the evidenced source and scope.

    Does not prove: Measured operating MW, customer use, utilization, revenue, profitability, sustained economic capacity, or operation of every phase.

  19. C18Contracted customer use observed

    Establishes: Customer workload or contracted use is observed for the specified scope.

    Does not prove: Measured utilization/revenue at the required basis, profitability, sustained economic capacity, or permanence.

  20. C19Utilization or revenue effect observed

    Establishes: Specified utilization or revenue evidence is observed for the defined period and boundary.

    Does not prove: Sustained economic capacity outside the evidenced period/scope, profitability unless shown, permanence, or full-campus realization.

  21. C20Sustained economic compute capacity

    Establishes: Sustained economic operation is evidenced for the stated boundary, method, and period.

    Does not prove: Permanence, all phases or sites, future growth, general market success, or transferability beyond the evidenced scope.

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

    Establishes: An adverse or changed-status subtype is evidenced for the specified scope and date.

    Does not prove: A universal terminal state, erasure of historical states, final cancellation when only delay/appeal is shown, or failure of related phases/projects.

Traceability model

Every material statement has a path back to evidence.

Official sourceAtomic claimTyped objectPage componentReopen trigger

Contrary evidence narrows the permitted claim. A negative finding records what the reviewed public record did not establish. Rights controls determine whether the site may link, paraphrase or exclude material.

Read the evidence and editorial standards

Institutional control

No single actor controls the complete chain.

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
Linked sources
SRC-0003SRC-0083SRC-0114SRC-0120SRC-0165