BadPD current-source check, June 3, 2026: the Saline Township data-center fight moved from proposal politics into construction-stage accountability this week. Related Digital, Blackstone, Oracle, OpenAI, Walbridge, and Governor Gretchen Whitmer celebrated construction of The Barn on June 1. OpenAI described the site as a 1GW campus. Michigan Public, WGVU, and WILX all covered the same public-facing push: jobs, tax revenue, workforce promises, AI competitiveness, and claims that Michigan is building the project the right way.

That is a major Michigan event. It is also exactly the moment when BadPD should be useful instead of noisy. The question is not whether Michigan should build compute. It should. The question is whether the biggest compute buildout in state history comes with public receipts detailed enough for residents, ratepayers, schools, local officials, and regulators to test every promise.

BadPD’s frame stays pro-American compute and anti-cheap-public-water, anti-free-grid-ride shortcuts. A serious AI data center can be good for Michigan. A serious AI data center should also survive a hard public ledger: power, water, noise, ratepayer protection, local benefit, farmland/wetland protection, emergency-service costs, tax incentives, and what happens if the tenant delays, exits, or misses promised job numbers.

What Moved This Week

Related Digital’s June 1 release says the project team celebrated construction of The Barn in Saline Township and called it the single largest economic investment in Michigan history. The release says financing includes equity from Related Digital, funds affiliated with Blackstone, and fixed-rate long-term debt financing anchored by PIMCO-managed funds and accounts. It says more than 700 Michigan tradesmen and women are already building the campus, that the project will create more than 2,500 union construction jobs, and that the project team is committing $10 million for Saline Recreation Center expansion and modernization.

OpenAI’s June 1 post says it broke ground alongside Whitmer, local community and labor leaders, Oracle, Related Digital, and Walbridge. OpenAI says The Barn is expected to create more than 2,500 union construction jobs, 450 permanent onsite jobs, 1,500 county-wide jobs, and 1,000 indirect jobs. It also says the project is projected to generate $1 billion in tax revenue over the lease term and that OpenAI will make up to $45 million in Codex credits available to eligible Michigan college, community-college, and trade-school students during the 2026-2027 academic year.

Michigan Public reported from the ceremony that business and state leaders ceremonially broke ground on a $16 billion data-center project. The story also captured the tension. Leaders framed the site as a model for responsible AI infrastructure, while critics remain worried about environmental damage, power demand, a possible AI bubble, local control, and whether public safeguards are enforceable. WGVU reported that the first phase is scheduled to go online early next year, and WILX noted the facility takes up 250 acres in Saline Township, south of Ann Arbor.

Those facts are enough for an update. They are not enough for a victory lap.

The Public Ledger Has To Outlast The Shovel Ceremony

Groundbreaking ceremonies are built for optimism. They show flags, hard hats, officials, executives, union labor, and the best version of the project. That has a place. But the public ledger has a different job. It asks what the project will draw from public systems, what it will put back, who is liable if the economics change, and whether the enforcement language is as real as the ribbon-cutting language.

The first ledger column is power. OpenAI says 1GW. The MPSC issue brief for DTE’s Case U-21990 says DTE sought approval of two special contracts with Green Chile Ventures LLC for a data-center customer in Saline Township and an energy-storage agreement under which DTE would develop and procure approximately 1,400 megawatts of storage resources. The same issue brief says the primary supply agreement includes a 19-year minimum contract duration, an 80% minimum billing demand, termination payments of up to 10 years of minimum demand charges if operations end earlier than expected, and credit/collateral requirements.

Those are meaningful safeguards if they are enforceable and if the public can understand how they work. They also raise questions that should remain front-page, not buried in a docket: what specific grid upgrades are needed, who pays for each one, how storage is scheduled, how load ramps, how the data-center customer is curtailed in emergencies, what collateral exists, what public reports will show, and how regulators will make sure existing customers do not inherit costs through later rate cases.

The second ledger column is ratepayer protection. The MPSC’s customer-protection infographic says the data center, not other customers, bears unrecovered costs; the contract has a 19-year minimum term; the customer pays for at least 80% of contracted capacity; early termination fees can reach up to 10 years of demand charges; data-center load can be curtailed before other customers; and collateral protects against nonpayment. That is the state regulator’s public case for protection.

But the Attorney General’s office has been blunt about why consumer advocates do not want slogans in place of access. In April, Attorney General Dana Nessel said DTE’s latest $474.3 million electric-rate request deserved intervention and criticized what she called secret data-center contracts and unproven affordability benefits. Her office said it was fighting in court to read DTE’s Saline data-center contracts. That is the accountability gap: regulators say the protections are strong; consumer advocates say the public cannot fully test the redacted deal.

Water Claims Need Gallons, Not Just Adjectives

The Saline project supporters know water is one of the central political risks. Michigan Public’s April 25 context story reported that the companies said they plan to preserve 750 acres of open space, farmland, and wetlands and use a closed-loop cooling system to protect Michigan’s water. That is exactly the kind of claim that could make this a better project than the worst examples elsewhere.

But closed-loop should not be a magic phrase. The public should know expected average water use, peak use, commissioning demand, refill cycles, maintenance losses, fire-water requirements, sewer discharge, treatment chemicals, drought plans, and whether water use changes as the campus scales. If the answer is low water use, publish the numbers. If the project uses significantly less water than critics fear, the operator should want the numbers public because they help distinguish this build from weaker projects.

Michigan should not let anti-compute panic define every water discussion. It should also not let a company promise low water use without a readable water ledger. Water-light by design is good. Water-light by enforceable document is better.

Jobs Are Receipts Too

