Saline Treasurer Resignation Shows How Data Center Fights Break Small-Town Government

BadPD source-check, May 21, 2026: Saline Township Treasurer Jennifer Zink resigned after six years in office, citing threats tied to the Related Digital data-center fight in rural Washtenaw County, Michigan. The project is connected to Oracle and OpenAI’s Stargate infrastructure push and has been described in local coverage as a 1.4-gigawatt data center. Zink’s resignation is effective May 29.

There are two accountability lanes here, and BadPD should keep both in view. First: threats against local officials are indefensible. A township treasurer is not the right target for rage over a multibillion-dollar data-center deal. Second: small-town officials are being forced into a rigged-feeling box, where saying no can trigger developer litigation, settlement pressure, utility proceedings, redacted contracts, and resident fury. That pressure system is the story.

What Is Confirmed

Spectrum News reports that Zink announced her resignation at the end of the May 13 township board meeting, citing threats while construction continued on the Related Digital project. Spectrum reports the township board had voted in September against rezoning more than 500 acres of agricultural land, after which the developers sued and the township settled in a way that allowed the project to continue.

404 Media’s visible report identifies the same resignation and says Zink spoke through tears at the meeting. CBS Detroit also reported that Zink resigned after receiving death threats tied to the data-center development, with officials saying threats had come through emails and phone calls.

The township’s own FAQ confirms the legal sequence: Related Digital applied in July 2025 to rezone about 575 acres from agricultural to industrial/research use; the township board denied the rezoning; developers and property owners sued on September 12; the parties later agreed to a consent judgment approved by the Washtenaw County Circuit Court. The FAQ also says township codes control only where the consent judgment is silent and where they do not prevent, preclude, or reduce the size or scope of the authorized project.

Threats On The Meeting Record

The strongest public receipt is the township’s own meeting video: Saline Township May 13, 2026 Board Meeting. YouTube metadata identifies it as an official Saline Township upload, released May 13, uploaded May 14, and running 2 hours, 2 minutes, and 20 seconds. YouTube did not expose usable captions for this check, so BadPD is anchoring the threat descriptions to the meeting video, Spectrum’s written meeting report, and CBS Detroit’s local video description.

What is on the public record is not just a vague “people were mean online” claim. Spectrum reports that Zink referenced someone threatening to “tar and feather” officials. It also reports a threat framed around a “tick nest,” Lyme disease, and death. Zink was also reported describing a wish that she die a “premature death.” CBS Detroit separately says officials described threats arriving through emails and phone calls.

Those examples matter because they show escalation from policy anger into personal intimidation. They also show why the article needs two lanes at once. Residents can say the project should not get cheap public water, a free grid ride, redacted power contracts, or a rushed land-use deal. They can demand records, challenge permits, recall officials, pressure the Michigan Public Service Commission, and fight the consent judgment through lawful channels. But threats aimed at a treasurer’s life, family, home, or health do not create accountability. They isolate the local people least able to absorb the pressure.

BadPD should also be precise: the meeting and local reports document officials describing threats; they do not, by themselves, identify who sent each message, prove a criminal charge, or show whether the threats came from township residents, outside activists, anonymous callers, or people trying to inflame the fight. The missing receipts are police reports, case numbers, screenshots or exports of threatening emails, call logs, voicemails, and any prosecutor or court filings.

That distinction protects the story from two bad shortcuts. One shortcut is pretending the threats are imaginary because residents have legitimate infrastructure concerns. The other is pretending the threats erase the underlying problem: a township said no, got sued, settled, and then became the public face of a national AI infrastructure project involving far bigger corporate, utility, financial, and regulatory actors.

Why The Threats Are Wrong

People have every right to oppose a project, protest, sue, petition, recall officials, demand records, pressure regulators, and ask whether a data center is about local benefit or outside extraction. They do not have a right to terrorize a treasurer, clerk, trustee, or supervisor. Threats do not stop a data center. They make public service unbearable and make small governments easier to break.

That last point matters. When residents turn the township board into the enemy, the company, the utility, the financiers, and the state-level approval process become less visible. The people sitting at the folding tables in a township hall are often the least powerful actors in the room.

The Box Small Towns Are In

Saline Township initially said no. Then the developer and landowners sued. The settlement and consent judgment became the operative document. That is the squeeze: a small township can either spend money it may not have fighting a specialized land-use lawsuit, or settle and get blamed for surrendering. In the short term, officials may be trying to save taxpayers from legal bills. In the long term, residents may feel they have lost control of the place they live.

