brain/
sourcestock-market

Autoresearch: Does a state-level data-center siting gate destroy load or merely relocate it to another ISO?

Texas paused ALL new data-center grid interconnections on 2026-08-03 (474 GW queue, ~90% data centers), 20 days after New York's EO 62 — so the two largest destination markets gated near-simultaneously and the 'load just relocates to another ISO' premise fails. Both gates carve out an explicit exemption for purely behind-the-meter on-site generation, which makes off-grid the escape valve rather than another ISO.

Source

Autoresearch: Does a state-level data-center siting gate destroy load or merely relocate it to another ISO?

Generated by /autoresearch on 2026-08-10 (sequential route). Synthesized across 2 rounds from 6 web pages. No Grokipedia anchor attempted — fast-moving contemporary policy topic, outside encyclopedic coverage. Treat as raw material — review before promoting. Context: vault/projects/stock-market

Summary

The question was framed as a binary — does a siting pause destroy data-center load or relocate it to PJM/ERCOT/MISO? The research says neither, and the framing itself is now stale. On 2026-08-03, twenty days after New York's EO 62, Texas Governor Greg Abbott directed the PUCT and ERCOT to audit every data center in the interconnection queue and halted approvals pending the result (Texas Tribune). ERCOT's queue holds 474 GW across 1,800+ projects, ~90% of it data centers — more than five times Texas's record peak demand (Utility Dive). The largest receiving market gated itself before the redirect could arrive.

The load's actual escape valve is written into both gates: purely behind-the-meter on-site generation is exempt. New York's EO 62 pauses discretionary DEC environmental permits, not local ones; Texas's directive governs ERCOT interconnection, so "projects utilizing purely 'behind the meter' on-site generation and not interconnecting through ERCOT may not be subject to this directive" (Foley & Lardner / National Law Review). The rotation implied is not geographic — it is from grid-interconnected to off-grid.

Findings

Two gates, twenty days apart, on the two markets that matter

New York, 2026-07-14. Governor Hochul's Executive Order 62 imposes a one-year moratorium on discretionary environmental permits for data centers of 50 MW or more, making New York the first state with a statewide data-center permitting moratorium (Hodgson Russ; Governor's office, EO 62). The DEC pauses review of incomplete permit applications. Carve-outs matter: permits deemed complete before 2026-07-14 are exempt, the order does not reach local-government permits, and data centers primarily serving manufacturing, research, education, or medical care are excluded (Harter Secrest & Emery).

Texas, 2026-08-03. Abbott ordered PUCT + ERCOT to run a "comprehensive verification and audit" of all data centers seeking grid connection, with approvals halted until it completes. Abbott: "Any data center project that fails to comply with the verification and audit process to protect the reliability and resilience of the Texas electric grid must be denied" (Utility Dive). The audit must verify tax incentives received, power use and self-generation, water consumption and cooling, community-impact mitigation, and facility ownership (Texas Tribune). ERCOT told Fox News the directive "effectively pauses all data center projects."

Critically, the audit timeline is unspecified in both the directive and the reporting — the end-condition is unbounded, the same defect this wiki already flagged in EO 62.

The mechanical consequence is already visible in ERCOT's own planning

ERCOT paused its "batch zero" transmission planning study and will request a good-cause exemption to regulatory timelines at its 2026-08-20 meeting (Utility Dive). That is a hard, dated, near-term catalyst — and it is a transmission-planning deferral, i.e. it hits the engineering-and-construction leg directly rather than the generation leg.

Scale for context: Texas Tribune counts 335 operating data centers and 248 planned projects in the state (Texas Tribune).

The receiving ISOs cannot absorb a redirect anyway

  • ERCOT's large-load queue nearly quadrupled in a year — from 63 GW at end-2024 to ~226 GW, with ~77% from large data centers targeting 2030 connection (Latitude Media).
  • PJM faces a capacity shortfall that could reach 15 GW by 2030, with a projected 6.6 GW deficit for 2027–2028 (Ascend Analytics).
  • MISO is designing a dedicated, expedited large-load process outside its regular interconnection queue as its fast lane winds down (RTO Insider).

So the "relocate to PJM/ERCOT/MISO" leg fails on two independent grounds: the destination gated itself, and the destinations that didn't are already capacity-short.

The exemption is the trade: off-grid, not out-of-state

Both gates leave the same door open. Texas: projects on purely behind-the-meter on-site generation that do not interconnect through ERCOT may fall outside the directive; additionally, roughly 50 Texas counties sit outside the ERCOT region — El Paso, parts of the Panhandle, Far East Texas — and are not subject to it (Foley & Lardner). New York: the order reaches discretionary state environmental permits, not local approvals, and not projects whose permits were already complete.

