The Triptych Said This Would Happen
I closed Part III on Monday with one sentence that I want you to read again before we go further:
The architecture is older than the Manhattan Project. The Manhattan Project is the name we give to one cycle of it. We are watching another cycle now, and the receiving end has not been told.
Three days later the receipts started landing. Two of them inside the same week of May 2026. One in a wealthy Atlanta suburb. One in the Sonoran desert outside Tucson. Both stories follow the same script. A community discovers, almost by accident, that an AI data center developer has been taking water it was not supposed to take. The developer says the water use was normal. The local government says it was a paperwork error. The community says it was theft. The reporting moves on in three days. The water keeps flowing.
The reason these two stories matter is not that they are scandals. They are not, technically, scandals. Both developers paid the bills they were asked to pay. Both county and city governments described their response as appropriate. No one was prosecuted. No one will be. The reason the stories matter is that they show you what the architecture looks like when the curtain slips for a second — what a community sees when it finally turns around and asks where the water went.
This is Watch the Water. It is the first continuation of the Manhattan Architecture series. It is not Part IV. It is the receipts on what Parts I, II, and III mapped.
Project Excalibur, Fayette County, Georgia
A 615-acre data center campus 20 miles south of Atlanta. Codenamed Project Excalibur. Developer: Quality Technology Services, owned by Blackstone — the largest alternative-asset manager in the world, with roughly $1.2 trillion under management. Current build: 13 buildings totaling 6.2 million square feet. Planned build: up to 16 buildings at full buildout. Projected annual property tax revenue to the city of Fayetteville: $150 to $200 million.
Last year, residents of a wealthy subdivision next to the campus called Annelise Park noticed their water pressure dropping. They called the county. The county told them to stop watering their lawns. Georgia was in a drought. The state was on fire. The wells were thinning.
The residents kept asking. Eventually a local attorney named James Clifton — who is also a candidate for the Fayette County Board of Commissioners — filed a public-records request. What he got back was a May 15, 2025 letter from the Fayette County Water System to QTS. The letter said the developer owed the county $147,474 in retroactive billing for water that had flowed through two industrial-scale connections the county had not been collecting on. One of the connections, the county said in writing, had been installed without the knowledge or inspection of the county water system. The other one existed in the records but was not linked to QTS's billing account.
The volume the county had failed to bill for: 29 million gallons.
For context. 29 million gallons is roughly the daily water consumption of an American town of several thousand people. It is 44 Olympic-sized swimming pools. It is, depending on which side of the dispute you believe, somewhere between four months and fifteen months of unbilled water — the county said four, the developer said nine to fifteen. The water flowed through the connections during the same period in which the county was telling residents to stop watering their lawns. It flowed during a drought emergency. It flowed past meters the utility had not been reading.
The retroactive bill was not a fine. Fayette County Water System Director Vanessa Tigert said on the record that her department chose not to fine QTS. Her quoted explanation:
They're our largest customer, and we have to be partners. It's called customer service.
That sentence is the architecture in one line.
QTS paid the bill and disputed the timeline. The company said the water had been used for construction-related demand — dust control, concrete, site preparation — and that its operational data center cooling uses a closed-loop system that does not consume municipal water. Anyone who read Part III will recognize the closed-loop framing as the same language Krystal Two Bulls flagged on Democracy Now! as verifiably misleading, because the cooling-tower evaporative rejection of heat consumes water regardless of what the internal loop does.
The county administrator, asked to comment, said the unmetered water was the result of a procedural error during the county's transition to a new cloud-based smart-meter system. One of the two meters was still being read under the old system after the conversion. The county thought it was reading the meter electronically. It was not. The bill that resulted was a six-month cumulative bill, not a single-month spike. The administrator said the framing of the story as theft was overheated. QTS, in a statement, called any suggestion of improper water use by QTS categorically false.
This is where the story gets structurally interesting.
The county's explanation and the developer's explanation are coordinated. They are saying the same thing. They are describing what happened as a paperwork problem inside the utility's billing transition, not as a developer taking water it should not have been taking. The residents and the attorney who filed the records request are saying it was the latter. Both narratives are partly true. The architecture survives by ensuring that the narrative the regulator and the regulated entity agree on is the narrative that makes it into the next news cycle.
What the county did not do is fine the developer. It billed the developer for what it could prove had flowed. It chose not to use its enforcement authority on a customer it described, in writing, as a partner. The residents of Annelise Park kept being told to stop watering their lawns.
A footnote worth holding: Fayetteville's city council passed Ordinance 26-0-12 earlier this year, banning new data centers in every zoning district within city limits. The city was already trying to slow the build. The QTS campus had been approved before the ban. It will continue to expand. The city of Fayetteville is one of at least 50 cities across the United States with active moratoriums on new data center construction. Four of those are permanent. The reason the city banned new construction is that the existing build already overwhelmed the systems the city had in place to monitor it.
Project Blue, Tucson, Arizona
Different state. Different desert. Same script, different vehicle.
In August 2025, the Tucson City Council voted unanimously to reject any city involvement with a 290-acre data center development called Project Blue on land south of Tucson near the Pima County Fairgrounds. The developer is Beale Infrastructure. The end-tenant, according to the contemporaneous reporting at the time of the council vote, is potentially tied to tech giant Amazon. The council's stated reason for the rejection: water and energy usage in a region that already cannot support its existing population's water demand.
The vote was clear. The city told the developer no. The city told the developer in writing that it would not provide water to the project. The mayor blocked an annexation that would have routed the site through city services. The developer pulled out of city negotiations. The Pima County Board of Supervisors then approved a land deal that let the project move forward outside the city's jurisdiction.
This is the jurisdictional architecture I have been mapping in the series. The city says no. The county says yes. The developer routes around the city's refusal by working through the county. The result is the same kind of bilevel sovereign loophole the Northern Cheyenne case turned on, just at a smaller scale and a different jurisdictional layer.
What happened next is the receipt.
On April 24, 2026, the developer's contractor — a firm called Ames Construction — obtained a construction water meter from Tucson Water. The application did not specify Project Blue as the destination. The contractor took the meter and used it to draw water from inside the city's service area. The contractor then transported that water out of the city's service area to the Project Blue construction site, in Pima County, where the city had explicitly refused to provide water.
A resident asked a Ward 4 staff member where the dust-control water for Project Blue was coming from. The Ward 4 staffer relayed the question to the city. The city investigated. The city found Ames Construction's construction meter and confirmed the routing. On May 4, 2026, City Manager Timothy Thomure sent a letter to Brendon Gallagher, senior vice president of Beale Infrastructure, revoking the meter. The letter said the city was amazed that Beale had taken city water for a project the city council had unanimously refused.
The volume taken: 2 acre-feet. Approximately 651,700 gallons.
Thomure also demanded that Beale replace the 2 acre-feet with water credits at no charge to the city. As of mid-May 2026 Beale had not responded to that demand.
Beale's response to the news cycle was a written statement: The city issued a permit for temporary water per the normal course of business. Our contractor followed standard procedure and will be billed accordingly. We are procuring construction water from an alternative source for non-potable use.
Read that statement carefully. The developer says the city issued the permit, the contractor followed standard procedure, and the bill will be paid. None of that is a denial that the water was transported out of the city's service area against the explicit refusal of the city council. It is an assertion that the mechanism was procedurally clean. The mechanism is exactly the architecture.
A week later — May 8, 2026 — Pima County's Department of Environmental Quality cited Ames Construction for violating its fugitive dust permit during construction inspections at the Project Blue site. The county threatened $10,000 daily fines. The dust that Ames Construction had been trying to control with the stolen city water was a regulatory violation in its own right.
The pattern: the developer cannot legally control dust at the site without water. The city has refused water. The county that approved the project does not have its own water supply to give. The developer takes the city's water anyway through a construction-meter loophole. The contractor gets caught. The city revokes the meter. The county then cites the contractor for the uncontrolled dust the contractor caused by not having water. None of the structural problems are resolved by any of this. The project continues. The county still wants it. The developer is procuring water from an alternative source for non-potable use — which in southern Arizona means trucked groundwater from somewhere outside Tucson's service area, drawn from an aquifer that someone else's community depends on.
Beale Infrastructure has been here before. The company has been in active disputes with the town of Marana over a separate data center. It withdrew from a Kansas project after a city refused incentives. It is currently fighting community opposition and lawsuits in multiple jurisdictions where it has tried to build. The Tucson dispute is not a misstep by a competent operator. It is the operating model of a company that builds where local communities have already said no.
The Numbers Behind the Two Cases
The Georgia case is 29 million gallons in a single suburban county. The Arizona case is 651,700 gallons over a few days at a single contractor's hands. Both are small in absolute terms relative to the national figure. Both matter because they are the visible part of an iceberg that no one is sizing publicly.
U.S. data centers directly consumed 17.4 billion gallons of water in 2023, according to the EPA. The same agency projects consumption to reach 38 to 73 billion gallons by 2028. That is a tripling to a quadrupling in five years. In Texas alone, the Houston Advanced Research Center estimated data centers would consume 49 billion gallons in 2025 and as much as 399 billion gallons by 2030. The 399 billion gallon figure is equivalent to drawing down Lake Mead — the largest reservoir in the country — by more than 16 feet in a single year. Texas reservoirs and groundwater are already drying up statewide. Corpus Christi is preparing to declare a water emergency with 25 percent usage cuts.
Google's data centers in The Dalles, Oregon — a city of 16,000 people — consumed 355 million gallons in 2021. That was roughly a quarter of the city's total water supply that year. When the local newspaper tried to obtain the water-use figures through a public-records request, Google funded the city's lawsuit against the newspaper, arguing the data was a trade secret. A Meta data center in Newton County, Georgia, disrupted nearby private wells. Families had to haul water in. Their appliances clogged with sediment. In South Carolina, conservation groups fought Google's permit to draw 1.5 million gallons per day from a regional aquifer.
The Ceres analysis is the second-order finding worth holding. Most of data centers' water consumption is not direct. It does not happen in the facility itself. It happens at the natural gas and nuclear power plants that produce the electricity the data centers consume. Water is consumed at the plant for cooling. Ceres estimates Arizona's power-plant water usage could quadruple to as much as 14.5 billion gallons per year to serve data center demand. That is enough water to supply at least 50,000 homes. The power plants are usually in rural areas. They usually draw from groundwater aquifers.
The closed-loop pitch is true at the boundary of the data center and false at the boundary of the watershed.
This is the structural punch. The data center developer can technically tell the truth about its own cooling loop. The data center's internal water use can be modest. The lake disappears under the power plant 40 miles upstream that is generating the electricity the data center consumes. The architecture's water consumption is mostly upstream of the building anyone is looking at.
Bring this back to the Manhattan Architecture series. The Small Modular Reactor proposed at Northern Cheyenne would consume water for cooling. The Natrium reactors TerraPower is building near Cheyenne, Wyoming would consume water for cooling. The legacy gas turbines being installed at Portsmouth, Ohio with SoftBank and the Department of Energy would consume water. Every reactor on the DOE 16-site list at Oak Ridge, Savannah River, Idaho National Laboratory, and Paducah would consume water. The fuel cycle this series mapped is also a water cycle. The receipts in Georgia and Arizona are showing us what that cycle looks like when it is small. The cycle is not going to stay small.
What This Tells Us
Three findings from the two cases, in plain language.
One. Communities Only Learn by Accident.
A homeowner with low water pressure. A Ward 4 staff member fielding a single question from a single resident. An attorney with a public-records form. The architecture's opacity is its operational feature. It depends on no one looking. The moment anyone looks, the story holds for one news cycle and then disappears. The water keeps flowing.
Two. The Regulators and the Regulated Are Not Adversaries. They Are Partners.
Fayette County's water director said it explicitly: They're our largest customer, and we have to be partners. It's called customer service. This is the same posture I named in Part III when NorthWestern Energy's CEO said his own customer was probably a federal contractor. The utility is not the public's check on the developer. The utility is the developer's intermediary with the public. The regulatory framework that was supposed to put friction between corporate water taking and community water rights has been re-engineered, at the local level, into a customer-service function.
Three. The Fight Is Structural, Not Local.
Beale Infrastructure has multiple parallel disputes. QTS is one of dozens of hyperscale developers operating across the country. The 50 cities with moratoriums are organizing because the existing build has already overwhelmed their permitting capacity. The water-theft cases I walked you through are not aberrations. They are the operational baseline of an industry building at a pace local governments cannot meaningfully supervise.
What Comes Next
I told you Monday this would happen. The architecture mapped in the Manhattan Architecture series is not theoretical. It is operating now in real communities, with real water meters, in real states. Georgia and Arizona this week. Other states next week.
The next continuation pieces in this investigation will follow these threads as the reporting clarifies. The foreign-capital question — what is Abu Dhabi's sovereign wealth doing inside U.S. AI infrastructure through MGX in the Stargate joint venture, and has CFIUS reviewed it. The money map — how Inflation Reduction Act tax credits, federal contracts, state tax abatements, and sovereign wealth equity flow through the same fuel cycle. The resistance — Red Lake Nation's closed-reservation jurisdictional shield, Apache Stronghold's continued fight at Oak Flat, the Muscogee and Seminole and Maine moratoriums, the Northern Cheyenne building their own solar and bringing back their buffalo while the federal government tries to build a reactor a few miles up the road.
The pace of the publishing event will track the pace of the news cycle. The receipts keep arriving. I will keep writing.
Watch the water.