Michigan Data Centers Are Moving Faster Than The Public Ledger

Michigan does not need a lazy anti-compute panic. It needs a public ledger strong enough to let serious compute projects survive public scrutiny. The June 8 data-center file gives BadPD a clean Michigan tracker: Mason is weighing utility service for a township data-center site, state senators have introduced a temporary moratorium package, Governor Gretchen Whitmer is reported as opposing a blanket statewide pause while backing resource and ratepayer protections, OpenAI and its partners are making enforceability claims around Saline, and Allen Park planners just rejected a data-center site plan after repeated delays.

That is not one story. It is the state’s data-center accountability map becoming visible at the same time.

The BadPD frame stays consistent: build American compute, but do not hand out cheap public water, hidden grid subsidies, or local-control shortcuts. The question is not whether Michigan should compete in AI infrastructure. It should. The question is whether communities can see the contracts, utility commitments, water numbers, interconnection obligations, ratepayer protections, and enforcement mechanisms before public systems are committed.

Mason: Unknown Developer, Known Utility Ask

WILX reported June 3 that a data-center developer is asking Mason to provide city utilities to a site at 3388 W. Columbia Road in Vevay Township. Mason City Manager Deb Stuart said the company had not been publicly identified. WILX also reported that the developer was willing to commit to at least a $1 billion investment and that talks included a possible $7.6 million annual tax-revenue claim.

Those numbers are large enough to matter. They are also large enough to demand public detail.

The first Mason question is identity. A city cannot ask residents to evaluate a utility commitment without naming the customer, the corporate parent, the land-control structure, and the party responsible for nonpayment, delay, termination, environmental harm, or infrastructure overbuild.

The second question is scope. A utility request is not just a pipe or wire. It can mean water capacity, sewer capacity, road access, emergency-response burden, electricity coordination, stormwater, possible backup generation, and long-term operations assumptions. If the site is in a township but city utilities are the ask, the public needs to see who gets revenue, who carries risk, and who can enforce conditions.

The third question is timing. Data-center projects often move through early conversations before residents realize the practical commitment has already been shaped. Mason should publish the utility-service ask, staff memos, capacity studies, site maps, electric-load expectations, and any draft agreement before the decision becomes a done deal.

Lansing: SB1018 And The Moratorium Pressure

LegiScan shows Michigan SB1018 was introduced June 4 by Sens. Jim Runestad and Ruth Johnson and referred to Government Operations. The bill would block state and local authorizations for new data centers and block new data-center operations until April 1, 2027, if tied bills are enacted.

A moratorium is a blunt tool. But the existence of the bill tells us something important: state lawmakers are no longer treating data centers as isolated local land-use fights. They are treating them as utility, environmental, water, and ratepayer events.

The strongest BadPD position is not automatic support for every pause. A statewide moratorium can overcorrect if it shuts down good projects that are willing to bring power, use closed-loop or water-light cooling, publish impact data, and protect residents from cost shifting. But a moratorium debate can be useful if it forces the state to write standards before every city and township has to negotiate alone against billion-dollar counterparties.

The April 1, 2027 date matters. If Michigan uses a pause, it should not be a dead zone. It should be a standards sprint. The public should know exactly what the state is building during the pause: large-load tariffs, water-disclosure rules, emergency-curtailment standards, backup-generation reporting, tax-incentive transparency, construction labor requirements, community-benefit reporting, and enforceable exit fees.

Whitmer: No Blanket Pause, But Standards Still Need Teeth

Michigan Advance’s June 8 weekly data-center download reported that Whitmer told WZZM she would not sign a blanket data-center moratorium, while supporting standards around natural resources, grid impact, and resident costs. That is an important distinction.

If the governor’s position is build-it-right rather than stop-everything, then the next question is obvious: what exactly makes a project right enough?

