Appendices & Reference Data

No single standard governs an AI data center; five overlapping regimes — resilience, thermal, efficiency, hardware, compliance — do, and they don't map one-to-one. These tables crosswalk them for a contract, RFP, or commissioning script.

Pick the archetype, accelerator generation, and scalable unit, and the megawatts, flow, fiber, ports, and dollars fall out of a handful of multipliers — this appendix supplies them and works three reference builds.

The irreversible decisions in this guide reduce to a handful of arithmetic checks; this appendix is the live calculator layer that runs them, plus the static reference tables that anchor it.

A number with no date, no source, and no caveat is not a fact — it is a rumor with a decimal point; this appendix is the live, date-stamped register that turns every volatile headline figure in the guide into one you can re-check before you bet a slab, an interconnection slot, or a financing structure on it.

Three reference layers for the bench — a glossary of every term of art, the 24–60 month land-to-go-live schedule as one critical-path table, and the feeds that keep the numbers current.

Every failure mode is dual-use — reachable as a random fault or an attacker's objective — so each gets one record (trigger, propagation, detection, blast radius, mitigation, recovery) feeding the availability model of Chapter 12.5.

A design correct in Ashburn is non-compliant, mis-cooled, and under-powered in Frankfurt or Singapore, because frequency, code, grid, water law, and climate shift across borders and re-decide choices from Parts 3 through 6.