Ready to put this into action?
Get the complete AI Integration Playbook — Practical AI implementation guide — prompt engineering, workflow automation, and ROI frameworks.
What Is Actually Being Proposed?
Examine the Site Layer 1 notice, proposed gas engines, and missing details so Grant County can distinguish documented facts from unanswered questions.
Recommended Resource
AI Integration Playbook
Practical AI implementation guide — prompt engineering, workflow automation, and ROI frameworks.
Part 1 of 13
What Is Actually Being Proposed?
The proposed Site Layer 1 development would put a data center and a substantial natural-gas power plant in southern Grant County. Its notice describes 32 engines with about 300.8 megawatts of generating capacity and possible operation around the clock. That makes this a conversation about computing, energy, water, and the future of a particular place.
I’m still undecided. Good jobs, useful investment, and dependable public revenue deserve serious consideration. So do the consequences for water users, nearby residents, and the governments that would provide services. I want to understand the whole proposal well enough to judge what we would receive, what we would commit, and who would remain responsible.
The published notice supplied for this series gives us a starting point. The supplied notice excerpt is included with the series overview so readers can check its wording and figures directly.
The starting point
| Topic | What the notice says | What it leaves unanswered |
|---|---|---|
| Applicant | Site Layer 1, LLC; New York address | Complete ownership, financial backing, and eventual operator |
| Location | About 4.5 miles northeast of Playas and 11.8 miles west-northwest of Hachita | Surveyed boundaries, full development footprint, and utility routes |
| Power | 32 gas engines rated at about 9.4 megawatts each | Dependable output, computer demand, fuel contracts, and actual operating pattern |
| Water | No complete water budget or cooling design | Sources, annual and peak demand, and effects on other users |
| Timing | Expected air-permit application submission October 1, 2026 | Actual filing status, review schedule, and other approvals |
Those distinctions prevent several mistakes. A planned submission date is not an approval. An equipment rating is not a measurement of actual computer demand. An applicant’s business address is not a complete account of ownership. The notice describes an intended project; it does not establish that every business arrangement needed to deliver it has been completed.
The power proposal deserves particular attention. Generating capacity measures what equipment is rated to produce under specified conditions. Some electricity supports cooling and other equipment, and some generating capacity may be reserved for outages or maintenance. The community needs the design that connects those figures. A headline describing a “300-megawatt data center” can otherwise leave readers confusing the power plant’s capacity with the computers’ actual demand.
The notice also lists estimated maximum greenhouse-gas emissions of 1,292,118 tons per year of carbon-dioxide equivalent, along with other pollutants. These are proposed estimates, not measured emissions from an operating facility. The calculations, operating assumptions, and controls deserve scrutiny. Later articles explain why annual emissions, pollution at a nearby home, and climate effects are related but different questions.
Air permitting supplies one route for examining the proposal. The New Mexico Environment Department describes the applicable categories and reviews on its air-quality permitting page. Residents need the actual application number, current documents, and participation instructions. One permit should not be treated as a verdict on every financial, water, land, or community question associated with the development.
The water discussion shows why we need to separate a claim from a project commitment. In its September 2, 2026 announcement, the Gila Resources Information Project presented a possible annual demand of 6,535 acre-feet for a facility of this size using wet cooling. That is an opponent’s scenario based on a cooling assumption. It is not a water requirement stated in the notice or a verified description of this developer’s chosen design. GRIP’s announcement gives readers the organization’s position.
The company should supply the actual design and calculations. The public should then compare them with the scenario and test the reasons for any difference. An assurance of “very little water” needs the same scrutiny as a warning about very large consumption. Both should lead to quantities, sources, seasonal demand, and consequences for other users. Concern deserves a fair hearing; the strength of a claim depends on its evidence.
We also need to know the development’s intended full size. An initial phase may be only part of the business plan. Roads, pipelines, land arrangements, or customer negotiations could anticipate later expansion. The public needs that larger picture before evaluating commitments that would make it possible. This does not mean predicting every future server purchase. It means understanding the development the first phase is intended to support.
In the materials reviewed for this series, a complete ownership chain, committed project financing, a confirmed customer, binding local employment commitments, and a full account of public costs remain unverified. That is a description of the available evidence, not proof that the arrangements do not exist. Publishing an accurate status for each would let residents concentrate on the questions that actually remain open.
I want this conversation to leave room for people who value development and people who worry about water or rural life. Many of us hold both concerns. We can recognize a useful national industry while asking whether its local terms are acceptable. We can also recognize a risk without assuming the company cannot address it.
The standard I will use throughout the series is straightforward: distinguish what is documented, what someone is proposing or claiming, and what remains unanswered. Then ask what evidence would resolve the question and which decision depends on that answer. That approach gives a serious developer a fair opportunity to make its case and gives the community a way to evaluate it.
What a useful answer would include
The developer should provide a dated project description covering the initial phase, intended expansion, ownership, operator, customers, financing milestones, and infrastructure. Each responsible agency should identify the applications it holds and the next public decision. Unresolved items should have a named contact and an expected date for an answer.
Questions worth asking
- Will the developer publish one dated description of the initial project and intended expansion, with a record of changes?
- Which applications have been received, under what numbers, and where can residents read the current files?
- Who would finance, build, own, operate, and purchase services from the facility, and which roles remain unfilled?
- What water, employment, and infrastructure statements are written commitments, and which are projections or goals?
- Which missing answers are needed before each proposed public commitment or agency decision?
AI assisted most of the research and initial drafting under my direction. Sources are linked; corrections are welcome.
Get the AI Dispatch
Weekly insights on ai & technology — delivered to your inbox. No spam, unsubscribe any time.
Want to choose specific topics? Customize your interests
Get the AI Dispatch
Weekly insights on ai & technology — delivered to your inbox. No spam, unsubscribe any time.
Want to choose specific topics? Customize your interests