NC / 5-county moratorium cluster + Charlotte test case + HB 1063

Why it matters

Three updates. (1) North Carolina is now structurally an effective state-level moratorium even though the General Assembly has not passed one. Five separate local moratoria covering Northampton, Durham, Harnett, Spring Hope (Nash County), and Orange County, plus the pending Charlotte test case, plus a state bill (HB 1063) that would impose statutory 25% on-site generation, mean a hyperscale developer evaluating an NC site faces near-certain entitlement delay regardless of specific county. The implication for Cliff's site-readiness underwriting: NC should be treated as a 'red' state through at least Q4 2026, with effective entitlement-feasibility limited to (a) already-permitted sites with grandfathered approvals, or (b) industrial-zoned sites in counties without active moratoria where the city has not separately moved. The competitive landscape page should add NC to the same risk tier as Maine (LD 307 history) and Virginia (Digital Gateway aftermath) for new hyperscale entitlement through 2026. (2) HB 1063 is the first state-level statutory 25% on-site clean-generation mandate in the US, and the threshold (40 MW peak load AND 1 billion liters/year water) is structurally different from the 50 MW threshold convergence covered above. The 'AND' conjunction is important — it only captures the largest, most water-intensive AI-training sites (cooling-tower-heavy designs hit 1 billion liters/year around the 100 MW mark; air-cooled or liquid-cooled-closed-loop designs at 40 MW may stay below). The 'OR' version would have caught most colocation, but the 'AND' version is targeted specifically at hyperscale AI training. The implication for Cliff: the bill is more sophisticated than typical ratepayer-protection legislation and points at a maturing legislative drafting community that distinguishes between hyperscale-AI and traditional colocation. If HB 1063 passes (which it probably will not in this session — Republican governor likely to veto if needed — but the architecture matters even if the vote fails), it becomes the template other states copy and refine. Cliff's regulatory-tracking should add a 'statutory on-site generation mandate' tag and treat HB 1063 as the primary reference text. (3) The Charlotte May 18 vote is the cleanest single-data-point test of whether a major NC metro can sustain a no-moratorium policy through public-opposition pressure. The political setup is hostile: Mayor Lyles tie-broke against public hearings on data centers 6-5 in late April, then put the discussion item on May 11's agenda after public pressure, then American Tower delayed the rezoning to May 18 (presumably for additional lobbying). A denial on May 18 would push Charlotte into the NC moratorium cluster and effectively close the largest NC metro to hyperscale entitlement for the foreseeable future; an approval over 4,200+ petition signatures and a hostile council would be the strongest signal in months that hyperscaler political capital can still override grassroots opposition in a major NC city. Either outcome is informative — track May 18 as the next-most-important date in the NC tape.