Local litigation

Why it matters

Three near-simultaneous suits (IL, MN, OH) targeting hyperscaler-tied data centers in the same week is a meaningful escalation of the local-opposition mechanism beyond the moratorium-vote channel covered yesterday. Worth tracking in byog-byong-state-patchwork.md as a separate 'litigation-pause' category distinct from 'moratorium-pause' — the procedural surface is different (zoning-defect lawsuits seek to invalidate already-issued approvals; moratoriums freeze new applications), and the resolution path is different (settlement, injunction, or appeal — typically 6–18 months versus the 90-day-rolling moratorium pattern). The Hermantown vote today is also a same-day pivot point: city council can vote up the Google development agreement before the lawsuit is heard, but the suit then becomes a post-approval challenge similar to PW Digital Gateway. This is the chain that Compass just walked away from — and it's now duplicating in the rust-belt corridor (OH) and the Upper Midwest (MN, IL). For Cliff's submission validator product, the implication is that 'submission-ready' must include an injunction-resilience module: did the public-notice path comply with state-specific procedural minimums that survive judicial review? PW Digital Gateway invalidation came from procedural defects in the 27-hour hearing, not substantive zoning grounds — and the Hermantown / Yorkville complaints are reading similarly. Open a new strategy/data-center-litigation-tracker.md page to track these systematically; will compound into a litigation-outcomes corpus alongside the approval-outcomes corpus already mapped in competitive-landscape-and-adjacencies.md.