Public-Interest Rescue Acquisitions

A public-interest rescue acquisition is an attempt to buy, restart, or preserve a failing institution because people rely on the service. The buyer may be a coalition of workers, users, community investors, unions, local governments, anchor institutions, or public agencies.

This mechanism belongs beside Worker Ownership Conversions, Community Investment, Steward Ownership, and Community Benefits Agreements. It combines ownership transfer, governance design, capital formation, public legitimacy, and regulated-system boundaries.

Live signal: Spirit 2.0

Spirit Airlines’ restructuring site says the company began an orderly wind-down on May 2, 2026, cancelled all flights, and pointed guests and vendors to bankruptcy-process information. A public statement from Spirit Aviation Holdings named higher oil prices, lack of additional funding, and the failed path out of bankruptcy as reasons for the wind-down.

The Spirit 2.0 effort is a useful signal because it shows public-interest demand forming faster than the legal vehicle. The campaign site describes non-binding pledges, one-member-one-vote governance, proposed profit sharing, worker equity through an employee stock ownership plan (ESOP), and a legal notice that no money is being collected yet. WBTV reported that the effort had $214 million in audited pledges by May 6, 2026. NBC News later reported $337 million in pledges and described legal, securities, bankruptcy, labor, aircraft, airport, and lender obstacles.

The campaign borrows from the Green Bay Packers model. The Packers’ official shareholder page describes the team as a publicly owned nonprofit corporation since 1923, with more than 5 million shares owned by more than 538,000 stockholders, no dividend, a board, an executive committee, and a cap on any person’s share ownership.

Spirit 2.0 is unresolved and legally narrow. It belongs here as a live stress test, not as proof that this mechanism usually works.

Durable case signals

These examples are more useful as baseline cases because they moved beyond a campaign into ownership, operation, or public governance.

New Era Windows shows workers from the former Republic Windows and Doors plant turning a threatened factory closure into a worker-owned cooperative after union pressure, occupation, financing, equipment negotiation, and operating restart. The software lesson is that the acquisition packet has to track worker mandate, asset purchase, patient capital, production restart, and new governance.
Walsh Community Store shows residents in Walsh, Colorado reopening the town’s only grocery store after it closed in 2006. More than 300 residents bought shares, the town raised over $200,000, and a rural economic development loan helped restart operations. The software lesson is that essential-service rescue needs pledge records, local ownership, debt, operating capital, and public-benefit evidence in one packet.
The George Community shows a Kent village using a community benefit society, community shares, match funding, and public grant support to buy and reopen a pub that had closed during the Covid-19 pandemic. The software lesson is that a community acquisition has to join member investment, grants, renovation work, community-use commitments, and ongoing business records.
Isle of Eigg community buyout shows a community trust taking ownership of an island in 1997 after residents faced insecure homes, poor infrastructure, unemployment, and absentee landlord instability. The software lesson is that land and infrastructure rescues need long-duration stewardship records, resident participation, subsidiary entities, and plans for housing, energy, and local enterprise.
Fire-department software consolidation is not a completed rescue acquisition. It is a warning case. A January 12, 2026 Senate letter to the Department of Justice and Federal Trade Commission cited New York Times reporting that ESO Solutions, backed by Vista Equity Partners, had acquired multiple fire-service software businesses and controlled software used by about 20,000 of the nation’s 30,000 fire departments. The software lesson is direct: mission-critical civic software can become an acquisition target itself, and communities may need data-export rights, open standards, cooperative vendors, regional buying power, or public-interest ownership before lock-in becomes too expensive to unwind.

The fire-software case sharpens the pattern. ESO’s own acquisition history says FIREHOUSE Software was used by about 11,000 fire departments when ESO acquired it in 2017. Its later Emergency Reporting acquisition announcement says that product served more than 7,500 fire and emergency medical services agencies in North America. At the same time, the official U.S. Fire Administration National Emergency Response Information System page shows that fire data reporting itself is moving through a national standards transition. That creates a forcing function: a department may need to migrate not because its local practice changed, but because standards, vendors, and product sunsets moved around it.

The other leading vendors are not outside this investment logic. First Due announced a $355 million strategic investment led by JMI Equity in 2025, and ImageTrend announced a strategic growth investment from Welsh, Carson, Anderson & Stowe in 2023. That does not make every vendor abusive. It does mean a civic protocol should assume ownership, pricing, product continuity, export rights, and standards compliance can change independently of the community’s needs.

