mid mixed B 4.33

The Civic Patch Tribunal

Cities establish public tribunals to allocate responsibility when human maintainers and coding agents jointly develop software that governs essential services.

Turning Point: After an automated benefits update wrongly cancels payments to 18,000 people, a national procurement court orders every municipality to submit machine-authored public software to a newly created civic patch tribunal.

Why It Starts

Open-source responsibility charters evolve into enforceable municipal law. Every change to public software carries separate records of human approval, agent execution, testing, and restitution. Citizens can challenge not only an algorithmic decision, but also the development process that produced it.

How It Branches

Open-source projects establish distinct permissions and audit obligations for human contributors and coding agents.
Municipal buyers require every machine-authored dependency to name a bonded human sponsor and retain its verification record.
After a benefits failure, a tribunal reconstructs the exact chain of contributions and divides restitution responsibilities among maintainers, vendors, and agencies.
Public procurement begins to favor projects with inspectable governance histories over those offering the lowest development bids.

What People Feel

At 8:40 on a rainy Tuesday morning in Leeds, benefits clerk Mara Ellison projects a disputed code change onto a tribunal wall. Three residents watch as the chain of approvals that emptied their accounts unfolds before them.

The Other Side

The tribunals may amount to accountability theater. Large vendors can afford bonds and compliance teams, while volunteer projects with better code vanish from public procurement because no one can afford to sponsor them.