The Bargain We Can Build

Let us give the town a name: Briar.

It is an imagined place, but the choices we have followed now belong to the same room. Mara wants reliable help with the work of life and a household bill she can understand. Jonas wants skilled work on decent terms. The council wants revenue that can improve services without becoming a trap. The water supplier needs a workable plan. The utility needs a credible commitment. The developer wants to build a successful facility.

None of them can get everything by making a speech about the future. They need an agreement.

The first proposal has changed. The equipment has moved farther from homes. The opening stage is smaller. Later expansion depends on stronger customer commitments and suitable infrastructure. The developer has offered financial protection for specified works. The town has withdrawn an open-ended incentive and proposed support tied to delivery. Some residents remain opposed. Others now see a project they could accept.

This is not a miracle ending. It is a decision that has become better informed.

The question before Briar is whether the remaining bargain is good enough, whether the responsible institutions can enforce it and whether the benefits justify the commitments. The town has to answer with evidence and judgment. It cannot borrow certainty from a national forecast or a company’s confidence.

Here is the kind of agreement I would want it to consider. It is a public design proposal, not a template to sign without local legal and technical work.

Begin with a clear description of what is being approved

The agreement should identify the current project, its stages and the permissions required for each. The first phase should not quietly authorize every later version of the campus. Equally, later phases should not face an entirely unpredictable process if they satisfy clearly stated conditions.

Briar publishes a short account of the first stage and the possible expansion. It distinguishes a land-use decision from electricity service, water arrangements and environmental permissions. Each has a responsible institution. The public record links them without claiming that one approval does the work of all the others.

A dated version remains available. If the design changes materially, the town publishes what changed and which review follows. Residents can tell whether the project being built is the project they were shown.

This is the foundation. A promise cannot be enforced if nobody can agree on what was promised.

The developer benefits too. A clear scope helps it plan and prevents later arguments built on incompatible memories of the first meeting.

Make a capacity request carry a commitment

Briar’s utility examines the requested load and the evidence supporting each stage. It identifies works needed specifically for the customer, works useful more broadly and investments that would be required anyway. Those distinctions enter the cost review.

The customer accepts obligations appropriate to the capacity being held and the risks its request creates. The governing tariff and approved contract specify payment, credit support, milestones and exit treatment. A slower ramp does not automatically send an unexplained residual to households. Nor does the agreement allow the utility to recover the same cost twice or avoid scrutiny of an imprudent investment.

The public summary cannot disclose every commercial detail. It can explain the protection, the responsible reviewer and the conditions under which exposure changes. Independent officials have access to the detail they need.

The town also refuses to count a requested future connection as a completed public benefit. It keeps a distinction between interest, commitment, construction and operation. Later stages earn their place through evidence.

This turns uncertainty into something the parties can manage instead of something the least powerful party discovers on a bill.

Require the operating promise to work in difficult conditions

The facility’s plan describes ordinary service and the periods when supply may be constrained. If the customer receives a benefit for flexibility, the required response is defined and tested. The agreement accounts for what happens afterward, including the return of postponed work.

Clean-supply claims name their boundaries. Annual matching is presented as annual matching. Resources not yet operating carry dates, milestones and a response to delay. Storage and backup commitments identify the service they can actually provide under the relevant rules.

Briar does not choose a favorite technology and treat its name as proof. It asks whether the proposed combination is dependable, compatible with public goals and honest about its remaining impacts. The responsible technical institutions examine that answer.

If an interim arrangement is needed, its duration and review conditions are written down. The facility cannot turn temporary into permanent merely by reaching the end of the calendar with no alternative ready.

The agreement should make success easy to recognize. When the promised resource arrives, the public record shows it. When a response test succeeds, the result is recorded. Accountability becomes a way to demonstrate competence, not only a mechanism for punishment.

Put the water plan in its actual place

Briar’s supplier and relevant authorities examine the source, other demands, seasonal conditions and the proposed cooling arrangement. The project supplies information at the intervals needed for those decisions. The public can distinguish delivered water from estimates of consumption and can see which wider accounts remain separate.

The drought response is settled before operation. It names the trigger, the required action, who verifies it and how the public will be informed. Alternative operating modes are assessed for the pressures they may create elsewhere. An apparent improvement in one account cannot quietly become an unexamined burden in another.

