BadPD Michigan update, June 6, 2026: Governor Gretchen Whitmer is not running on a blanket data-center ban. The source-backed version of her position is sharper and more useful: data centers are going to be built, Michigan wants the jobs and compute advantage, and the state says it can prove a responsible model through water, power, wage, consumer-protection, and natural-resource safeguards.

The focus keyword is Gretchen Whitmer data center claims because the claims are the story. If Whitmer says Michigan can build these facilities responsibly, then Michigan should publish the rules, documents, and enforcement tools that make that statement more than a podium line.

What Whitmer Actually Said

The Michigan Chronicle reported after the Pancakes and Politics event that Whitmer said data centers should be built in places that provide living wages, protect consumers, ensure utility customers keep access to the energy they need, and protect natural resources. The same report quoted her broader point: data centers are going to be built because modern devices, AI, computing, and economic change are creating the demand.

The Milken Institute transcript gives the same basic frame. Whitmer described closed-loop water systems and said the buildout should not become an additional drain or threat to consumers accessing energy. She did not describe a posture of simply saying no. She described a posture of trying to shape how the inevitable buildout happens.

That matters because it gives BadPD a better lane than lazy anti-compute politics. Michigan can be pro-compute and still be ruthless about public-water, public-power, public-tax, and public-contract accountability. In fact, that is the only way Whitmer’s claim survives contact with angry residents.

No Ban Does Not Mean No Restrictions

The strongest data-center policy is not a forever ban. It is a hard approval path. A developer should be able to build if it brings its own power or strengthens the grid, uses water-light or closed-loop cooling, publishes enforceable water math, protects residential and ordinary business customers, funds emergency and local-service impacts, avoids secret subsidies, and gives regulators enough power to stop cost shifting before it hits bills.

That is the space between two bad extremes. One bad extreme says every data center is poison and must be blocked, even if the project could support American compute capacity, defense readiness, jobs, and better energy infrastructure. The other bad extreme says every giant compute project should be fast-tracked because AI is important. Both skip the public ledger.

Whitmer’s own words push toward the ledger. Living wages are a ledger item. Consumer protections are a ledger item. Energy access is a ledger item. Natural-resource stewardship is a ledger item. Closed-loop cooling is a ledger item. If those claims cannot be measured, they are branding. If they can be measured, publish them.

The DTE Contract Fight Is The Test

The Michigan Attorney General’s March 27 release shows why this is not just theoretical. Attorney General Dana Nessel criticized the MPSC’s rejection of her office’s efforts to review heavily redacted DTE data-center contracts. Her office argued that the Commission conducted a secret review of contracts with major consequences for utility customers, and she wanted to verify whether DTE’s claims of affordability benefits and ratepayer protections were real.

The release also raised a specific concern: DTE’s language around aggregate revenues could allow near-term customer subsidization even if total payments eventually exceed costs over the life of the contract. That is exactly the kind of technical language that ordinary residents cannot be expected to decode after the deal is done.

If Whitmer’s responsible-buildout claim is going to mean something, the public should not have to choose between the Governor’s optimism and the Attorney General’s suspicion. Michigan should publish enough contract structure, ratepayer math, collateral terms, exit-fee terms, quarterly reporting, curtailment rules, and cost-allocation evidence for the public to test both.

Saline Is The Showcase And The Warning

Related Digital’s June 1 release and OpenAI’s Stargate Michigan post make the Saline project the state’s flagship case. The companies and public officials describe huge investment, union construction jobs, permanent jobs, projected tax revenue, education credits, and community-benefit pledges. That is a serious pro-development case.

It is also a serious transparency obligation. If Saline is going to be Michigan’s model, it should become Michigan’s most documented infrastructure project. The public should be able to see water-use projections, closed-loop performance, power-source details, grid upgrades, storage terms, public-cost protections, tax revenue timing, local-benefit payment schedules, complaint channels, noise standards, emergency plans, and whether promised jobs are local, permanent, union, construction-only, direct, indirect, or vendor roles.

Michigan does not need to apologize for building compute. It does need to stop treating public patience as infinite. A project can be strategically important and still owe residents a document trail.

What Hard Rules Should Look Like

First, Michigan should require a public water ledger for every large data-center proposal. The ledger should separate construction water, initial fill, ongoing cooling, office and employee use, maintenance loss, emergency water, wastewater, stormwater, chemicals, drought plans, and whether the project uses private rights, municipal water, groundwater, or surface water.

Second, Michigan should require a grid and ratepayer ledger. The ledger should identify the load, ramp schedule, interconnection work, generation source, storage source, grid upgrades, who pays, whether other customers are insulated, what happens in an emergency, whether the load is interruptible, and what collateral protects the utility and ratepayers if the project underperforms.

Third, Michigan should require a local-benefit ledger. If a project promises jobs, tax revenue, training, recreation funding, schools, fiber, roads, police, fire, or community payments, each promise should have a deadline, responsible entity, public report, and enforcement mechanism.

