Readiness Over Hype: Why We Publish Constraint Analysis

Wisconsin is being talked about as a destination for AI-scale data centers. The announcements are large, the renderings are glossy, and the timelines are optimistic. Our work starts one step earlier — with a plainer question:

Can the infrastructure actually support it?

Readiness is a systems problem

Whether a region can host AI-scale compute is decided by the interaction of several physical constraints, not by any single headline number:

• Power capacity — firm generation and resource-adequacy margin.
• Grid deliverability — whether that power can physically reach the site.
• Cooling and water — thermal loads at AI density, and sustainable supply.
• Land, zoning, and community — parcel fit and the social license to operate.
• Workforce and schedule — skilled trades and multi-year equipment lead times.
• Regulatory and planning — MISO and PSC rules, and who pays for new build.

A project can clear five of these and still stall on the sixth. The bottleneck is what matters.

What this blog is for

This is where we’ll publish shorter-form analysis between editions of the Readiness Brief: notes on specific constraints, context on announcements, and the occasional myth we think is worth correcting — always engineering-first, and always non-promotional.

We are not selling a site, a ranking, or a narrative. We assess feasibility.

If that’s useful to the work you do, get the Readiness Brief and follow along here.