A material change in cooling design requires the appropriate review. Expansion must remain within a supported resource plan. If the evidence does not support the proposed scale, the scale changes or the stage waits.

The company has a right to a competent and timely decision. It does not have a right to make a strained source more abundant through a press release.

Briar also keeps the older water problems on its agenda. It does not make the new applicant responsible for every historic weakness, and it does not use that distinction to ignore the cumulative decision now being made.

Turn local promises into dated obligations

The workforce agreement identifies real routes into paid work. Training is linked to qualifications and employer needs. Reports distinguish enrollment from completion and completion from employment. Local hiring aims are described within the applicable law and with clear measures, rather than a phrase nobody can test.

The town’s financial account includes concessions, public costs and expected receipts. Support is released in stages where appropriate. If lawful recovery provisions apply when a commitment is missed, they are written clearly enough to use. Public officials do not rely on a future negotiation to recover something they could have protected at the start.

The budget treats uncertain growth with care. Some gains strengthen reserves or repair existing assets. Continuing service commitments have a credible funding plan. The town publishes a slower-growth case instead of treating the most hopeful forecast as the only future allowed into the room.

Residents can see how gains reach them. Renters are included in the discussion. Nearest neighbors retain specific protections even if the wider county benefits. A fiscal success cannot erase a site problem by changing the subject.

This is what shared prosperity looks like at the level of an agreement: a route from a commercial activity to a person who is better off, with the missing steps filled in.

Pay for the public ability to check

Briar needs staff and independent expertise. It cannot evaluate a complex proposal with a part-time clerk, an overfull calendar and a hope that the applicant will explain everything fairly.

The process therefore includes lawful funding for technical review and ongoing monitoring. The arrangements protect the independence of the reviewer. The applicant pays required costs without choosing the answer. Public officials disclose relevant conflicts and the basis of their decisions.

The documents remain usable. A plain-language record sits beside the technical material. Major revisions are flagged. Meetings and comment routes allow people with ordinary working and caring responsibilities to participate. Questions receive a response that identifies the relevant decision, not merely a polite acknowledgment.

The town also defines what information cannot be released and why. Security and legitimate commercial confidentiality matter. They should be treated specifically rather than used as a blanket reason to conceal public exposure.

A promise to be transparent should be judged by whether a reasonable person can find what they need to challenge a claim.

Public capacity is infrastructure too. It is the part that keeps the other parts answerable to their purpose.

Give the agreement a life after the ribbon is cut

Briar names the office responsible for each continuing obligation. It sets reporting dates, response times and remedies. It identifies changes that trigger review and distinguishes them from routine adjustments. It provides a fair route to challenge decisions.

Obligations that need to survive a sale are written to do so through the appropriate legal instruments. Credit protection is reviewed as circumstances change. Records remain available to the authorities that need them. A failure path explains what happens if the operator departs or becomes unable to meet its commitments.

The public summary says who can act, on what evidence and through which process. Residents do not have to discover that a promised remedy belonged to an office with no power to use it.

In my draft Abundant Republic, I wrote, “Institutional mechanisms are needed to turn rights from ideals into operable policy.”¹ At Briar, that means a named duty, a usable record, a decision-maker and a consequence. The machinery of accountability should be as carefully connected as the machinery inside the building.

A good agreement is written for the inconvenient year.

That is how it protects the good years too.

Give useful capability somewhere to go

An infrastructure bargain should protect the community from avoidable harm. It should also help the community participate in what the infrastructure makes possible.

Briar considers a separate, carefully governed program for public-interest access to useful tools. The proposal might support local service organizations, small firms or residents who would otherwise struggle to afford capability and training. It requires evidence of need, a budget and evaluation. It cannot become a decorative claim that the data center itself has solved public access.

The town asks which work would improve with better tools. It begins with a few defined tasks and checks accuracy, privacy, cost and the human effort needed. It keeps alternatives available where people need them. It shares what it learns so that other local institutions do not have to repeat every mistake.

The project may help fund this work under a transparent agreement, or the town may choose a different funding route. The important point is that access becomes an actual policy choice rather than a vague promise that everybody will eventually benefit.

We should want residents to meet new technology as users, workers, builders and decision-makers. A future in which they are asked only to host the infrastructure and absorb its risks is an unnecessarily small future.