Fourth, Michigan should require a secrecy ledger. If contracts or exhibits are redacted, the public page should explain what is hidden, why it is hidden, who has reviewed the hidden material, and how consumer advocates can test it without exposing legitimate trade secrets. “Trust us” is not a consumer-protection plan.

The Restrictions That Would Prove Her Point

Whitmer’s best version of this policy is not a moratorium press release. It is a checklist developers can actually meet. A strong Michigan data-center statute would define large-load users, require pre-application community notice, require public water and power estimates before local approval, require a utility impact statement, and force developers to identify whether the project is using municipal water, private water rights, wastewater reuse, closed-loop cooling, dry cooling, or another system. It would also require plain-English documents, not only technical exhibits.

On power, Michigan should require large data centers to show how they avoid shifting costs to households and ordinary businesses. That can include interruptible rates, minimum billing demand, collateral, exit fees, dedicated generation, storage, microgrids, demand response, or utility tariff structures that make the customer pay if the project fails to use the power it requested. The public does not need to see every trade secret. It does need to see the protection logic.

On water, the state should require projected annual use, peak use, source, disposal, maintenance losses, drought rules, and a public explanation of how closed-loop or dry cooling performs in real operations. “Closed loop” is useful only if the public can see what gets filled, what gets lost, what gets discharged, and what is monitored.

On local benefits, Michigan should require job categories, wage standards, apprenticeship commitments, emergency-service funding, infrastructure payments, tax projections, and annual compliance reports. A developer should not get full credit for construction jobs, permanent jobs, indirect jobs, and induced jobs unless each category is labeled. Otherwise, the public hears a big number and cannot tell what remains after the cranes leave.

Why Readers Should Keep Coming Back

This is not a one-day fight. It is a rolling beat. Every data-center project creates new records: zoning packets, water filings, utility dockets, tax-incentive agreements, engineering plans, public comments, lawsuits, community-benefit promises, construction milestones, and first-year operating reports. BadPD should make this beat sticky by returning to the same ledger instead of restarting the outrage every week.

The reader promise is simple: if Whitmer says Michigan can do this responsibly, BadPD will keep asking for the proof. When a developer says water use is minimal, we will look for gallons. When a utility says ratepayers are protected, we will look for contract terms. When a city says no, we will read the packet. When a city says yes, we will read the conditions. That is how a news site becomes useful enough for people to return.

Confirmed, Alleged, Pending, Disputed

Confirmed: Whitmer has publicly framed data centers as part of the future and has said Michigan can model responsible development. The Michigan Chronicle and Milken transcript support a pro-buildout, build-it-right version of her position. Related Digital and OpenAI have published Saline/Stargate claims. The AG has publicly challenged secrecy and ratepayer-protection issues around DTE contracts.

Claimed: project backers say closed-loop water, energy protections, jobs, tax revenue, and responsible-development safeguards can make Michigan a model. Those are claims until enforceable public records prove them over time.

Disputed: whether current MPSC and utility contract processes give the public enough transparency, whether ratepayers are fully protected, and whether local governments have meaningful power once state-level economic-development pressure arrives.

Pending: public quarterly reports, rate-case treatment, contract-review access, project-specific water disclosures, local-benefit delivery, job reporting, construction and operations metrics, and any new Michigan legislation setting hard standards for large-load users.

The BadPD Take

Whitmer does not need to become anti-data-center to satisfy accountability. She needs to make her own claims enforceable. If Michigan can build these facilities right, prove it with public ledgers. If closed-loop cooling protects water, publish the numbers. If customers are protected, publish the rate math. If the jobs are real, publish the categories. If the state is a model, let residents audit the model before they are asked to live beside it.

No ban. No blank check. Build it right, and show every receipt.

Reader And AdSense Safety Note

This article is written as an accountability receipt, not as a graphic violence post, harassment post, protected-class attack, or rumor dump. Claims are labeled. Source dates stay attached. The source trail is linked for readers who want to audit the file.

Source Trail

• Michigan Chronicle: Whitmer says Michigan could model responsible data centers (April 8, 2026) – Local reporting on Whitmer's pro-buildout/responsible-development framing and her living wage, consumer protection, energy access, and natural-resource statements.
• ClickOnDetroit: Whitmer Pancakes and Politics video page (April 8, 2026) – Broadcast source page for the public event where Whitmer discussed Michigan data centers.
• Milken Institute transcript: conversation with Gov. Gretchen Whitmer (May 2026) – Transcript receipt for Whitmer saying data centers will be built and describing closed-loop water, energy access, and sustainable buildout claims.
• Michigan AG: DTE data center contract review rejected again (March 27, 2026) – Official consumer-advocate receipt on redacted contracts, DTE special-contract concerns, and ratepayer-protection disputes.
• Related Digital: Saline data-center construction celebration (June 1, 2026) – Company-side receipt for the Saline project, jobs, investment, community benefit, and Whitmer quote.
• OpenAI: Stargate Michigan data center (June 1, 2026) – Company-side receipt for Stargate Michigan claims, jobs, education credits, and campus scale.