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. This document identity index selects the source text for a contract, RFP, or commissioning script.

Choose the accelerator and counted reference population, then reconcile rack power, supporting IT, flow, fiber, ports and quoted dollars at their own boundaries; this appendix integrates two 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 — the terms of art, an applied dependency-schedule exercise, and the primary sources and communities that keep a project team’s decisions current.

Random failures and adversarial scenarios need distinct initiating evidence and controls; link them only where a validated topology shows that they converge on a shared top event or protective response.

An Ashburn design does not port to Frankfurt or Singapore unexamined: frequency, code, grid, water law, and climate shift across borders and re-decide choices from Parts 3 through 6, and this appendix names the deltas that force the redesign.