The public can ask for more because more is possible.

Now let something go wrong

Suppose the second stage is delayed. A major customer has changed its plans. The first building remains in service, but the expected expansion is uncertain.

Under a weak bargain, the town receives a reassuring statement and waits. The utility has already spent. The budget assumes receipts that may not arrive. Training participants are left wondering whether the advertised jobs still exist. Residents hear conflicting explanations.

Under Briar’s proposed bargain, the delay triggers specific actions. The utility reviews the load ramp and the next investment stage. Contracted payments and credit support are examined under their terms. The town updates its revenue assumptions before making new recurring commitments. Training providers tell participants which routes remain available. The public record identifies the change without pretending that confidential customer details must all become public.

The agreement does not make the disappointment vanish. It limits the confusion and clarifies who carries which part.

Now imagine a different problem. The operating sound at nearby homes does not match the approved expectation. The complaint process starts an investigation using the specified method. If a breach is established, the responsible authority requires the appropriate corrective action. The operator can challenge an error through a fair process, but residents do not have to begin by proving that technology itself is bad.

Or imagine a dry period activates the water plan. The facility performs the agreed response, records it and communicates through the established channels. Other users can see that the rule applies when it matters.

A bargain that can handle these situations has earned more trust than one that merely predicts they will not occur.

Now let something go right

The opposite test matters too.

Suppose the first stage operates as promised. The clean-supply project is completed. The facility delivers its tested flexibility. The local workforce program produces recognized skills and paid work. Tax receipts support a useful service without destabilizing the budget. Neighbors can see that conditions are being met.

The public process should recognize that performance. Later applications can use the evidence. A responsible operator should not be treated as though nothing has been learned. Predictable review can reward delivery by making the path forward clearer.

This is how safeguards can support a building program rather than merely restrain one. They distinguish reliable commitments from empty ones. They let a community say yes for reasons it can defend. They help companies understand what it takes to earn that yes.

We should aim for a system in which good projects become easier to identify, better designs become more valuable and avoidable harms become harder to hide.

That is an affirmative vision of progress. It asks society to become better at governing because its technical possibilities are growing.

Do not confuse a fair bargain with a perfect world

Briar will still face disagreement. Some residents may believe the remaining burden is too high. The developer may believe a condition costs too much. An estimate may be wrong despite careful work. A new technology may alter the balance.

No agreement can remove politics, uncertainty or the need for judgment. A good one makes those difficulties visible and gives people a way to respond without starting from nothing.

Nor can a local bargain solve every question about AI. It cannot decide all of the technology’s effects on work, information, power or social life. It has a narrower task: govern the physical commitments made in this place and connect them to legitimate public aims.

That narrower task is substantial. It includes who pays for infrastructure, who gets reliable service, who can sleep, who has access to water, who receives work and how gains support a shared life. There is no need to inflate it to make it important.

We can build a network of such accountable decisions, supported by wider planning and common protections. Some places will be suitable for particular developments. Others will not. Some proposals will improve enough to proceed. Some will remain poor bargains.

The future becomes more credible when we can tell the difference.

The ambition beyond the fence

I want the benefits of useful AI to become ordinary enough that people can rely on them without marveling at the machinery every time. Help with a difficult task. Better access to knowledge. More capable local organizations. Work made less tedious. New ways to investigate problems that have resisted us.

I also want the supporting systems to become stronger because we chose to build this capability. More dependable supply. Better use of resources. Skilled workers with routes forward. Public offices able to examine a technical claim. Communities that can negotiate without being threatened with permanent exclusion from progress.

Those outcomes require effort and choices. They are worth that effort. We should not allow a small conception of responsibility to become a small conception of the future.

The public is already present in the infrastructure story: through shared systems, law, land-use decisions, education, labor and the households that depend on the network. The question is whether that presence carries power and a fair return.

Mara closes her laptop. Jonas leaves a site with work done safely and wages owed clearly. A planner updates a record that someone will need next year. An engineer checks an operating condition before authorizing the next stage. None of these moments needs a grand announcement.

Together, they describe a future that can bear its own weight.

The cloud has a power bill. Let the people who order the capacity answer for their commitments. Let the systems grow where the evidence supports them. Let the gains find their way into ordinary lives.

Then build something worth keeping on.