One city vote did not settle Project Blue; the land and electric agreements followed separate tracks.
Original publication: Date not retained · Last substantive update: September 21, 2026
What changed: The September 21 source review adds the county’s phase and site description and its stated disclosure limit. These are plans and disclosure context, not a measured operating campus.
Project Tango’s expansion request was denied and then challenged. The land-use record is real; a built campus or public subsidy is not established here.
Brightseat names an applicant and a proposed technology park, then runs into a county pause that leaves the operator, workload, and public cost unsettled.
Project Jupiter separates county approval, reported financing scale, the permit fight, and a changing power plan instead of treating them as one number.
The campus is under construction, but private entities, confidentiality agreements, utility negotiations, and tax policy obscure what was visible before commitments hardened.
Quantica’s paper trail offers a tax-impact projection, a reported labor agreement, and a large power plan without showing what the public approved or will pay.
Project Lincoln changed sites and scale faster than the public record could explain the bargain, leaving infrastructure cost and consumption questions open.
Seafox has published agreements, water-allocation ceilings, and a proposed power bridge; the remaining work is separating commitments from projections.
The Data Center Trade: does Jupiter's power problem stay in New Mexico?
This standing investigation is withheld from the public site while its hypotheses and fact labels are reviewed. Its stored record and sources are kept unchanged.
Featured case · Project Blue, Arizona
Tucson said no. The land deal closed anyway.
Tucson ended negotiations over bringing Project Blue into the city. Months later, Pima County recorded a completed land sale. The two decisions belonged to different governments.
One city vote did not settle the project. The land deal and electricity agreement were handled elsewhere. That is the question worth following: who has the authority, who gets paid, and how much of the deal can the public actually see?
The city decision
Arizona Luminaria reported that Tucson’s council voted on August 6, 2025 to end negotiations and remove the annexation and development agreement from its agenda. Its reporting described public anger over transparency and debate about nondisclosure agreements. Beale Infrastructure said it was disappointed and would share future plans.
The county transaction
Pima County’s April 2026 update, pages 1–2, says its board approved zoning and a land agreement in June 2025. The sale closed on December 24. The site is in unincorporated Pima County. Tucson’s decision and the county’s transaction concern separate approvals.
The water workaround
AZPM reported that Arizona water officials approved two commercial wells tied to Project Blue under three existing groundwater rights totaling 96.5 acre-feet per year. The Department of Water Resources told AZPM that the company must report its water use annually; the article says each well was described as having 600 gallons-per-minute pumping capacity. That establishes a permitted supply path, not measured use, wastewater discharge, or proof of the developer's estimate of 15,000–20,000 gallons per day once fully operational.
The electricity agreement
TEP's own agreement summary says the deal caps service at up to 286 MW and includes minimum monthly bills, financial security, and a termination fee if the project does not meet its obligations. Those are contract protections described by the utility, not evidence that the campus is energized or that the safeguards have been tested in practice.
The Arizona Corporation Commission’s account records a 4–1 vote approving a special service agreement in December 2025. It says the agreement protects existing TEP customers through measures including termination fees and minimum payments. It also attributes to TEP a commitment that the data center would fund new generation needed beyond the initial 286 MW.
Those are the regulator’s stated protections. Testing their effect means following the agreement, construction costs and later bills.
The first payment trail
TEP's June 2026 Form 10-Q says FERC approval of an amended transmission-and-switchyard construction agreement triggered a $20 million advance payment from the customer. TEP says the agreement requires the customer to pre-fund project costs and that another $24 million is expected when remaining conditions are complete. That is a reported customer advance and an expected future payment—not public spending, a completed campus, or proof that minimum bills and termination protections have been tested.
The control question
Project Blue is a useful stress test for public oversight because the decisions arrived in pieces: Tucson ended negotiations, Pima County closed a land sale, and the state regulator approved utility terms. The records establish those separate actions. They do not establish a coordinated plan, name the future operator or customer, or disclose what the campus will actually run.
That is the sharper issue than whether one meeting looked secretive. When land, power and compute are split across different institutions, each decision can look narrow while the public bargain stays hard to see. That is an interpretation of the paper trail, not proof of hidden coordination.
Investigation & analysis · September 12, 2026
The Billionaire Building AI’s Rulebook
Dustin Moskovitz invested in Anthropic and helped finance the institutions shaping AI policy. Follow the money from private philanthropy to the people defining risk—and ask who gets to decide what the machines may say.