Durham NC / unanimous

Why it matters

Three updates for byog-byong-state-patchwork.md NC section and a new entity page on Durham/Charlotte/Mecklenburg if the cluster keeps growing. (1) The 60-day-cap-then-extend-via-planning-commission mechanic is procedurally distinct from the typical 6-12 month council-issued moratorium. Cliff's de-rate calculator regulatory-risk module currently treats moratorium duration as the input — but the Durham mechanic shows that the underlying procedural pathway (council unilateral vs. council + planning commission joint) determines the practical ceiling, not the headline duration. NC HB 1004 (yesterday's lead, on-site generation mandate) layered on top of the Durham 60-day-then-12-month pattern means a single NC site can face: (a) the 60-day council moratorium (immediate freeze), (b) extension to 12 months via joint commission (medium-term freeze), (c) statutory on-site-generation mandate at 25% if HB 1004 passes (permanent design constraint). That's three discrete regulatory-risk inputs for the same site, each layered chronologically — far more than the single 'moratorium yes/no' input the calculator currently models. (2) Charlotte mayoral-veto contrast: a 6-5 mayor-deciding-vote against even holding a public hearing is a cleaner test of where local political leadership lands than a typical moratorium vote, because it isolates the mayor's view from the council majority. Mayor Lyles holds the line for now, but adding data centers to the May 11 agenda creates a subsequent decision point. If Charlotte's east-side application then clears May 18 council, Charlotte becomes the rare NC city refusing to moratorium even as Durham and Wake County pause — a real-time intra-state regulatory-arbitrage trade-off Cliff customers will need to model. (3) The compounding implication of Durham + Camdenton MO + Lonsdale MN + St. Charles MO + Sheboygan WI all moving in the same 48 hours is that the moratorium pattern is now spreading at roughly 1 city-per-day, well above the ~1 city-per-week pace observed in March. If that acceleration holds, by mid-June there will be 50+ active municipal data-center moratoria nationwide. The byog-byong-state-patchwork.md changelog cadence needs to drop from weekly to daily, and the de-rate-calculator-gtm.md should treat 'check moratorium-cluster status' as a built-in workflow step, not a one-off diligence task.