A Well-Informed
Community Makes a
Better-Informed Response.

Memo 019 made the case for brackish water as a real, undeveloped resource for this region — including its potential to supply the large industrial water users, like data centers, that are increasingly interested in exactly the kind of groundwater New Mexico has never fully mapped. That connection is real, and one of Project Jupiter's own local boosters has already said so publicly. But the resource case and the trust case are two different arguments, and this memo is about the second one: what happens to a community, and to a project, when transparency comes first — and what happens when it doesn't.

Doña Ana County offers a live example of what happens when that trust erodes. Project Jupiter — the data center campus under construction in Santa Teresa — was disclosed to the public in August 2025 and broke ground the following month, under funding ordinances the county approved before the project's own commitments were finalized.[1] A promised community town hall was quietly swapped for a developer-hosted job fair, and residents who showed up to demand answers instead packed a commission meeting that a commissioner had to repeatedly threaten to clear.[1] A local nonprofit and two residents have since sued the county over how the approval process was run.[3] The developers have missed their own job-reporting deadlines. And on July 21, 2026 — the day before Memo 019 was drafted — the county's own manager had his contract terminated, without cause, by unanimous vote, after not quite two years in the job.[4]

None of that is a reason to avoid brackish water — if anything, it's the opposite. One of the project's own local boosters has already said the quiet part out loud: Santa Teresa is "sitting on an ocean of brackish water that can be a generational source of water for decades to come," and that the data center could eventually draw from it.[2] The resource case for pairing brackish water with large industrial water users is real and already being made, by supporters of exactly this kind of project. What Project Jupiter shows is the cost of skipping the community first — the transparency, the honest accounting of water use, the town hall that actually happens instead of getting swapped for a career fair. A community that feels blindsided doesn't just fight the project in front of it. It makes every future project, and every future employer or resident sizing up whether to move here, factor in the risk that this could happen to them too. That is a cost no spreadsheet captures, and it is entirely avoidable.

Water access is only half of what a data center brings, and Ohio shows what the other half looks like when it goes wrong. Ohio hosts more data centers than any other Great Lakes state, and in October 2025, its EPA proposed a single statewide permit letting eligible facilities discharge cooling-tower wastewater — carrying biocides, anti-scaling chemicals, and potentially PFAS "forever chemicals," plus heat itself as a pollutant — into rivers and Lake Erie with far less individual review than before.[5] The agency's own justification, stated in writing, was that a "lowering of water quality... is necessary to accommodate important social and economic development" — a real, existing legal exemption, invoked to clear an administrative bottleneck created by genuine industry growth, not an invented loophole.[6] More than 7,000 public comments came in against it.[7] On July 21, 2026 — the same day Doña Ana County's manager was let go — Ohio's EPA abandoned the proposal entirely, saying case-by-case review "is the most appropriate path forward."[7]

Water quality wasn't the only thing Ohio residents organized around. Neighbors of existing data centers describe a constant low-frequency hum from cooling systems and backup generators running day and night — disrupting sleep, and, per health researchers, contributing to measurable stress over time in ways most local noise ordinances were never written to address.[8] Add continuous security lighting, farmland converted to server floors, and a tax-abatement pattern one township trustee summed up plainly: residents cover the cost of the police and fire service a data center relies on, while the facility itself pays no property tax for years under the incentive package that brought it there.[9] Jerome Township passed a development moratorium in response. More than 60 residents testified against data centers at a single Ohio Statehouse committee hearing in June 2026.[10] Nationally, opposition to a data center being built nearby jumped from 42 percent of Americans in September 2025 to over 70 percent by June 2026.[11] That's not a fringe reaction. It's a fast-moving shift in how ordinary people are responding to this entire industry — and neither New Mexico nor Sierra County is exempt from it just because Project Jupiter sits in a different county from either of us.

