Interpretation guideGUIDE-04

The public record becomes thinnest after infrastructure is operating.

C17 can be supported by an operating disclosure while C18 contracted use, C19 measured utilization or revenue and C20 sustained economic capacity remain unestablished. The subject of that limitation is the reviewed public record, not the underlying world.

Executive summary

Read the conclusion before the archive.

  1. Operating infrastructure is a threshold observation, not proof of customer use or economic output.
  2. Unknown project-level utilization or revenue is a public-evidence gap; it is neither zero nor proof of success.
  3. C20 requires durable, scoped evidence linking operation, use and economic output.

01 · Core argument

Visibility can decline after the physical project becomes real.

Permits, construction and energization often leave public traces. Customer use, utilization, revenue and sustained project economics may be private, aggregated or defined inconsistently.

The correct output is a bounded status and an explicit gap, not an invented bridge.

02 · Evidence transition

Operating status is the threshold, not the finish line.

Each downstream state needs a new observation and a stable denominator.

Signature model · C17–C20

The evidence boundary becomes less observable after operation

The gradient represents public-record visibility, not the existence or absence of private activity.

  1. C17Threshold observation

    Operating infrastructure

    A bounded operating statement or equivalent observation.

    Boundary: Does not establish customer use, utilization or project economics.

  2. C18Commercial bridge

    Contracted use

    A scoped arrangement linking operating capacity to customer use.

    Boundary: Contract scope, customer identity or capacity denominator may remain private.

  3. C19Measured downstream use

    Utilization or revenue

    A comparable measure with denominator, period and project scope.

    Boundary: Portfolio or company-wide metrics may not isolate the named project.

  4. C20Durable operating-economic bridge

    Sustained economic capacity

    Evidence connecting sustained operation, use and economic output.

    Boundary: Public project-level evidence is often absent or non-comparable.

Unknown is not zero. Missing public C18–C20 evidence is recorded as a scoped gap, not as proof of full utilization, failure or stranded capacity.

Reopen rule: advance only when a new source supplies the missing scoped contract, denominator, period, utilization observation or operating-economic bridge.

03 · Observability matrix

Separate what is visible, partially visible and not established.

The matrix describes the reviewed archive at its cutoff. It is not a statement that private activity does or does not exist.

More observable

Physical and regulatory traces

  • permits and land-use decisions
  • tariffs, dockets and service filings
  • construction and equipment disclosures
  • energization or operating statements

Partially observable

Commercial scope and customer use

  • contract maximums or backlog
  • company-defined active power
  • named-customer arrangements
  • portfolio-level operating metrics

Often not established

Comparable project economics

  • average operating MW
  • measured utilization denominator
  • project-level revenue contribution
  • sustained C20 evidence

04 · Editorial guardrails

Unknown is neither zero nor proof of success.

The Dark Zone requires symmetrical discipline against hype and doom.

Anti-hype boundary

A contract, active-power label, backlog figure or operating announcement does not automatically establish utilization, revenue or C20.

CLM-0005CLM-0180

Anti-doom boundary

When measured operating MW or project-level C20 evidence is not located, the recorded result is a public-evidence gap rather than a finding of zero activity.

NEG-0014NEG-0015

Decision boundary

C20 requires a documented bridge through the Dark Zone.

Permitted conclusion

Report the highest downstream state supported for the named scope and identify which C18–C20 observations remain unavailable or incomparable.

Prohibited stronger claim

Do not infer full utilization, project revenue, stranded capacity or economic failure from an upstream label or a missing public metric.

Quantitative ceiling
Portfolio backlog, active power and project MW remain distinct measures.
Causal ceiling
A public-record gap does not establish the cause of any operating or economic outcome.

05 · Claim register

The bounded finding at the cutoff.

Claim ceiling, exact locator and Linked sources remain visible for every load-bearing statement.

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-0180 · interpretation

RPO, revenue backlog, equipment backlog, active power, contracted power, cabinet utilization and development capacity are non-equivalent measures.

Claim ceiling
No cross-metric aggregation or conversion to economic compute without disclosed bridge data.
Evidence
Tier A · HIGH
Locator
Referenced filing definitions