Where Solidarity Commons Protocol Helps

Solidarity Commons Protocol should sit around mission-critical civic software, not inside every operational system. It can preserve the public-interest layer that ordinary vendor tools do not own:

A procurement mandate records which departments, towns, unions, mutual-aid associations, or regional agencies authorized a shared negotiation.
A vendor-risk record tracks ownership changes, product sunsets, price shocks, data-export terms, migration deadlines, and standards compliance commitments.
A data-export manifest records what was exported, when, by whom, under which contract clause, in which schema, with which hashes, redactions, and receiving system.
A migration packet links old-system records, new-system mappings, unresolved fields, audit notes, and continuity obligations.
A cooperative or public-interest vendor record tracks who owns the software steward, who can vote, who receives benefit, which communities are represented, and which anti-extraction commitments bind the operator.
A pooled purchasing or rescue-acquisition record tracks member commitments, grants, loans, community development financial institution (CDFI) financing, public appropriations, and benefit conditions.

That makes the protocol useful before a rescue acquisition exists. A regional fire association, community foundation, public agency, or cooperative vendor could use these records to lower exit costs, coordinate buyers, preserve evidence, and create the option to move toward open standards, cooperative ownership, or a public-interest acquisition later.

Basic pattern

A rescue acquisition usually has to answer these questions before software can model it honestly:

What is being acquired: an operating company, brand, equipment, real estate, contracts, source code, data, licenses, routes, gates, or only selected assets.
Who the coalition represents: workers, users, communities served, creditors, public agencies, unions, local governments, or mission-aligned investors.
Which ownership vehicle can actually hold the asset: cooperative, trust, nonprofit, ESOP, public authority, community investment vehicle, or hybrid structure.
Which capital stack is legal and credible: pledges, grants, recoverable grants, member capital, accredited-investor financing, public loans, credit enhancement, or acquisition debt.
Which public-interest commitments are binding: route access, affordability, wages, local hiring, service continuity, transparency, or anti-extraction rules.
Which regulator, court, airport authority, lender, trustee, or public agency can stop or reshape the transaction.

Why it matters here

Public-interest rescue acquisitions create records that ordinary business software rarely keeps together:

Pledge intent, contributor eligibility, contributor verification, and securities status.
Coalition roles, organizing authority, negotiation mandates, and member consent.
Asset lists, diligence notes, bid packets, court filings, and public-agency correspondence.
Worker, user, community, and investor governance rights.
Benefit commitments, enforcement terms, and public reports.
Data-export rights, software continuity, open-standard requirements, and migration plans.
Bridge records to regulated systems that must remain authoritative.

Solidarity Commons Protocol should treat this as a coordination mechanism, not a fundraising widget. The useful record is the public-interest acquisition packet: who authorized the bid, who the bid claims to represent, what commitments bind the rescued institution, which evidence backs those claims, and which external systems hold the legal truth.

What software should not flatten

This mechanism is easy to misread as “crowdfunding plus ownership.” In regulated industries, that is not enough.

For airlines, the U.S. Department of Transportation says an air carrier needs safety authority from the Federal Aviation Administration (FAA) and economic authority from the Department of Transportation before it can provide air transportation service. The FAA’s certification introduction says the agency issues an Air Carrier or Operating Certificate and Operations Specifications only after the applicant completes the certification requirements, phases, and gates. Federal regulations also tie certificate issuance to Department of Transportation economic authority when required.

Capital formation has its own boundary. The Securities and Exchange Commission (SEC) says Regulation Crowdfunding offerings must use a registered intermediary and are capped at $5 million in a 12-month period. Associated Press reported that Spirit’s court-approved liquidation involved creditors, regulators, airport authorities, employees, aircraft, engines, spare parts, gates, and landing slots.

Mission-critical software has a separate boundary. A public-sector or cooperative acquisition cannot fix vendor lock-in merely by buying code. It needs data rights, cybersecurity obligations, procurement authority, transition support, and maintenance governance.

Software can preserve the organizing memory, consent trail, source documents, public commitments, and handoff packets. It should not pretend to replace bankruptcy counsel, securities counsel, aviation certification, court orders, airport agreements, labor agreements, lender consent, public records, public procurement, or security review.