BadPD’s frame should not flatten that into “the board betrayed the town.” The better question is who designed a process where a rural township is expected to litigate against a data-center developer, major landowners, utility contracts, state tax incentives, and national AI infrastructure politics with a local-government budget.

This is the fairness problem the May 13 meeting exposes. From the resident side, a settlement can look like local officials folding after the vote already happened. From the township side, continuing litigation can look like writing blank checks with public money while specialized land-use lawyers, developers, utilities, and state regulators move the real leverage elsewhere. Both realities can be true. That is why the accountability target should move up the chain: the developer, the utility, the court-approved consent judgment, state regulators, state tax authorities, and lawmakers who have not built a fair process for hyperscale projects landing in small jurisdictions.

The Public-Utility Layer

The fight did not stop at zoning. Spectrum reported that the Michigan Public Service Commission approved DTE Energy contracts for the proposed 1.4-gigawatt data center, after residents and ratepayers criticized the process as rushed and raised concerns about redacted filings, rates, energy demand, water use, wetlands, and noise. Michigan Public later reported that Attorney General Dana Nessel pushed the MPSC to open a contested case, arguing that DTE had not satisfied the conditions meant to protect existing customers from subsidizing the data center.

That is the build-it-right question. If a data center wants enormous power, the public needs enforceable guarantees that existing ratepayers are not carrying the risk. If contracts are redacted, the public needs a credible substitute: regulator findings, cost-allocation proof, stranded-cost protections, interconnection records, and a clear answer for what happens if the customer leaves before infrastructure is paid off.

Water, Cooling, Noise, And Tax Receipts

The township FAQ says the facility is not supposed to use high-water-use evaporative cooling, and describes air-cooled equipment with a water/refrigerant mix. It says developers anticipated about 20,000 gallons per day, but that the township and other agencies would continue reviewing water consumption as construction plans and equipment inventories are finalized. It also describes temporary wells for an on-site concrete batch plant, metering devices, noise limits of 55 decibels at property lines, emergency generators, and EGLE air-permit oversight.

The same FAQ says the township agreed to a 12-year industrial property tax abatement and notes possible state sales and use tax exemption issues. Those are not side details. They are the receipts residents need to judge whether the project is paying its own way or shifting risk and cost onto the public.

Confirmed, Alleged, Pending

Confirmed: Zink resigned effective May 29; she and other officials publicly described threats during the May 13 board-meeting cycle; the township denied rezoning before developers and landowners sued; a consent judgment now governs the project; utility-contract and environmental-review lanes are part of the public record.

Alleged or reported: the specific threat language is reported through local outlets and officials’ meeting statements, including threats involving “tar and feather,” disease, and death. Any criminal-threat investigation, suspect identity, or charging status remains separate and should not be assumed without police or court records.

Pending: resignation acceptance records; any police reports; emails or phone logs documenting threats; the full consent judgment; township legal-cost exposure; DTE cost-allocation proof; final water and cooling numbers; wetlands permit status; tax-abatement final values; and whether state lawmakers create a better process for small towns facing hyperscale development pressure.

BadPD Angle

This is not anti-compute. The United States needs AI infrastructure and domestic compute capacity. But pro-compute cannot mean “small towns absorb the legal risk, residents absorb the uncertainty, and officials absorb the threats.” A serious buildout should come with state-backed technical review, public water and power math, litigation-risk support for small governments, no free grid ride, no cheap public water shortcut, enforceable community protections, and a process that does not leave a township treasurer crying at the end of a meeting because residents think she personally controls a national infrastructure deal.

Threatening local officials is wrong. Letting trillion-dollar AI infrastructure politics land on tiny local governments without a fair process is also wrong. BadPD should keep both receipts attached.

Source Trail

