The morning the repair is simply there
A resident reports a broken pump, a funded team repairs it, another person checks the result and the record explains what happened. A well-designed institution can turn a small contribution into a visible improvement without requiring the resident to chase every department.
A decision should arrive in somebody’s life
Consider a neighbourhood deciding to repair a pump. The vote may take minutes; the useful outcome takes parts, expertise, access to the site and a way to pay for the work. In a possible arrangement, residents can see the agreed budget, the responsible operator, an expected completion date and the evidence needed to accept the repair. If work stalls, they know where to ask for help. This is a design example, not a reported project outcome. Its ambition is ordinary and substantial: people should be able to trust a shared decision enough to plan their day around its delivery.
Separate the powers that make action possible
OpenZeppelin’s governance documentation distinguishes proposing, voting, queuing and execution, with timelock roles that include cancellation and administration. It offers a technical example of powers that can otherwise remain hidden behind a voting screen. For a physical repair, the corresponding roles might belong to residents, a budget holder, an operator and an inspector. Write down what each may do and who can replace them. Some actions can be automated, such as releasing a scheduled payment once agreed conditions are met. Others require judgement or physical work. A clear division lets each person contribute without granting any one role unlimited control.
Keep the promise attached to its budget
The Participatory Budgeting Project treats proposal development, voting and implementation as connected stages. Decidim’s Social Contract requires decisions and their treatment to be traceable. Our hypothetical repair process could combine those ideas in one public record: a proposal, an approved amount, a work order, progress and a reason for any delay. Residents should be able to distinguish an idea awaiting assessment from work that has actually been funded. The operator also benefits from a clear commission and an agreed acceptance test. A visible chain of responsibility can reduce duplicated requests and make coordination easier across people who have never met.
Recognise contributions without confusing records with results
SourceCred uses a graph to connect contributions and distribute recognition through their relationships. That is useful inspiration for remembering the reporter, the person who diagnosed the fault and the person who documented the repair. It does not establish whether the pump works. In our proposed arrangement, recognition for reporting would be separate from payment for completed work and from evidence of service restoration. Contributors could agree those distinctions before beginning. A small intervention may prevent a large failure; several visible actions may produce little benefit. Keeping the categories explicit makes it easier to reward useful participation without encouraging people to manufacture activity.
Inside the Commission
The Assembly can reconsider an allocation only after the responsible directorate certifies a proposal. The directorate cannot certify the omitted need because it falls outside the existing objective. The opportunity to vote exists on paper while the proposal can never reach it. Redesign must therefore include agenda access, evidence standards and amendment powers, rather than changing the ballot alone. Physical systems also need accountable operators: no on-chain result repairs a pipe without resources, labour and a responsible implementation process.
Make correction part of a successful project
Suppose an inspection finds that the repaired pump is unsafe. A defined pause and an independent review can protect residents while giving the operator a fair opportunity to explain or correct the work. Payment terms should include legitimate material costs and labour already performed, so a safeguard does not casually transfer every risk to the worker. A complaint should identify what is disputed, who reviews it and when a decision is due. Residents should also have a route when the inspector is wrong. Designing this in advance can make cooperation less frightening: disagreement becomes a process people can use, rather than a breakdown they must endure.
Build one complete loop
CommunityRule offers templates for making a group’s governance arrangements explicit. A useful exercise is to write a one-page agreement for one small project: how it is proposed, funded, delivered, checked and reconsidered. Try it with a repair, a shared tool purchase or a community event. Record what was learned and amend the agreement for the next cycle. This is a suggested exercise rather than an endorsement of any particular template. The laboratory lets you assemble the conditions for a repair to reach completion. A group that can reliably finish one useful project has gained something reusable: the confidence and practical knowledge to attempt another.
What would let a resident follow an approved proposal all the way to a useful result, with a fair way to challenge mistakes?
Bring the decision into daily life.
Give an approved repair a budget, a responsible operator and a way to verify completion. Add a complaint and review route, and examine when releasing payment becomes justified.
Open this experiment