Category Discipline
A short excerpt from _Legitimacy Is Infrastructure_
The strongest idea in this paper is not "data centers are good."
It is not even "publish a better checklist."
The strongest idea is category discipline.
A serious builder may already know many of the individual tools in the full paper. That is not the point. The point is that tools scattered across sustainability, permitting, utilities, construction, security, communications, and community teams do not add up to legitimacy unless they are wired together as one proof system before the narrative hardens.
Right now, the public argument often turns "data center" into one object. Water use, construction water, operating cooling, indirect power-generation water, grid upgrades, ratepayer risk, construction dust, brown-water allegations, backup generators, gas turbines, noise, tax breaks, limited permanent jobs, AI job anxiety, e-waste, and foreign strategic competition all get compressed into one moral symbol.
That compression is dangerous for everyone.
It is dangerous for communities because real harms become harder to fix when everything becomes one outrage object. A resident with brown water needs testing, source tracing, pressure logs, construction timelines, well data, utility records, and remediation. A generic debate about "AI water" does not fix their sink.
It is dangerous for builders because a fixable construction, metering, rate, noise, or stormwater problem can become evidence that the entire AI infrastructure project is anti-community.
It is dangerous for policymakers because blunt pauses and weak disclosure rules can either let bad projects through or freeze good projects unnecessarily.
It is dangerous for the country because strategic compute capacity can become politically fragile before the infrastructure is mature enough to defend itself.
The category changes the fix. It does not erase the duty to fix.
That sentence matters.
| Collapsed public claim | Correct category split | What the proof should show |
|---|---|---|
| "Data centers use too much water." | Operating cooling water, construction water, indirect electricity water, peak public-system draw, source, timing, basin stress. | Annual and peak demand, source, withdrawal vs consumption, drought mode, utility capacity, and verification. |
| "Data centers contaminate water." | Water quality incident, construction stormwater, sediment/turbidity, wastewater discharge, pipe damage, treatment capacity. | Lab results, permits, incident records, location, pathway, responsible party, remediation, and unresolved uncertainty. |
| "Data centers make bills rise." | Generation, transmission, distribution, capacity markets, interconnection upgrades, tariff design, tax incentives, stranded asset risk. | Cost causation, who pays, ratepayer protections, utility filings, load shape, and upgrade allocation. |
| "Data centers are noisy." | Construction noise, cooling equipment, transformers, substations, backup generators, continuous turbines, truck traffic, low-frequency/tonal sound. | Baseline, modeled sources, frequency bands, nighttime receptors, mitigation, monitoring, and fix obligations. |
| "Community benefit buys support." | Impact mitigation, enforceable benefits, one-time donations, workforce claims, public dashboards, successor obligations. | What is legally binding, maintained, funded, monitored, reported, and separate from unresolved harm. |
| "Clean energy solves it." | Annual matching, hourly CFE, physical deliverability, firm power, backup generation, demand response, workload flexibility. | Which claim is being made, during which hours, on which grid, with what firm capacity and what local impacts. |
The first job is not persuasion. The first job is classification.
A water-consumption complaint, a stormwater violation, a wetlands permit, a construction-metering failure, a wastewater-discharge concern, and a drought-basin conflict are not the same claim. Treating them as the same claim helps both bad PR and bad criticism.
But category discipline is not responsibility laundering. A company cannot say "that was a contractor issue" and then act confused when the public associates it with the project. The community does not experience your category map. The community experiences dirty water, higher bills, trucks, dust, hum, secrecy, and confusion. The burden is on the builder to make the categories legible before the public has to infer them from headlines.
If a pipe strike, missing construction meter, bad stormwater inspection, unclear ratepayer exposure, or poorly muffled generator becomes the public's proof that AI infrastructure is reckless, that is not because the incident was too small. It is because the proof layer was too weak.
Full paper:
<https://saucony.github.io/legitimacy-is-infrastructure/>