• Spectrum News: Saline Township treasurer resigns, citing threats – Primary local report on Jennifer Zink announcing her resignation at the May 13 meeting, citing threats tied to the data-center conflict.
• Saline Township YouTube: May 13, 2026 board meeting – Official township meeting video receipt for the meeting where Zink announced her resignation and officials discussed threatening messages.
• 404 Media: township leader resigns over OpenAI data-center death threats – Technology-accountability follow-up tying the resignation to the Oracle/OpenAI Stargate data-center dispute; paywall limits full access, but visible text confirms the core claim and meeting quote.
• CBS Detroit video: Michigan township treasurer resigns over data-center threats – Local video receipt saying officials reported threats by email and phone.
• Saline Township: data center project FAQ – Official township receipt: project background, lawsuit timeline, consent judgment, water/cooling/noise limits, emergency generators, and tax-benefit details.
• The Saline Post: Related Digital and landowners sue Saline Township – Local receipt on the September 2025 lawsuit after rezoning denial.
• Data Center Dynamics: township settles lawsuit, project proceeds – Industry receipt on settlement after Related Digital and landowners sued over the rezoning denial.
• Spectrum News: MPSC approves DTE contracts for Saline Township data center – Power-contract receipt: MPSC approval, 1.4GW load, redacted filings, ratepayer concerns, wetlands meeting, and project job claims.
• Michigan Public: AG keeps pressure on MPSC approval – Public-media receipt on Attorney General Dana Nessel challenging the approval process and customer-subsidy safeguards.
• Michigan Public: major construction underway, financing secured – Follow-up receipt that construction and financing had advanced despite continuing public concerns.

BadPD source repair: what this page can prove

This article has been upgraded from a fast watcher item into a clearer receipt ledger for Saline Treasurer Resignation Shows How Data Center Fights Break Small-Town Government. The original item remains above. This repair section does not add a verdict. It explains what the attached source trail can support, what it cannot support by itself, and what records would make the story stronger.

The topic lane is Infrastructure Accountability. BadPD is treating www.youtube.com, spectrumlocalnews.com, www.404media.co, www.cbsnews.com, salinetownship.org, thesalinepost.com, www.datacenterdynamics.com, www.michiganpublic.org as receipts, not as final authority. A receipt can prove that a claim was made, that an agency published a statement, that a news outlet reported a fact, or that a public dispute exists. A receipt does not automatically prove the whole story. That is why this page keeps the links visible and keeps the open questions attached.

Source ledger

• www.youtube.com: Saline Township May 13, 2026 Board Meeting
• spectrumlocalnews.com: Spectrum News: Saline Township treasurer resigns, citing threats
• www.404media.co: 404 Media: township leader resigns over OpenAI data-center death threats
• www.cbsnews.com: CBS Detroit video: Michigan township treasurer resigns over data-center threats
• salinetownship.org: Saline Township: data center project FAQ
• thesalinepost.com: The Saline Post: Related Digital and landowners sue Saline Township
• www.datacenterdynamics.com: Data Center Dynamics: township settles lawsuit, project proceeds
• spectrumlocalnews.com: Spectrum News: MPSC approves DTE contracts for Saline Township data center
• www.michiganpublic.org: Michigan Public: AG keeps pressure on MPSC approval
• www.michiganpublic.org: Michigan Public: major construction underway, financing secured

What is confirmed right now

The page confirms that BadPD captured a public source trail around this claim and preserved the lead item with supporting checks. It also confirms the publication context, the source lane, and the follow-up direction. If the attached links disagree, the disagreement is part of the story. If they agree only on the existence of a claim, then the claim still needs stronger records before it should be treated as settled fact.

For readers, the useful value is the source map. It shows where the first claim came from, where the cross-checks came from, and which public institutions or publishers are part of the record. That matters because low-quality news often strips the claim away from its paper trail. BadPD keeps the paper trail close to the claim so the reader can test it.

What is not proved yet

This page should not be read as proof of every allegation, quote, motive, number, or timeline in the wider dispute. It should be read as a live accountability record. The strongest next version would add primary documents, direct video, court filings, official transcripts, public-meeting records, procurement records, agency data, or named on-the-record responses from the people and institutions involved.

Questions BadPD still wants answered

• What public permits, utility filings, water agreements, power contracts, tax incentives, zoning votes, and meeting minutes exist?
• Who pays if the project needs more grid capacity, emergency backup power, road work, water capacity, or wastewater handling?
• Does the proposal bring its own power, closed-loop cooling, leak detection, public reporting, and enforceable local conditions?
• Which claims come from residents, which come from government records, and which come from advocacy or industry messaging?

Why this stays on BadPD

BadPD covers stories where power, public money, police authority, courts, public safety, infrastructure, recalls, war powers, or public records are in play. A story does not need to be finished to deserve tracking. But it does need a clear label. This page is now labeled as a source-ledger item unless and until the record supports a stronger long-form conclusion.

The standard from here is simple. If a stronger record appears, this post should be updated with the new receipt and the claim should move from pending to confirmed, disputed, or corrected. If no stronger record appears, the post should stay cautious. That is the difference between accountability coverage and content churn.