The Data-Center Moratorium Map Is Not Anti-AI. It Is Local Government Asking For Receipts.

The June 8 data-center map is bigger than one town. Texas is trying to understand hundreds of planned data centers and a flood of large-load requests. New York has a statewide hyperscale moratorium bill waiting for the governor. Pasco County is considering a one-year pause. Seattle is preparing a vote while a downtown project may test vested-rights carveouts. Alvin, Texas, approved an official opposition resolution pending impact studies. Charlotte is now city-confirmed through its official FAQ, while Mesa remains an evening-watch item where the final record has to catch up with the public rumor stream.

The lazy version of this story says cities are blocking AI. The useful version says local governments are realizing they do not have the public-record tools to evaluate industrial-scale compute fast enough.

BadPD’s frame is simple: build the compute, but build it right. Bring power. Protect water. Publish interconnection and utility terms. Do not hide tax subsidies. Do not shift grid costs onto households. Do not dismiss residents as cranks when the public record is thin.

Texas: ERCOT’s Large-Load Problem Is Now A Local-Control Problem

The Texas Tribune reported June 8 that it identified at least 248 planned Texas data centers and that about half were aimed at unincorporated areas. The Tribune also reported that ERCOT received 519 requests to connect large electricity users in the last two years, compared with 24 the year before, and that estimated demand in those requests totaled 438,595 MW, with roughly 90% tied to data centers.

Those numbers should not be treated as all projects that will definitely be built. Interconnection queues can include speculative, duplicate, paused, or abandoned requests. But the scale of the queue is still an accountability receipt. Even a fraction of that demand changes the grid-planning conversation.

Texas also exposes the county-control problem. Developers often prefer land where zoning power is weak or fragmented. Residents then discover that the county may have limited tools to regulate noise, water, backup generation, tax incentives, construction traffic, and long-term utility consequences. If state law encourages a project to locate where public oversight is weakest, that is a policy design problem, not just a local complaint.

ERCOT’s large-load integration page and the Public Power summary of ERCOT’s Batch Zero process show that grid operators are trying to organize the wave. The missing public layer is project-by-project accountability: who brings power, who pays for upgrades, who gets curtailed during scarcity, which projects have batteries or microgrids, which use waterless or closed-loop cooling, and which rely on public infrastructure without public benefit.

New York: A Moratorium Bill With Utility Classes And Community Benefits

New York’s official Senate and Assembly releases say the Responsible Data Center Development Act passed both chambers. If Gov. Kathy Hochul signs it, the state would create a one-year moratorium on new permits for hyperscale data centers over 20 MW, while requiring environmental review, hearings, new electric and water rate classes, host-community benefits, labor standards, and domestic steel provisions.

That is a different kind of pause. It is not just a stop sign. It is a demand that state agencies write the rules before new hyperscale projects are allowed to reshape power and water systems.

Industry and economic-development voices may argue that the bill chills investment or overrides local decision-making. That argument deserves to be heard. But it is not enough to say AI is important. A 20 MW-plus facility is not a normal office user. If a project is large enough to change electric planning, water planning, emergency services, or rate design, it is large enough to need its own public class of review.

The New York bill also gives other states a checklist: environmental impact reporting, public hearings, separate utility rate treatment, community-benefit terms, labor standards, and project lists that can be audited. Michigan, Texas, Florida, Washington, and North Carolina should be watching.

Florida: Pasco County Wants Time To Write A Code That Actually Covers Data Centers

Axios Tampa Bay reported June 8 that Pasco commissioners are considering a one-year moratorium on large-scale data centers in unincorporated Pasco County. County administrator Mike Carabella said data centers have infrastructure and natural-resource implications and that current county code does not really regulate them. Tax Collector Mike Fasano raised consumer-cost concerns.

That is the kind of quote that turns a local story into a national pattern. A county is not necessarily saying no to compute. It is saying the current rulebook was not built for this type of load, scale, cooling, and backup-power profile.

The right question for Pasco is what the moratorium will build. The planning commission hearing and June 16 board vote should produce definitions, exemptions, active-application rules, water and electric review requirements, emergency-service standards, tax-incentive transparency, and a public schedule for final regulations.

Seattle: The Carveout Problem

Seattle’s official council materials said a proposed moratorium would take effect immediately on adoption for 365 days, unless extended, and would study grid capacity, water, environmental impacts, utility rates, land use, jobs, public health, and community well-being. The Guardian reported committee passage and a full council vote expected June 9. KIRO reported on a proposed downtown Digital Realty/co-location project at Third and Virginia and quoted the company distinguishing it from an AI data center.

The Seattle problem is not only whether a moratorium passes. It is whether projects that already submitted enough paperwork are exempt. WFAE reported a similar carveout question in Charlotte: anything with a full set of construction plans submitted before the moratorium would be exempt.

That is the practical loophole in many pauses. A moratorium can arrive after the key commitment has already been made. If cities want meaningful local control, the public needs early-warning systems, not just last-minute pauses.

Alvin: An Official Resolution Instead Of Rumor

The City of Alvin, Texas, posted notice of Resolution 26-R-25 expressing opposition to data-center construction or development within city limits until additional information, impact analysis, and regulatory considerations are evaluated. KPRC reported the council approved the resolution unanimously June 4 and that preliminary information described possible sites of 100 to 200 acres, initial electric load around 200 MW, and possible growth to 1 GW.