A real standard would not be vibes. It would define minimum public disclosures and minimum enforceable terms. It would say when a data center must bring its own power, when it must support the grid, how much backup power is allowed, whether diesel generation is limited, whether battery storage or microgrids are required, how water use is measured, whether closed-loop claims must be independently modeled, and who pays if a project cancels after a utility builds infrastructure.

A real standard would also separate actual resident concerns from unsupported foreign-funding claims. Residents can oppose a project because of water, noise, rates, secrecy, land use, or trust without being part of a conspiracy. If someone claims China, a nonprofit, an industry rival, or a political donor is secretly funding opposition, BadPD needs money-flow records before treating that as fact.

Saline: The Barn Has The Promises Everyone Else Will Be Measured Against

OpenAI’s official June 1 post on Stargate Michigan says The Barn in Saline is a 1GW data-center campus. OpenAI says local residents will not bear infrastructure or energy costs, the facility will use closed-loop cooling, the project will create more than 2,500 union construction jobs and 450 permanent onsite jobs, and the company will support Michigan education and workforce programs.

Those are the promises data-center backers want the public to hear. They are exactly the promises that should be converted into enforceable public records.

The April 17 Michigan Attorney General release says Dana Nessel appealed MPSC approval of DTE’s Saline data-center contracts. That appeal matters because the public argument is not only about whether OpenAI and its partners sound responsible. It is about whether the contracts actually protect ratepayers, whether redactions block meaningful review, and whether future DTE rate cases can shift costs that today’s press releases say will not be shifted.

The Saline ledger should show average and peak water use, cooling-system design, commissioning water demand, sewer discharge, chemical use, emergency curtailment, battery or storage terms, interconnection cost assignments, collateral, termination penalties, quarterly reports, and complaint/enforcement channels. If The Barn is truly the model project, it should be the easiest project in Michigan to audit.

Allen Park: Local Control Still Exists

WXYZ and Planet Detroit reported that the Allen Park Planning Commission denied a 26MW data-center site plan after several postponed votes and unresolved questions around engineering, water, and sound. An appeal remains possible.

Allen Park is a reminder that local review is not a decorative step. A project can be pro-technology and still fail a local record if the site plan does not answer the community’s technical questions. Sound, water, power, emergency access, and engineering details are not anti-AI talking points. They are the things planning commissions are supposed to test.

That lesson should travel to Mason, Saline, Ypsilanti, Allendale, and every Michigan jurisdiction watching the next developer walk in with investment numbers.

Confirmed, Alleged, Pending, Disputed

Confirmed: WILX reported the Mason utility request for 3388 W. Columbia Road, the undisclosed company status, and the minimum $1 billion investment claim. LegiScan shows SB1018’s June 4 introduction and referral. OpenAI says The Barn is a 1GW Saline campus with closed-loop cooling and no local infrastructure or energy cost shift to residents. The Michigan Attorney General’s office says it appealed the MPSC approval of DTE’s Saline data-center contracts. WXYZ and Planet Detroit reported Allen Park’s planning denial.

Source-attributed: Michigan Advance reported Whitmer’s no-blanket-moratorium posture and resource/ratepayer-protection framing. Mason’s projected tax-revenue figure remains a local-source claim that needs contract and fiscal backup.

Pending: Mason developer identity, Mason utility-service draft, SB1019 and SB1020 paths, Whitmer’s direct office statement, Saline public contract terms, Allen Park appeal timing, and whether future MPSC/DTE filings keep ratepayers insulated.

Disputed: Whether a statewide moratorium is needed, whether Saline’s protections are transparent enough, whether local-control concerns are being respected, and how much of Michigan’s data-center politics is genuine resident concern versus organized advocacy, industry lobbying, or unsupported claims.

The BadPD Ask

Michigan should publish a statewide data-center ledger. Each major project should have one public page listing developer identity, parent company, land ownership, site plans, water demand, sewer demand, electric load, interconnection costs, backup generation, battery or storage commitments, tax incentives, ratepayer protections, community benefits, construction jobs, permanent jobs, emergency services impact, and complaint contacts.

