Where AI policy stops being about models and becomes about land, water, and power
Most of the AI debate is conducted at a level of abstraction that never touches ground — capability thresholds, evaluation regimes, preemption doctrine. Data centers are where it lands. More than 4,400 registered facilities now operate across the United States, with at least one in every state, and the fights they generate are about the oldest questions in American governance: who decides what gets built, who pays for the infrastructure it requires, and who absorbs what it emits.
This is also the arena where the industry-layer analysis is most visible. Hyperscalers carry nearly all of the physical exposure. Frontier labs carry it indirectly, through the lease commitments that underwrite construction — and those commitments transfer, as the disclosure of a competitor renting frontier-scale capacity from a rival's fleet made plain. The app layer, which consumes the capacity all of this exists to supply, carries none of it, which is why app-layer companies are absent from these fights entirely.
The proposals that engage sort along a single spectrum: whether a community may refuse a facility, or may only negotiate its terms. Everything below the halt-and-consent end accepts the buildout as given and argues about conditions.
5 of 17 proposals say anything specific about data centers
The only proposal seeking to stop the buildout at national scale rather than condition it. Treats data center expansion as an environmental and energy question first, and is the single proposal that put the environmental footprint of AI infrastructure on the agenda before it became a local political force.
Who decides: The federal government, by halting construction outright
The only item on the map that asserts a right to refuse construction outright, and the only one that defends local authority against state preemption rather than state authority against federal preemption.
Who decides: The affected community, through county and municipal authority
The most precisely engineered instrument aimed at data centers. Mandatory public disclosure of energy, water, emissions, and backup generation, with federal bonus depreciation conditioned on meeting efficiency standards — and the revenue recovered from limiting that subsidy dedicated to the workers the infrastructure displaces.
Who decides: The federal tax code, through conditioned depreciation
Accepts the buildout and sets terms: data centers must serve host communities through local hiring, computing resources for schools and libraries, dry cooling to protect water supplies, and payment of their full electricity costs rather than shifting them onto ratepayers.
Who decides: Federal standards on what a host community is owed
Engages data centers on exactly one question: residential ratepayers must not bear increased electricity costs. Siting, water, emissions, noise, subsidies, and local authority are all left untouched, and the framework's preemption agenda cuts against the state and local rules that currently govern them.
Who decides: Utility regulators, on cost allocation only
Which contested questions each proposal actually reaches
| Proposal | Siting | Power | Water | Air / noise | Tax | Jobs | Who decides |
|---|---|---|---|---|---|---|---|
| Sanders | — | — | — | ||||
| DC Bill of Rights | |||||||
| Warner | — | — | — | ||||
| Khanna | — | — | — | — | |||
| WH Framework | — | — | — | — | — | — |
What is actually being fought over, issue by issue
Where a facility may be built, how close to homes and schools, and whether a community can refuse one outright. This is the question the local fights are actually about, and the one federal proposals most consistently skip.
Who pays for the generation and transmission a large load requires. The recurring concern is cost-shifting — a facility contracts for cheap power while households and small businesses absorb the system upgrades through their bills.
Cooling withdrawals and consumption, disclosure to local providers, and siting in water-stressed regions. Projections reach up to 32 billion gallons a year by 2028, against a baseline that is largely unmeasured because operators are not required to report.
Diesel backup generators, gas turbines, and cooling systems produce emissions and persistent low-frequency noise. These are the harms nearby residents report first and the ones with the clearest documented health pathway.
Sales and property tax abatements, federal bonus depreciation, and whether public subsidy carries conditions. The live question is whether incentives granted against job promises can be recovered when the jobs do not appear.
Construction employment is substantial and temporary; permanent operations employment is small, often under 150 workers at even the largest facilities. The gap between the two numbers drives most of the local political conflict.
Whether counties and municipalities keep authority over siting or are overridden by their state. Note the inversion: in data center politics the preemption fight runs state-over-local, not federal-over-state.
12 proposals say nothing specific about data centers
The omission is structured, not random. Proposals built around model capability — the frontier safety frameworks, the state transparency laws, the evaluation regimes — treat AI as software and have no vocabulary for land use. Proposals built around workers and taxation reach the buildout only through the tax code, if at all. The result is that the most locally contentious consequence of AI development is absent from most of the documents that claim to govern it.