Acts of Repair

• Time needed From ten minutes to many years
• Alone Can be practised on your own
• Together Can be practised with others

What this practice is

Acts of Repair is the practice of mending things rather than replacing them, in the widest sense that the word will honestly carry.

It includes relationships: the message you did not answer, the friendship that lapsed for no reason either party can now recall, the family member you were right about and lost anyway.

It includes communities: a group that fractured, a shared space that has been let go, a rota nobody has maintained since the person who cared moved away.

It includes ecosystems: a verge, a stretch of water, a patch of ground. Small and local, usually, and slow.

It includes institutions: a process that has stopped serving the people it exists for, a policy written for a situation that no longer exists, a committee that meets and decides nothing.

It includes data: a record with the wrong name on it, a database that has been quietly wrong about someone for years, a dataset that encodes a mistake and passes it on to everything built downstream.

It includes software and infrastructure: the unglamorous maintenance that keeps working systems working, the fix that will never be announced, the dependency somebody has been supporting alone.

And it includes systems of trust, which are the hardest and the most consequential: the confidence between neighbours, between a public and an institution, between colleagues, between a person and the services they depend on.

Why repair rather than perfection

Repair is more sacred than perfection.

We hold this because perfection is mostly a claim about the future and repair is a claim about the past. Building something new that has never failed tells you nothing about whether it can survive failure. A mended thing carries the evidence that it was worth mending, and that someone was willing to do it.

There is also a practical argument. The dominant instinct in technical culture is replacement. The old system is unclear, the codebase is inherited, the institution is compromised, so it is torn out and rebuilt. Sometimes this is right. Often it discards knowledge that was expensive to acquire, and the new system meets the same reality and acquires the same scars, only later and at greater cost.

And there is a moral argument. When people are harmed, replacement is not available. You cannot rebuild a relationship from a clean specification. What is on offer is repair, or nothing.

Repair is not apology

An apology is a statement. Repair is a change in the world.

The two are related and frequently confused. Saying that you are sorry can be the beginning of repair, and where it is genuine it matters. But an apology that leaves the situation exactly as it was is a transaction in which the person harmed is asked to give something and receives nothing.

Ask what would actually be different afterwards. Money returned. A record corrected. A name removed from a list. A rule changed so the next person does not encounter what you encountered. Time given. A public statement made where the false one was made.

Ask also whether the repair is for them or for you. Repair undertaken mainly to stop feeling bad tends to arrive with a request for absolution attached, and that request is a further cost placed on someone who has already paid.

When you cannot repair it

Sometimes the person has died, or has asked you not to contact them, or the institution no longer exists, or the damage is simply beyond what one person can reach.

This is common and it is not a failure. Two things remain available.

You can repair adjacent to the harm. Do for someone else what cannot now be done for the person you injured. This is not equivalent and should not be presented as though it were, but it is better than paralysis.

And you can stop the mechanism. If a system harmed someone through you, and the system is still running, turning it off is a repair even though nobody will experience it as one.

What this asks and does not ask

It does not ask you to repair everything. A life spent mending every broken thing you encounter would end quickly and badly. Choose what is near.

It does not ask you to reconcile with someone who harmed you. Repair is not owed by the injured party, and any reading of this practice that places the burden on them is a misreading.

It does not require money, tools, health, or a group. Some of the most substantial repairs available to any of us are made of attention and a few honest sentences.

And it does not promise resolution. Many repairs are refused. Do them because they are right, and let the outcome be uncertain.

The sequence

The order matters more than the wording. Nothing here has to be said aloud, and no step is improved by being hurried.

1. Name one thing that is broken and within reach

   Not the largest broken thing you know of. The nearest one you could actually touch this month.

2. Find out what the harm actually was

   Ask the person or people affected, if you can, rather than deciding on their behalf. What you assume was the injury is often not the injury.

3. Say what happened, without softening it

   If you contributed to the damage, say so plainly and without the explanation attached. Explanation can come later, if it is wanted.

4. Do the smallest real thing

   One returned message. One corrected record. One hour of unglamorous maintenance. Repair is made of unremarkable acts done repeatedly.

5. Ask whether the conditions still hold

   If nothing about the arrangement has changed, you have restored the situation to the state that produced the harm.

6. Accept that it may not be finished

   Some repairs are not completed, are not accepted, or are refused. Do them anyway if they are right, and stop expecting resolution as payment.