The reporting is explicit that developers are already using this: "some data centers are building on-site power generation that allows them to bypass traditional connection to the grid" (KERA News).

The statewide-moratorium wave is mostly failing; the county wave is not

This is the counter-weight, and it matters for sizing the forcing function. As of June 2026, 14 states are considering or have implemented restrictions, with moratorium bills introduced in 11 states — but most failed to advance: Virginia, Georgia HB 1059, South Dakota SB 232, Wisconsin SB 1061. Ohio's proposed constitutional amendment to ban data centers over 25 MW failed to qualify for the 2026 ballot, gathering only ~70,000 of the 413,488 signatures required by the 1 July deadline (Good Jobs First; Stateside Associates).

The action has instead moved local. In Indiana alone, Indiana University's Environmental Resilience Institute counts 11 counties with data-center ordinances, at least 17 with temporary moratoriums, and 2 (Marshall and Cass) with outright bans (WFYI). County-level gates are more numerous, less legible, and harder to route around than a single statewide order — and notably, NY EO 62 explicitly does not pre-empt local permits.

Tradeable implication

The chain that survives this research is: siting/interconnection gate → grid-connected greenfield deferred (unbounded end-condition) → load served either from existing generation or from behind-the-meter on-site generation → value rotates away from grid-interconnection-dependent EPC/transmission and toward (a) incumbent existing generation and (b) BTM generation equipment.

  • Deferred: grid-interconnected greenfield build — the EPC/transmission complex (PWR, and the transmission-planning work ERCOT just paused).
  • Advantaged (a), existing generation: CEG, and merchant/nuclear incumbents that can serve load without new interconnection.
  • Advantaged (b), behind-the-meter equipment: on-site generation vendors — fuel cells (BE), turbines (GEV), gensets (CAT, CMI) — because the exemption is written into the gate.

⚠ Held honest: this synthesis establishes the policy mechanism and the exemption, not the magnitude of the shift. No source here quantifies how much load has actually moved to BTM, and no source names a specific project cancelled or re-sited. The (b) leg also sits in tension with live performance — CAT is currently −8.1% sector-excess in this project's own ledger — so the argument is a forward mechanism, not a confirmation of the current tape.

Contradictions and open questions

  • No source names a single project cancelled or relocated. Every source describes the gate; none reports the response at project level. This is the load-bearing gap — the mechanism is confirmed, the transmission is not.
  • The audit end-condition is unbounded in both states. NY EO 62 is nominally one year; the Texas audit has no stated timeline. "Paused" could mean weeks or years, and that difference decides whether this is a deferral or a de-rate.
  • Does the BTM exemption survive contact with the audit? Abbott's audit explicitly examines "whether data centers provide their own power or depend on ERCOT" — which could mean BTM projects are favored, or that BTM claims will be scrutinized and narrowed. The directive text supports the first reading; the audit's inclusion of self-generation as a verification item leaves the second open.
  • Does the county-level wave matter more than the state-level one? State bills are mostly failing while county ordinances proliferate. A county patchwork may be the more durable constraint — and it is far less visible to anyone modelling this from state legislation.
  • Is CAT's current lag evidence against the BTM leg, or evidence of the timing gap? The mechanism argues CAT should benefit; the tape says CAT lags its sector. Unresolved.

Provenance

Rounds run: 2 of 3 (early exit — round 2 resolved the central question decisively; a third round would not have changed the synthesis).

Sub-questions by round:

Round 1 (broad survey):

  1. What is the status of New York EO 62 and comparable state data-center moratoria as of August 2026?
  2. Is there evidence of data-center projects being cancelled outright versus re-sited to another ISO since June 2026?
  3. Are PJM / ERCOT / MISO interconnection queues showing inbound migration from restricted regions?

Round 2 (drill-down):

  1. What exactly does the Texas 2026-08-03 directive do, what is exempt, and on what timeline? — targeted the round-1 discovery that the presumed receiving market had itself gated.
  2. Are developers responding by moving to behind-the-meter on-site generation? — targeted the exemption surfaced in round 2's primary sources.
  3. How broad is the state-level moratorium wave, and is it succeeding? — targeted sizing the forcing function against the failure rate of these bills.

Anchor source: none — no Grokipedia anchor attempted (fast-moving contemporary policy, outside encyclopedic coverage).

URLs fetched (2 full fetches + 4 search-result syntheses; 0 failed):

Round 1:

Round 2:

Tools used: WebSearch, WebFetch. Generated: 2026-08-10 (headless daily run)

Referenced by