The ledger should label what is confirmed, what is projected, what is redacted, what is disputed, and what is still missing.

That is how Michigan can build compute without asking residents to accept billion-dollar promises on trust.

Reader Safety And Source-Status Note

This article is an accountability receipt, not a rumor dump, graphic violence post, protected-class attack, or partisan certainty machine. Source dates stay attached. Claims are separated from confirmed records, and missing facts are named for follow-up.

Pine Grove Township: Six Months To Write Local Rules

Update, June 20, 2026; source dates March 26 and June 2026: Pine Grove Township in Van Buren County has now posted an official notice of adoption for Ordinance No. 06-03-2026, a temporary data-center moratorium ordinance. The notice says township trustees adopted it on June 3, 2026, and that the moratorium pauses processing of data-center applications while the township studies public health, safety, welfare, resident, and existing-land-use concerns.

The official notice summary says the moratorium runs for six months from the ordinance effective date, or until the township adopts data-center regulations, whichever comes first. The same notice says the board can extend the moratorium by resolution before it expires. That makes Pine Grove another Michigan local-control receipt, but not an anti-compute ban: the public question is what rules the township writes before any large-load project can lock in rights.

Van Buren County’s Digital Innovation Task Force gives the local context. In a March 26 update, the county described rapid regional interest in data centers, solar, battery storage, and small modular reactor activity. It said the county was working on vetted public information, educational articles, and a vulnerability atlas to map farmland, utility substations, and noise-sensitive areas. That is the useful build-it-right path: put the facts where residents and township officials can see them before rumor, sales pressure, or litigation sets the agenda.

Confirmed: Pine Grove Township posted the moratorium notice and the official PDF says Ordinance No. 06-03-2026 was adopted June 3, 2026. Pending: the full ordinance text, publication date, exact effective date, application inventory, draft zoning language, water and power impact studies, fire and emergency-response records, and any developer or land-control records tied to Pine Grove or nearby Van Buren County projects.

Source Trail

• Pine Grove Township notice page: Temporary Data Center Moratorium (June 2026; checked June 20, 2026) – Official township page linking the moratorium notice.
• Pine Grove Township notice PDF: Ordinance No. 06-03-2026 (Adopted June 3, 2026; checked June 20, 2026) – Official notice summary for the temporary data-center moratorium, six-month term, study purpose, extension option, and clerk-copy location.
• Van Buren County Digital Innovation Task Force monthly update (March 26, 2026) – County context on proactive planning for data centers, solar, battery storage, vetted information, educational articles, and vulnerability mapping.
• WKAR Michigan data-center tracker (Published February 27, 2026; checked June 20, 2026) – Statewide tracker context for Michigan moratoria, legislation, utility decisions, and grid impact.
• Michigan Advance: Michigan data centers weekly download (June 8, 2026) – Statewide tracker and Whitmer/moratorium context.
• WILX: Mason utilities request for data center (June 3, 2026) – Local reporting on Mason utility ask, site, undisclosed developer, and investment/tax claims.
• LegiScan: Michigan SB1018 text/status (Introduced June 4, 2026) – Bill text and status for the proposed data-center moratorium package.
• OpenAI: Stargate Michigan data center (June 1, 2026) – Company-side receipt for Saline scale, jobs, closed-loop cooling, and cost-shift claims.
• Michigan AG: Nessel appeal of MPSC DTE data-center contracts (April 17, 2026) – Official consumer/ratepayer challenge to DTE Saline data-center approvals.
• WXYZ: Allen Park data-center site plan denied (June 2026) – Local report on planning denial and unresolved public questions.
• Planet Detroit: Allen Park planners reject data center (June 2026) – Local accountability context for Allen Park denial.
• Data Center Dynamics: Michigan moratorium proposal (June 2026) – Industry/outlet context for SB1018-SB1020.