Jobs are one of the strongest arguments for the project. Related says more than 700 tradesmen and women are currently building the campus and more than 2,500 union jobs will be created during construction. OpenAI lists 450 permanent onsite jobs, 1,500 county-wide jobs, and 1,000 indirect jobs. WILX repeated the core job and tax-revenue claims in local coverage.

Those commitments need their own ledger. Which jobs are construction jobs, which are permanent onsite jobs, which are vendor or indirect jobs, what wages apply, what apprenticeship commitments exist, what local-hire standards exist, and what happens if permanent job numbers land lower than promised? The answer cannot be that any job number is good enough because the project is large. Public benefit should be measurable.

The $10 million recreation-center commitment belongs in the same file. It is a real local benefit if delivered. The public should also know whether it is a voluntary grant, enforceable community-benefit term, philanthropic side deal, tax-offsetting agreement, or part of a broader mitigation package. A useful public file would show the payment schedule, recipient, restrictions, reporting, and what happens if project ownership or timing changes.

Local Control Did Not Disappear

One reason this project remains politically hot is that residents and nearby communities have argued the process moved faster than local trust. Michigan Public’s June 1 story says community members and environmental groups have long feared irreversible impacts and have protested around permitting meetings and the area. WGVU’s June 2 story described the project as facing a lot of opposition from people worried it could hurt the community south of Ann Arbor. WILX noted that residents have spent months voicing concerns not only about Saline but about proposed data centers across the state.

That opposition is not automatically proof the project is bad. It is proof the public wants a stronger lane than trust-us development. Once a project becomes a statewide economic-development priority, the local township can feel like the smallest player in the room. That is when state officials need to over-disclose, not under-disclose.

Good local control in a project this large does not mean every neighbor gets a veto. It means every neighbor gets a clear record: what was approved, who approved it, which conditions apply, who enforces them, where to file complaints, what monitoring will be public, and what remedies exist when the operator misses standards.

Confirmed, Alleged, Pending, Disputed

Confirmed: Related Digital and partners publicly celebrated construction of The Barn on June 1, 2026. OpenAI says the campus is 1GW and part of Stargate. Local reporting says the project is moving toward first-phase operation early next year. Related and OpenAI claim thousands of construction jobs, permanent jobs, local tax benefits, a recreation-center pledge, and broader workforce commitments. The MPSC issue brief documents special-contract terms including a 19-year minimum duration, 80% minimum billing demand, storage procurement around 1.4GW, termination payments, collateral, and quarterly reporting duties.

Alleged or claimed by parties: project backers say the build will protect water, create energy savings or ratepayer benefits, and set a responsible-development example. Opponents and consumer advocates warn about environmental impact, local-control pressure, redacted contracts, power costs, and whether ordinary customers could still absorb risk through future utility filings.

Disputed: whether the special-contract protections are transparent enough, whether existing ratepayers are fully insulated, whether public redactions prevent meaningful review, whether local benefits outweigh land-use and environmental costs, and whether this project should become a template for future Michigan data centers.

Pending: public quarterly contract reports, the Attorney General’s access and appeal posture, future DTE rate-case treatment, data-center large-load tariff design, final water-use disclosures, noise compliance measurements, emergency curtailment details, storage procurement records, local-benefit delivery, and first-phase operational performance.

The BadPD Ask

Michigan should build serious compute. The state should also publish a serious compute ledger. A project of this size should have a public page that tracks power load, storage status, interconnection work, water-use commitments, closed-loop performance, emergency-response plans, backup generation, noise monitoring, job commitments, tax revenues, community-benefit payments, ratepayer protections, and quarterly MPSC reporting.

That page should not be a marketing microsite. It should be a living accountability file. It should link to orders, permits, reports, public comments, monitoring data, and plain-English summaries. It should separate what is confirmed from what is projected. It should say when a document is redacted and why. It should show who can enforce each condition.

The United States needs compute capacity. Michigan has a chance to help build it. The way to beat bad data-center politics is not to mock residents or hide behind national-competitiveness language. It is to show the receipts so thoroughly that a good project can stand on documents instead of vibes.

The Barn broke ground. Now the public ledger has to catch up.

Source Trail

• Related Digital press release on The Barn construction celebration (June 1, 2026) – Company-side receipt for project scope, financing mix, job claims, recreation-center pledge, and Whitmer quote.
• OpenAI: Building the infrastructure for the Intelligence Age in Michigan (June 1, 2026) – Company primary receipt for 1GW campus language, jobs, school/training/Codex-credit claims, and broader Stargate framing.
• Michigan Public: company leaders say Saline development will set example (June 1, 2026) – Local accountability reporting from the ceremony, including risks, opposition, water/power concerns, and first-phase timing.
• WGVU: Whitmer, OpenAI, Oracle CEOs celebrate Saline Township data center (June 2, 2026) – Local broadcast receipt for the celebration, opposition frame, first-phase timing, and Altman remarks.
• WILX: Oracle, OpenAI break ground on The Barn (June 1, 2026) – Local TV receipt for acreage, jobs, tax-revenue claims, and resident pushback.
• MPSC issue brief for DTE special contracts in Case U-21990 (December 18, 2025) – Primary state regulatory receipt for 19-year term, 80% minimum billing demand, approximately 1.4GW storage agreement, quarterly reporting, and cost-protection conditions.
• MPSC data-center customer-protection infographic (Accessed June 3, 2026) – Primary state summary of risk protections, minimum billing, early termination, curtailment, and collateral claims.
• Michigan Public: major construction underway, financing secured (April 25, 2026) – Context receipt on financing, closed-loop cooling and open-space claims, AG appeal posture, and power load context.
• Michigan AG: DTE rate-hike intervention and secret-contract criticism (April 28, 2026) – Official consumer-advocate receipt tying DTE rate case scrutiny to data-center approvals and redacted contract concerns.