CLM-0188 · interpretation

No inspected public filing establishes C20 sustained economic compute capacity for a named AI data-center project.

Claim ceiling
Company portfolio revenue or backlog cannot substitute for named-site C20 proof.
Evidence
Tier A · HIGH
Locator
Operating, contractual and financial disclosures inspected through cutoff

CLM-0206 · interpretation

No selected case reaches public C20 sustained economic compute capacity at cutoff.

Claim ceiling
Absence of public C20 proof is not proof that no private economic capacity exists.
Evidence
Tier A · HIGH
Locator
Case reachability profiles and named project disclosures

Rival tests inside the Dark Zone

CTR-0007 · Demand-quality problem

Contracted or installed capacity may not yield high utilization, customer use, revenue, or durable economic output.

Evidence result:NOVEC testimony shows a large difference between served and contracted aggregate load; the program’s C18–C20 states require later operating/economic evidence.

Ceiling effect:No contracted-to-utilized/economic conversion.

CTR-0048 · Backlog attrition and timing

RPO and order backlog may be recognized over years and may be reduced, deferred, cancelled or rescheduled.

Evidence result:Vertiv discloses cancellation/rescheduling risk; Cloud RPO schedules extend beyond 24–60 months; supplier backlog is undelivered.

Ceiling effect:Backlog is contractual exposure, not utilization or realized revenue.

CTR-0049 · Metric-boundary mismatch

Active power and cabinet utilization do not measure average consumption, MW-IT, accelerator utilization or economic output.

Evidence result:CoreWeave and Equinix use different portfolio metrics and exclusions.

Ceiling effect:No cross-company utilization ranking.

Public-record gaps

NEG-0014

Question checked:Is public measured operating MW available for the four bounded C17 project records?

UNKNOWN — PUBLIC EVIDENCE NOT LOCATED. Operating states are disclosed, but common measured average/peak operating load is not.

Implication:No aggregate operating MW; unknown must not be recorded as zero.

NEG-0015

Question checked:Is sustained economic compute capacity C20 publicly established for any bounded Pass 02 project?

UNKNOWN — PUBLIC EVIDENCE NOT LOCATED. No record jointly establishes sustained utilization, customer use and economic output at project level.

Implication:C20 remains unassigned.

06 · Maintenance

Evidence that can reopen C18–C20.

A useful update must add a scoped contract, measured utilization, comparable revenue observation or sustained operating/economic bridge.

Evidence that can reopen C18–C20

  • OIR-0020 · Public evidence provides measured operating load, commissioned IT capacity, customer-use, utilization, revenue/economic incidence, or independent verification for a C17 project.

    Required update: Verify unit, period, site boundary and source function; upgrade only the supported state; preserve contrary evidence and C18–C20 distinctions.

  • OIR-0048 · A company discloses a public bridge from RPO/backlog to delivered capacity, utilization or recognized revenue at a bounded project.

    Required update: Inspect contract schedule and project state; preserve recognition and delivery timing separately.

  • OIR-0049 · Comparable public utilization, average-load or C20 evidence becomes available for CoreWeave, Equinix xScale or a named operating AI cluster.

    Required update: Normalize meter boundary, time period, denominator, AI share and economic measure before state upgrade.

Record navigation

These records share claims or sources with this report. The linkage supports navigation, not a causal inference.

