Developer-litigation counter-attack matures into three distinct postures — Imperial County CA files TRO + Inver Grove Heights MN passes 3-2 despite $150M threat + Hill County TX retrospective — California enters the moratorium map for the first time with a water-rights cross-pollination, Minnesota becomes the fourth state-level cluster, and implementation week clock ticks down to VA tax T+3, ERCOT Batch Zero T+12.

Why it matters

Three implications. (1) California is now on the moratorium map for the first time, and via a structurally distinct mechanism: not a county PREVENTING a project, but a county RESCINDING its own prior approval. That's a new pattern Cliff's corpus should add as a separate moratorium category — 'reversal moratoriums' carry different procedural fragility than 'pre-emptive moratoriums' because the developer has already accrued reliance damages on the original approval. The TRO mechanism (Hill County TX won in May, Imperial County CA filed last week) is now the standard developer counter-move. (2) The water-rights front is a Cliff-specific signal of where the corpus needs to expand. Every diligence framework Cliff has built so far is power-load/grid-cost-allocation focused; water-permit risk is a parallel diligence vector with its own state-by-state regulatory geography (Colorado River Compact states + Great Lakes Compact states + Floridan Aquifer states all have separate frameworks). The 'fallow farmland water reallocation' theory IVCM is testing is the AI-native version of an agriculture-to-industrial water-rights transfer, and if a court accepts it, every CA / AZ / NV / UT / NM / CO data center could template against it. Add 'water-rights senior-claim transfer' to the corpus schema. (3) The developer litigation now has three distinct postures (Imperial / IGH / Hill), each with different outcomes. That's data Cliff's diligence framework should productize as a probability-of-survival score for any moratorium target: posture × jurisdiction × procedural posture (pre-approval pause vs. post-approval reversal) → predicted resolution timeline. The corpus should be tagging every active moratorium with this metadata starting now.

Why it matters

Three implications. (1) The MISO concentration matters because MISO is one of the six RTOs FERC issued show-cause orders to on June 18 (30-day reliability + 60-day tariff). The Minnesota cluster, combined with the existing Wisconsin cluster, means MISO now has 5+ active moratoriums in jurisdictions whose state regulators will be cited in MISO's August 17 tariff filing. FERC's tariff design will have to make a substantive choice about whether to override local moratoriums via federal tariff preemption or accommodate them. That choice is the next major federalism question in the cost-allocation fight. (2) The Minneapolis size+geographic exemption is the template Cliff's corpus needs to flag as the 'preferred' exemption design for cities with mixed urban/suburban data center pipelines. The political logic is durable: it lets a council take the headline 'we paused data centers' without breaking the colocation/cloud-edge economic-development relationships that downtown business interests care about. Expect Boston, Seattle, Denver, Atlanta, Pittsburgh, and similar mid-tier cities to copy the format if they face moratorium pressure in 2027. (3) Inver Grove Heights is the first proof-point that the developer-litigation threat is NOT automatically winning. Hill County TX (May 27 / June 4) was a rescission. IGH (Jun 26) was a hold. Two different MN/TX procedural environments, two different outcomes. The probability that a $150M-letter threat reverses a moratorium is now somewhere between 0/1 and 1/2, not 1/1. That's a real data point for any developer drafting a similar letter in the next 30 days and a real data point for Cliff diligence on developer-side outcome probability.

Why it matters

Three implications. (1) The 90%-of-438k-MW data point is the clearest single quantification yet of the speculative-to-real ratio in any RTO large-load queue. Cliff's corpus should use this number as the baseline 'load queue speculative ratio' for cross-RTO comparison: when PJM, MISO, SPP, etc. file their August 17 FERC tariffs, the same number for each RTO will be the most important comparative metric Cliff can extract. The 'queue-to-system-peak ratio' becomes a corpus-level KPI. (2) For Cliff GTM in Texas: the August classification notices are the first time a Texas hyperscaler site's interconnection status will be public-and-structured. Every Cliff site-diligence package for a Texas project starting in September should pull the August classification — cleared / conditional / further-study — as the single most important interconnection variable. The corpus should have an automated PUCT-docket-tracker for Batch Zero filings starting July 10, since the filings will flow through PUCT IDs once forwarded by the ILLEs. (3) Virginia's $0.011/kWh tax going live in 3 days completes the implementation-week picture: a Texas site files Batch Zero on July 10 with PCLR commitment vs. a Virginia site is now paying the per-kWh tax starting July 1. The two states represent the cleanest comparative regulatory environment for hyperscaler decision-making, and the next 6 months will produce the first dataset of hyperscaler site-selection decisions made under the new dual regime. The corpus should be tracking announced TX vs VA campus decisions starting now.