Alvin’s official language is useful because it names the missing lanes: electrical demand, water consumption, wastewater, drainage, transportation, emergency services, land-use compatibility, environmental sustainability, tax base, economic goals, and community character.

That is not anti-AI. That is exactly the list any serious project should be ready to answer.

Charlotte Is Now City-Confirmed; Mesa Still Needs The Final Record

Source-status update, June 19, 2026: Charlotte’s official data-center moratorium FAQ says City Council voted on June 8, 2026 to establish a moratorium on data centers. The FAQ says Charlotte is temporarily not accepting applications for new data centers, while projects with full and complete applications or prior approvals before June 8, 2026 can continue being built and existing data centers may continue operating.

The duration is now confirmed by the city: Charlotte’s City Council approved a 150-day moratorium during the June 8, 2026 meeting, and the FAQ says it lasts until Nov. 5, 2026. That moves Charlotte out of the rumor/watch lane and into the official-record lane.

The accountability frame stays the same: this is a build-it-right pause, not a blanket anti-compute ban. The city says the pause is intended to assess infrastructure capacity, noise impacts, and other environmental concerns before additional development proceeds. The next records to chase are the adopted ordinance text, final vote/minutes, the roster of exempt or vested projects, Duke Energy and Charlotte Water capacity analysis, emergency-response impacts, and the staff recommendations due before Nov. 5.

Charlotte also says it established an interdisciplinary group made up of staff from city and Mecklenburg County departments to research and recommend policy and solutions, engage external stakeholders, and offer community engagement opportunities. That group is now the records target: agendas, membership, public-comment channels, utility assumptions, and proposed conditions should be public before the moratorium clock runs out.

Mesa’s NTT data-center agenda confusion remains a watch item until the final vote record and project conditions are captured.

AZFamily reported that Mesa City Council was set to decide Monday on a 170-plus-acre NTT Data Group campus near Pecos and Crismon roads, with seven data-center buildings, more than 2.2 million square feet, a private power substation, and a new Salt River Project substation. But the final agenda review in the BadPD sweep did not clearly surface the item, and social chatter claimed the clerk said it was not on that night’s agenda. That is a classic source-discipline test. Treat the social claim as a lead. Do not publish passed, denied, or delayed without the clerk, minutes, agenda, or video.

What Build-It-Right Actually Means

The phrase can become empty unless BadPD keeps attaching it to public requirements.

Build-it-right means data centers should publish:

• electric load by phase and full buildout,
• interconnection costs and who pays them,
• backup generation type and emissions controls,
• battery, microgrid, or grid-support commitments,
• curtailment rules during emergencies,
• water source, water volume, and cooling method,
• wastewater and chemical handling,
• tax incentives, abatements, and clawbacks,
• community-benefit agreements,
• construction and permanent jobs,
• noise, traffic, and emergency-response studies,
• and developer identity, ownership, parent company, and financing structure.
• City of Charlotte: Frequently Asked Questions: Data Centers & Moratorium (Published June 8, 2026) – Official city FAQ confirming the council vote, 150-day duration, Nov. 5 end date, new-application pause, exemptions, and city/Mecklenburg review group.

If a developer has those receipts, publish them. If a city does not have authority to require them, the state should fix the authority gap. If a moratorium is needed to write the rules, use the pause to write the rules quickly and publicly.

The United States needs compute. Residents need water, power, disclosure, and bills they can afford. Those goals are not enemies unless governments let secrecy make them enemies.

Reader Safety And Source-Status Note

This article is an accountability receipt, not a rumor dump, graphic violence post, protected-class attack, or partisan certainty machine. Source dates stay attached. Claims are separated from confirmed records, and missing facts are named for follow-up.

Source Trail

• Texas Tribune: Texas data centers, electricity, power, water (June 8, 2026) – Texas data-center count, ERCOT request context, and local-control reporting.
• ERCOT: Large Load Integration (Accessed June 8, 2026) – Primary ERCOT large-load integration source.
• American Public Power Association: ERCOT Batch Zero (June 2026) – Large-load process context.
• NY Senate: Responsible Data Center Development Act passes (June 2026) – Official New York Senate sponsor release.
• NY Assembly: Data center moratorium bill release (June 2026) – Official Assembly release for statewide bill.
• Axios Tampa Bay: Pasco County data-center moratorium (June 8, 2026) – Pasco one-year moratorium reporting.
• Seattle City Council: data-center moratorium introduction (April 30, 2026) – Official Seattle council source.
• KIRO: Downtown Seattle data-center permit lane (June 2026) – Local report on potential carveout/vested-rights problem.
• City of Alvin: data-center resolution notice (June 2, 2026) – Official local resolution notice.
• KPRC: Alvin council approves data-center opposition resolution (June 5, 2026) – Local vote and project-scale reporting.
• WFAE: Charlotte 150-day moratorium details (June 2, 2026) – Charlotte carveout/application detail and June 8 vote watch.
• AZFamily: Mesa NTT data-center proposal (June 8, 2026) – Mesa project scale and agenda/vote watch.
• City of Charlotte: Frequently Asked Questions: Data Centers & Moratorium (Published June 8, 2026) – Official city FAQ confirming the council vote, 150-day duration, Nov. 5 end date, new-application pause, exemptions, and city/Mecklenburg review group.