On the morning after the public meeting, the windows are broken and stones litter the study floor. Dr Stockmann’s father-in-law comes to call. Morten Kiil owns the tannery whose waste poisons the Baths, and he has not wasted the morning. Panic over the doctor’s report has driven Baths shares down. Kiil has bought, as he puts it, “as many as I could pay for.”
He paid with the money set aside for the doctor’s family. “It is the money that Katherine and Petra and the boys will have when I am gone,” he tells the doctor. Then he sets out the terms. Kiil expects a retraction to restore the shares’ value and clear his name. If he refuses, “the shares go to a charity, and that this very day,” and Katherine gets “not a halfpenny.” Kiil wants his answer “before two o’clock.”
Kiil ties the family’s inheritance to the doctor’s answer. In the same act, Aslaksen and the editor Hovstad arrive. They have heard about the shares and assume the doctor staged the scandal to buy cheap. The objection has become a trade in their account of it.
The market’s reading
Modern project finance has its own ways of registering dissent. A developer reads a record of delays to learn where a site may stall. A lender asks whether the same problem could affect its loan. The commercial question is what might interrupt the project and what that interruption would cost.
The lender’s view matters to people downstream because financing can place a price on unresolved permissions. A due diligence pack for a hyperscale data center might hold a land-use approval and an environmental authorization for the standby generators. It might hold servicing confirmations from the utility and a set of claims about benefits. Every document in it can be authentic and correctly issued.
A lender reviewing approvals should ask who can challenge them and on what grounds. In Cape Town, The Dissenting Vote examined the distinction between land-use permission and later design scrutiny. The approval conditions govern how much that scrutiny can require. An administrative appeal may be followed by a court challenge to the lawfulness of the decision. Which challenges remain available depends on the decision and applicable law. A sale can transfer the asset while leaving uncertainty over its permissions.
For investors, a dispute can add to the cost of holding an asset while construction waits. For residents, the same waiting period may be the remaining opportunity to change a permission. A financial incentive to settle quickly does not resolve the merits of the objection.
The terms of the benefit
A community benefit agreement can do that by making commitments enforceable. Some agreements are fair bargains. Each party gets something, and the public can read the terms. Others shift risk onto the community, or leave it with promises it cannot enforce.
Lancaster, Pennsylvania, offers a publicly available example. The Federation of American Scientists (FAS) described it as fully executed in its August survey of eight agreements. Its terms make it possible to examine who can enforce the promised benefits.
The agreement provides twenty million dollars in payments, split between community-foundation funding and the city’s climate goals. A separate ten-million-dollar letter of credit backs contingent clean-energy duties. Resource-use provisions sit alongside site safeguards, with some detailed plans to follow later.
Sections 10.1–10.2 make obligations broadly dependent on final approvals and financing followed by construction. A planning contribution takes effect earlier under an express exception. Section 13.3 excludes third-party enforcement. The city can enforce the agreement; residents cannot sue directly under it. Other rights under applicable law remain. Section 13.8 binds successors, so the contractual duties are intended to survive a change of owner.
These terms give the city a financial stake in a project reaching final approval. That can create pressure for disputes to end. Residents retain the ability to object, and an appeal can change an approval before it becomes final. The questions are who can enforce the eventual bargain, and whether the benefits remain worthwhile under the permissions that survive.
FAS says some agreements required public-records requests, although most it found were publicly available. Negotiations can also take place under NDAs. A resident needs the full agreement in time to examine it, including the terms that delay or limit benefits.
Four questions for any bargain
Microsoft’s US community-first initiative includes promises about power costs and water infrastructure. A corporate policy gives residents a basis for questions. A signed undertaking or binding tariff can give a responsible body a means of enforcement. The difference becomes visible when a promise is broken.
Who can enforce the bargain, and is its full text public before the decision it seeks to influence? Does it bind whoever owns the site next? Which project milestones trigger benefits, and who carries the cost of delay? Does any clause restrict residents’ rights to object or challenge an approval?
These questions separate weaknesses that need different remedies. A missing enforcement right calls for a named claimant and a usable remedy. A payment milestone needs scrutiny of who bears the risk. A non-opposition clause would need its own justification. Kiil makes surrender explicit. An agreement should be read closely enough to establish what, if anything, the community is asked to surrender.
Stockmann refused his father-in-law. Ibsen makes it a matter of pride as much as principle, and the family pays the price. Communities that face a priced objection should not need a heroic gesture. They need the terms where they can read them, and a right to enforce what they were promised.
Companions
- Whom Do We Write To, on finding a respondent.
- Your Investor, Your Supplier, on positions that fail together.
- The Bill Has a Date, on commitments with doors.
- What Would Count as Benefit, on promises no number could attach to.
Bibliography
Burns, Kate Garman, and Stephen Badea, ‘How we found eight data center community benefit agreements and why it matters’, Federation of American Scientists, 11 August 2026.
City of Lancaster and developers, ‘AI Hub Community Benefits Agreement’, November 2025, published copy via Columbia Law School’s Sabin Center.
Ibsen, Henrik, An Enemy of the People (1882), trans. R. Farquharson Sharp (Project Gutenberg), Act V.
Microsoft, ‘Community-first AI infrastructure’, 13 January 2026.