May 20.

Why it matters

For Cliff's site-readiness map this changes the base rate, not just the data points. If you assumed moratorium risk clustered in a few regions, a site in a 'safe' state looked clean. The correct read now: any U.S. jurisdiction can pass a pause on roughly 30 days notice once a developer's interest becomes public, regardless of region or politics. That argues for two product features. (1) A 'moratorium velocity' field per jurisdiction — not just 'is there a moratorium today' but 'how fast could one appear,' driven by whether neighbors recently passed one (Logan County → Bloomington/Normal is a clear contagion chain in one Illinois media market). (2) A layered-moratorium flag: Reno proves a single pause is no longer the worst case — a council can stack a use-permit pause and a construction-permit pause to close loopholes, so 'we already have our use permit' is not a safe-harbor assumption. The Inver Grove Heights case also names the developer (Fortress Investment Group) and a specific parcel (the former Travel Tags site), which is the kind of structured fact — developer + parcel + vote margin + duration — the approval-outcomes corpus should capture for every one of these.

Why it matters

A 4-1 first reading almost always becomes a passed ordinance on second reading, so treat tonight's vote as a near-certain yes and the real question as 'what's the template?' The Cave City template — developer interest becomes public, councilmember files ordinance, ~30 days to an enforceable 12-month pause — is being exported across rural jurisdictions by anti-data-center advocacy networks. For Cliff this is the strongest argument yet for tracking the gap between 'developer interest disclosed' and 'moratorium enacted' as a metric: in Kentucky it's now trending under 30 days. It also reinforces why developers use shell-company land options to stay anonymous through early diligence — but small-town councils are increasingly able to unmask the real buyer from public records, which collapses that protection. A site-readiness product that flags 'this jurisdiction has an active anti-DC advocacy presence and no state preemption law' would have predicted Cave City weeks early.

Why it matters

This is the live wedge the whole Texas thesis depends on, and the timeline is now hard rather than estimated. Cliff's operational window is roughly today through July 24 — about nine weeks. The committee votes clearing (PRS, ROS, TAC) means the rules are essentially final ahead of the June 1 board rubber-stamp, so the product can be built against settled text now rather than waiting. Three concrete to-dos: (1) confirm the May 19-20 TAC vote actually landed and note any last-minute amendments — a single TAC tweak to the financial-security or firm-load definitions changes the underwriting math. (2) The July 24 Declaration of Intent (Form W Part A) is the single highest-value structured document in the Texas pipeline — every developer claiming a Batch Zero slot files one, each carrying their per-study-year minimum firm-load limit, which is exactly the queryable, primary-source data the live-docket wedge is meant to ingest. (3) Pair this with the parallel PUCT financial-security rule (16 TAC §25.194, $50,000/MW non-refundable fee) so a developer sees both the ERCOT timing gate and the PUCT cost gate in one underwriting view.

Why it matters

This is the federal bookend to the local moratorium story above: localities are pausing, while the federal executive is trying to accelerate — and they will collide on real sites. For Cliff, the end-of-June FERC framework is a second top-tier federal docket to track alongside the PJM co-location proceeding (EL25-49), and it is broader because it potentially touches every RTO, not just PJM. The jurisdictional angle is the part to model: if FERC asserts authority over large-load interconnection terms, a project's connection rules get standardized federally; if states retain it, the rules stay a 50-jurisdiction patchwork that is exactly the complexity Cliff's knowledge graph is built to navigate. Either outcome increases the value of a single product that maps 'who has authority over this specific connection.' Add the DOE/FERC large-load proceeding to the live-docket watchlist with a hard date checkpoint at end of June.