El Paso offers the contrast worth sitting next to Ohio's warning. Its desalination plant has disposed of brine through deep-well injection for nearly two decades — standard, proven, but still just burying the problem underground. In the last two weeks, El Paso Water approved a new project recovering roughly 2.8 million gallons of drinking water a day, and sellable minerals, from what used to be pure waste.[12] That's the same circular-economy logic Memo 019 argues for brackish groundwater generally, now proven at the exact plant that memo treats as its reference case — and it points at something structural, not just aspirational, about doing this in New Mexico rather than Ohio: a brackish plant paired with deep injection and mineral recovery has nowhere to discharge cooling wastewater into a river or lake, because there isn't a Lake Erie sitting next to it. New Mexico's scarcity is also what would force closed-loop design from day one here, not better intentions.

A well-informed community makes a better-informed response, in both directions. Ohio's residents weren't wrong to organize, and they weren't uninformed either — they showed up with the specifics: what chemicals, what noise levels, whose taxes, whose water. That's the version of public pushback that actually changes an outcome. It isn't generic anger at a project; it's a room full of people who did the work to know exactly what they were objecting to, which is precisely what let 7,000 individual comments add up to a reversed decision instead of getting waved through as noise.

Project Jupiter didn't get that chance, on either side. The developer never gave residents the town hall that would have let them ask specific questions before ground broke. The county never gave itself the political cover a genuinely informed public hearing would have provided. Nobody in that sequence — not the developer, not the county, not the residents — ended up better off than they would have been with more information earlier. That's the real cost of skipping the community first: not that the project necessarily should have been stopped, but that nobody involved ever found out whether it should have been, because the process that would have answered that question never happened.

The Authentic Method asks one question underneath everything else: who does this project really serve first — the people it says it serves, or an interest it isn't naming? TAM answers that through four pillars, each asking a different angle of the same thing. What follows is how a resident, not an institution, actually uses them — walked through with a generic, hypothetical project rather than any real one, so the method stays a tool you apply yourself rather than a verdict handed to you.

Pillar One asks who really benefits. Picture any large project proposing to bring jobs, tax revenue, or new infrastructure to a county. The question isn't whether it says good things will happen — it's whether the stated benefit is specific and checkable. "This will create jobs" is a claim. "This will create 400 permanent jobs at these wage tiers, reported to this agency on this schedule" is a claim you can actually verify a year later. If a project's public promises get vaguer the closer you look, or if the same people funding the project are the ones who'd personally profit from an approval regardless of community benefit, that's the pillar flagging something — not proof of bad faith, but a reason to ask a sharper follow-up question before you decide.

Pillar Two asks whether the claims hold up under scrutiny. Does the project's own account of itself match what independent sources — local news, other agencies, people not employed by the project — actually report? A project that answers hard questions directly is behaving differently than one that responds only with prepared statements, or that quietly cancels the meeting where those questions would have been asked and replaces it with something friendlier. This is the pillar Ohio's residents were using without naming it: they didn't just object, they came with specific chemical names and specific noise complaints, and checked whether the permit's own language matched what was actually being proposed.

Pillar Three asks how the project or the people behind it behave when nobody's forcing them to explain themselves. A track record matters more than a pitch. Has this developer, in other places, done what they said they'd do on the timeline they said they'd do it? Have they met reporting deadlines when nobody was watching, or only when required to under legal threat? A single project is a promise. A pattern across several is evidence.

Pillar Four asks whether the project can admit it might be wrong about something. Every real project has tradeoffs — water use, noise, traffic, land. A project that acknowledges its actual tradeoffs and explains how it's addressing them is behaving differently than one that describes itself in only positive terms and treats every question as hostile. Defensiveness in the face of a reasonable question is itself information.

None of these four questions produces a score by itself, and that's deliberate. The value isn't a number — it's that a resident who's walked through all four has a specific, defensible account of what they know and don't know, instead of a feeling. That's the difference this memo keeps returning to: Ohio's 7,000 comments moved a decision because they were specific. A crowd that's simply angry, however justified the anger, is easier to dismiss than a crowd that's specific — and TAM's real value is helping a community get from one to the other, on any project, regardless of which answer it ends up pointing toward.

Memo 019 makes the resource case for brackish water in detail — what it is, what it costs, and why it's worth developing deliberately. This memo is the other half of that argument: any large water-intensive project built on that resource, data center or otherwise, earns its community's trust the same way it earns its water right — by asking first, not by explaining after the fact.