Bibliography and exact locators

  1. SRC-0001 — AI Compute Infrastructure — autonomous research operating prompt

    Operator-supplied controlling input · 2026-06-18 · CONTROLLING INPUT

    Locator: Full file; sections 0–14

    OPERATOR-SUPPLIED PROGRAM INPUT

  2. SRC-0002 — AI Compute Infrastructure — research seed charter

    Operator-supplied bounded brief · 2026-06-18 · BOUNDING INPUT

    Locator: Full file; sections 1–14

    OPERATOR-SUPPLIED PROGRAM INPUT

  3. SRC-0152 — Alphabet Inc. — Quarterly Report on Form 10-Q for quarter ended March 31, 2026

    Alphabet Inc. · 2026-04-23 · Tier A

    Locator: Lines 590; 1968–1972; 2206–2217; capital expenditures, Cloud RPO, asset placement in service

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  4. SRC-0154 — Quarterly Report on Form 10-Q for quarter ended February 28, 2026

    Oracle Corporation · 2026-03-10 · Tier A

    Locator: Lines 1666–1670, 2948, 6529–6756; RPO, power obligations, capex and financing

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  5. SRC-0155 — CoreWeave, Inc. — Annual Report on Form 10-K for year ended December 31, 2025

    CoreWeave, Inc. · 2026-02-27 · Tier A

    Locator: Lines 330–351; 3001–3041; active and contracted power, RPO, take-or-pay contracts, concentration and financing

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  6. SRC-0156 — CoreWeave Reports Strong First Quarter 2026 Results

    CoreWeave, Inc. / SEC Exhibit 99.1 · 2026-05-07 · Tier A-minus

    Locator: First-quarter 2026 financial highlights; revenue backlog $99.4 billion at 2026-03-31

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  7. SRC-0157 — Equinix, Inc. — Annual Report on Form 10-K for year ended December 31, 2025

    Equinix, Inc. · 2026-02-13 · Tier A

    Locator: Lines 350–384; 1044–1045; 1553–1571; 1736–1756; 2191–2198; 5739; 6154–6167

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  8. SRC-0162 — Eaton Corporation plc — Quarterly Report on Form 10-Q for quarter ended March 31, 2026

    Eaton Corporation plc · 2026-05-05 · Tier A

    Locator: Lines 492–493, 1128–1163; backlog, data-center demand, margins; acquisition notes lines 327–396

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  9. SRC-0163 — Vertiv Holdings Co — Annual Report on Form 10-K for year ended December 31, 2025

    Vertiv Holdings Co · 2026-02-18 · Tier A

    Locator: Lines 378–389 and 637–639; combined backlog, delivery expectation, cancellation/rescheduling risk

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  10. SRC-0164 — GE Vernova Reports First Quarter 2026 Financial Results

    GE Vernova Inc. / SEC Exhibit 99.1 · 2026-04-22 · Tier A-minus

    Locator: Lines 40–53; $2.4 billion Electrification equipment orders supporting data centers; total orders and revenue

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  11. SRC-0161 — Talen Energy Corporation — Quarterly Report on Form 10-Q for quarter ended March 31, 2026

    Talen Energy Corporation · 2026-05-05 · Tier A

    Locator: Glossary lines 2053–2056; revised AWS PPA up to 1,920 MW through 2042; transition in April 2026

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  12. SRC-0066 — Crusoe Announces Flagship Abilene Data Center is Live

    Crusoe · 2025-09-30 · Tier A-minus

    Locator: Construction began June 2024; first two buildings energized; first racks June 2025; early training and inference workloads running

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  13. SRC-0071 — Meta’s Kansas City Data Center is now operational

    Meta · 2025-08-01 · Tier A-minus

    Locator: Company statement that facility is operational and serving traffic

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  14. SRC-0072 — Colossus

    xAI · UNSTATED — CURRENT PAGE AT RETRIEVAL · Tier A-minus

    Locator: Company statement: 200,000 NVIDIA H100 GPUs in a single interconnected cluster

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  15. SRC-0068 — Mount Pleasant datacenter project update

    Microsoft · 2026-04-09 · Tier A-minus

    Locator: March 2026 update: Phase 1 nearing completion; Phase 2 construction; Phase 3 earthwork

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  16. SRC-0120 — Digital Gateway rezoning appeals opinion

    Court of Appeals of Virginia · 2026-03-31 · Tier A

    Locator: Opinion pp. 4–5 and 52–53; records identified in Pass 05

    PUBLIC OFFICIAL RECORD — CITE/SUMMARIZE

  17. SRC-0165 — Order Accepting Tariff Revisions, Subject to Condition — Conditional High Impact Large Load Service

    Federal Energy Regulatory Commission · 2026-06-05 · Tier A

    Locator: 195 FERC ¶ 61,196; paras. 6–7, 104–105; ordering paras. A–B; effective July 1, 2026

    PUBLIC OFFICIAL RECORD — CITE/SUMMARIZE

  18. SRC-0052 — NOVEC Evidence for Virginia Load Growth Technical Conference

    Virginia SCC docket / Northern Virginia Electric Cooperative · 2024-12-16 · Tier A-minus

    Locator: Testimony: 58 buildings; 1,408 MW served; 3,513 MW contracted

    PUBLIC OFFICIAL RECORD — CITE/SUMMARIZE

  19. SRC-0076 — Google announces new investment in Jackson County, Alabama data center

    Google · 2026-06-15 · Tier A-minus

    Locator: Existing campus operating since 2019; $1.5 billion expansion announced for 2026–2027

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  20. SRC-0065 — OpenAI, Oracle, and SoftBank expand Stargate with five new AI data center sites

    OpenAI · 2025-09-23 · Tier A-minus

    Locator: Site list; 5.5 GW group; 1.5 GW SoftBank group; nearly 7 GW portfolio statement; updated 2025-10-22

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  21. SRC-0067 — Crusoe Expands AI Data Center Campus in Abilene to 1.2 Gigawatts

    Crusoe · 2025-03-18 · Tier A-minus

    Locator: 1.2 GW total campus design; initial two-building phase; six additional buildings under construction

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  22. SRC-0069 — Infrastructure Explained: Meta Data Centers

    Meta · 2026-04-28 · Tier A-minus

    Locator: Richland Parish, Lebanon, El Paso and Tulsa construction status; selected future-site capacity statements

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  23. SRC-0070 — Meta’s Richland Parish Data Center supports Louisiana economy

    Meta · 2025-12-01 · Tier A-minus

    Locator: Groundbreaking December 2024; ongoing construction; four-million-square-foot future campus; Hyperion description

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  24. SRC-0073 — Locations of Google Data Centers

    Google · CONTINUOUSLY UPDATED — CURRENT PAGE · Tier A-minus

    Locator: North America list: Mesa, Arizona marked in development; Jackson County, Alabama listed without in-development marker

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  25. SRC-0074 — Google announces carbon-free energy plan for Mesa data center

    Google · 2024-03-14 · Tier A-minus

    Locator: Historical objective that Mesa data center was expected to be operational in 2025

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  26. SRC-0075 — Google announces Meitner energy center and data center in Texas

    Google · 2026-06-04 · Tier A-minus

    Locator: Announcement of data center and co-located new generation in Gray and Roberts Counties, Texas

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  27. SRC-0077 — Gov. Holcomb announces Amazon Web Services plans to invest $11B in northern Indiana

    Indiana Economic Development Corporation · 2024-04-25 · Tier A-minus

    Locator: Investment plan; performance-based incentives; dependency on long-term energy service agreements

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  28. SRC-0078 — Amazon data center locations and community project updates

    Amazon · CONTINUOUSLY UPDATED — 2025-10-30 ITEM · Tier A-minus

    Locator: October 30, 2025 Richmond County, North Carolina groundbreaking update and other dated project items

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  29. SRC-0079 — Amazon plans $20 billion investment in Pennsylvania cloud and AI infrastructure

    Amazon · 2025-06-09 · Tier A-minus

    Locator: Planned investment; first named sites in Salem Township and Falls Township

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  30. SRC-0080 — AWS plans $10 billion investment in North Carolina cloud and AI infrastructure

    Amazon · 2025-06-04 · Tier A-minus

    Locator: $10 billion announcement and Richmond County project plan

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  31. SRC-0081 — Amazon announces $3 billion Warren County, Mississippi data center investment

    Amazon · 2025-01-23 · Tier A-minus

    Locator: Warren County $3B plan; statement that two Madison County campuses were being developed

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE

  32. SRC-0082 — Amazon continues Mississippi expansion, announcing plans to invest a total of $25 billion across the state

    Mississippi Development Authority · 2026-04-09 · Tier A-minus

    Locator: $11B Madison County expansion; $1B Clinton retrofit; $25B cumulative planned statewide statement

    PUBLIC COMPANY/SEC RECORD — CITE/SUMMARIZE