Claim before chart.
Every quantitative visual resolves to a structured claim and at least one direct source.
How this atlas knows what it knows
Methodology
The buildout moves quickly. Our method is designed to make uncertainty visible, preserve superseded evidence, and prevent a polished visual from outrunning the facts beneath it.
Follow one number
From source to something you can inspect.
Each step preserves the period, place, and limits of the original evidence.
- 01
Find the source
A primary document, specification, filing, or measured dataset.
- 02
Bound the claim
Attach its units, period, geography, classification, and method.
- 03
Explain the system
Use the claim in a chapter, diagram, or modeled assumption.
- 04
Review & preserve
Recheck changing claims and retain superseded records.
A real record · rack power
NVIDIA's DGX GB200 documentation describes a rack-scale system with 72 GPUs, 36 Grace CPUs, and an approximately 120 kW power envelope, with liquid cooling alongside air-cooled components.
Inspect this claim- Original source
- NVIDIA — NVIDIA DGX GB200 User Guide
- Classification & period
- vendor spec · DGX GB200 platform
- Scope & method
- Rack composition and approximate rated power transcribed from the current product manual.
- Use it in context
- Power System Rack dependencies Explore the planning model
Scope before comparison.
Power, water, carbon, capacity, and jobs are labeled by geography, time, and system boundary.
Ranges before certainty.
Forecasts retain their scenarios. Announcements are never silently converted into operating capacity.
Evidence hierarchy
Government datasets, standards, technical documentation, and audited filings are preferred. Vendor specifications support product-specific statements; representative polling supports public-opinion statements. Industry analysis is used for context when its methods and boundaries are clear.
- Company commitments are labeled as commitments, not outcomes.
- Hearing testimony is a stakeholder position, not representative polling.
- National averages are not substituted for fence-line or watershed effects.
- Requested, contracted, energized, peak, and average megawatts remain distinct.
Sources classified as market_data provide dated financial context, not live prices or evidence of operational criticality. Edition 01 freezes public-company market capitalizations at the August 28, 2026 close. The issuer, share-class, currency, fiscal-calendar, and comparability boundaries remain attached. Three-year consolidated-revenue histories are transcribed from issuer annual filings in the filing currency; market_data is used only for the dated market-cap snapshots. Consolidated revenue is not treated as a node-level operating metric. Forward-looking company measures appear only when direct management guidance closes the source, period, and accounting boundary; they remain classified as projections and are never blended with audited actuals or converted from a published range to an inferred midpoint.
Claim classes
- Fact
- A directly observed or durable technical statement supported by the cited evidence.
- Estimate
- A modeled or inferred value whose assumptions and boundary conditions must remain attached.
- Projection
- A future pathway, never presented as a promise or a single inevitable outcome.
- Vendor specification
- A product attribute published by its maker and valid only for the named configuration and date.
- Stakeholder position
- A documented concern, promise, or interpretation that is not treated as measured outcome.
System glossary
- PUE
- Total facility energy divided by IT equipment energy. It measures overhead, not useful compute or total impact.
- WUE
- Water usage effectiveness. Its boundary, water type, climate, and time period must be stated before comparison.
- HBM
- High-bandwidth memory: vertically stacked DRAM placed close to accelerators through advanced packaging.
- Tape-out
- The handoff of a verified chip design for mask creation and fabrication.
- Foundry
- A semiconductor manufacturer that fabricates designs for external customers.
- Scale-up fabric
- Links that make accelerators inside one tightly coupled compute domain behave as a larger system.
- Scale-out fabric
- The network connecting many servers or accelerator domains across a cluster.
- Interconnection
- The technical and commercial process for attaching a new generator or large load to the electric grid.
- PPA
- A power-purchase agreement: a financial or contractual energy arrangement that is not automatically the same as physical 24/7 supply.
Project states
Capacity is never promoted from a press release directly to an operating total. Projects move through these separately evidenced states.
- Announced
- A project has been publicly described; land, permits, utility service, finance, or construction may still be unresolved.
- Land controlled
- The developer has a site interest, without implying permission or power delivery.
- Permitted
- The named required approvals have been secured; scope and remaining permits must still be stated.
- Utility approved
- The utility or grid process has authorized a defined service arrangement, subject to its stated conditions.
- Under construction
- Physical work has begun; this is not treated as available capacity.
- Energized
- Electrical service is available to the project boundary or named phase.
- Operating
- The named phase is serving production workloads.
Review cadence
Content validation runs before every production build. Active claims that pass their review date fail the build until they are re-verified or superseded.
30days / high-volatility claims, including changing policy and forecasts
90days / medium-volatility claims
365days / low-volatility engineering explanations
Corrections & contact
Found an error, a broken link, or something that needs a clearer explanation? Email Ryan at ryan@intelligencebuildout.com.
For a correction, include the page or shared URL, the claim or passage, and what needs to change. A link to a primary source helps us review the issue and preserve the context of the original evidence.
Reading progress & preferences
Your reading position, Book or Focus preference, text size, and Atlas display preferences are saved in this browser on this device. There is no account or cross-device synchronization. Private browsing, clearing this site’s data, or switching browsers can remove or separate these settings.
You can share a volume, page, Atlas view, or Simulator scenario using its URL. Shared links contain the selected view or assumptions; they do not transfer your reading history. Use your browser’s site-data settings to clear saved preferences. The complete text edition also works without JavaScript.
The application includes no advertising or analytics trackers. The hosting provider may process ordinary request and security logs to serve and protect the site.
Edition record
Edition 01 · published August 29, 2026 · revised September 13, 2026
Edition revisions describe changes to the publication and its interface. Evidence verification dates belong to individual claims in the Sources ledger; a software release does not renew them. Market data retains its original edition snapshot date.
12 systems, 89 Atlas nodes ( 72 capabilities), 121 dependencies, 66 entities, 11 bounded facilities, 185 financial observations, 336 structured claims, and 193 sources. Superseded claims remain in the ledger with their replacement ID.
Named-entity roles cover 51 of 72 capabilities. Of the commercial capabilities, 33 currently have only one or two of the three-to-five representative entities targeted for this edition; 21 capabilities have no named role. Named endpoint context covers 112 of 121 dependencies; 0 currently identify a named organization as the documented performer of the exact relationship. The remaining 9 dependencies have no named endpoint context. Endpoint evidence and relationship evidence are displayed separately so proximity is never mistaken for direct participation, and every complete shortfall remains an explicit reviewed exception.
Edition 01 · Targeted evidence review
Rechecked claims approaching their September review deadlines against primary documents. Confirmed records carry individual verification dates; restricted or unresolved records retain their existing deadlines. Historical projections, announcements, and market snapshots retain their original periods.
Edition 01 · Interface and release preparation
Refined desktop and mobile Volumes, Atlas, Simulator, and Systems; prepared managed Node 24 deployment, security updates, page sharing, and a complete text edition. These software changes do not renew evidence verification dates.
Edition 01 · Atlas regional evidence closure
Restricted regional filtering to places with verified Atlas activity, connected evidenced facilities to their capability nodes, and added a source-closed Boise memory-fabrication pathway.
Edition 01 · Atlas operational graph v2
Expanded the Atlas into an evidence-backed capability, dependency, entity, facility, and financial-observation graph; public-company market capitalizations are a fixed edition snapshot from the August 28, 2026 close.
Edition 01 · Systems operational layer
Connected the twelve systems to evidence health, dependencies, actors, exact field-guide spreads, and adjacent planning tools.
Edition 01 · Volume evidence audit
Expanded all seven volumes with deeper analysis, current financial and infrastructure evidence, sixteen charts, and a licensed documentary-media ledger.
Edition 01 · Launch record
Published the guided story, twelve-system atlas, dependency graph, evidence ledger, and two sourced planning profiles.
Superseded claims
No claims were superseded in Edition 01.