Charlotte's 11-0 moratorium and Spokane introducing its own after Avista quietly inked a 125-to-500 MW MOU plus Oregon's PGE rate hike sliding to July 7.

Why it matters

Charlotte is the first major banking metro to enact a moratorium. That breaks the 'finance-anchored cities will stay developer-friendly' assumption — Cliff's siting tool should now treat banking-hub metros (Phoenix, Dallas, Atlanta, Charlotte, Minneapolis) as moratorium-risk-eligible, not as safe zones. The 35-DCs-already-in-city baseline is also the new precedent for 'mature market that pulled the brake': Loudoun County and Phoenix should expect similar pressure when their council compositions shift.

Why it matters

Spokane is the inverse of Charlotte — moratorium triggered by a single MOU disclosure, not by accumulated frustration. That makes the access-disclosure sequence itself the political flashpoint. Avista chose stages (June 3 vague → June 9 specific → confidential location). Each step compounded resident reaction. Pre-development diligence playbooks need to model this: in mid-size utility service areas, every disclosure step is a moratorium-trigger event, and developers should price NDA carve-outs and joint announcement frameworks into the early-stage deal terms with the utility.

Why it matters

Birmingham metro is now the densest moratorium cluster in the country — three cities frozen in one quarter, two of them preemptive (no application filed). That's a real signal that 'preemptive' is becoming a contagion category in its own right, separate from reactive freezes triggered by an actual proposal. For Cliff's moratorium tracker, the Birmingham cluster should be the prototype for the 'metro-area cascade' field — once two cities in a metro freeze, the rest of the metro should be flagged as 90-day-likely candidates.

Why it matters

This is the operational template for 'small-utility-meets-hyperscaler' moments that will repeat across the country in 2026-2027: a customer too large for the host utility's planning assumptions, an MOU that triggers a regulatory review cycle, and a local moratorium that arrives before the contract is even binding. Cliff's underwriting product needs a 'utility MOU stage' explicit indicator — service areas where a single MOU represents >25% of system peak should flag automatically as 'high moratorium risk' for the next 12 months.

Why it matters

Practical product implication: Cliff's tariff exposure scoring can now use Oregon Schedule 96 as a fully operational reference data point for the contract-term axis (the dials are real today), but should leave the residential-vs-DC-class price gap as TBD until July 7. The 200-page tariff file delay also generalizes — every state PUC adopting Oregon-shaped tariffs will run into the same 'framework approved, math still being checked' pattern, and the gap between framework effective date and dollar-impact effective date is the period where developers can still negotiate harder. Tag that lag explicitly in the regulatory knowledge graph.

Why it matters

OPSB approval is the regulatory checkpoint that mattered. Two state checkpoints stand between an announced BTM project and steel in the ground: OPSB (or equivalent siting authority) plus the state air permit (Title V if PTE crosses 100 tpy NOx, which 200 MW gas does). Williams + Meta have now cleared both for Socrates South. Cliff's BTM underwriting product should add 'state-siting-board status' as a distinct field (Socrates South = approved, hundreds of others still pending), and use the Meta/Williams 10-yr template as the reference contract for sizing customer-funded BTM economics.

Why it matters

Three product-relevant updates from the substitute bill: (1) The brownfield bonus is the first state-level economic incentive for developers to choose a previously-contaminated site over greenfield — Cliff's siting tool should add 'brownfield-eligible' as a positive scoring dimension in Ohio specifically. (2) The own-generation bonus formally codifies the BTM-as-policy-preference move — once Ohio rewards BTM, other AEP-tariff states (likely PA next under the PUC's April 30 model tariff) will follow, and Cliff's BTM economics module needs to model the sales-tax delta as a real line item. (3) The NDA restriction is a regulatory backstop on exactly the Spokane/Avista disclosure pattern — Ohio wants developer terms public, which is the opposite of the Spokane MOU framework. Two state templates are now diverging on the disclosure axis (Ohio public-by-default, Washington private-by-default), and Cliff's underwriting needs to handle both.