Edition

In the Playthrough

you

The people around you carry load and give it back

Bonds are marks with a quality, built slowly and spent fast. Load flows toward you and away; help asked for early is cheap and help asked for late is dear. No one you meet is a background character — each is running a full run of their own in which you are a minor part of theirs.

Feel it in a run →

Trust is slow to build and fast to spend

Trust is collateral accumulated from kept promises: each one raises what others will stake on you, and a single betrayal converts a lot of it back into doubt. It rebuilds, but on worse terms than the original — which is the honest version. Knowing the asymmetry is most of what stops people from spending years of accumulated goodwill in an afternoon and expecting it to refill on schedule.

It is worth separating this from a reputation, which behaves differently and is explained where standing is explained. A reputation is a set of copies other people hold, most of them written from hearsay and all of them stale. Trust between two people who actually see each other is not a copy: it is updated continuously, from direct evidence, by someone who will notice within a week if you have changed. That is why repair works at close range and rarely works at a distance, and why the strategies for managing a reputation are the wrong strategies for a friendship.

Repair is its own operation

Repair is not an apology, not a compromise, and not a negotiation, and confusing it with any of them is the usual way it fails. Negotiation assumes a divisible surplus and partly-opposed interests; repair assumes a shared thing that has been damaged and interests that are aligned. Run negotiation on a rupture and you convert a partner into a counterparty, which the other person feels instantly. The tell: after a good negotiation, both sides feel they got a reasonable deal; after a good repair, nobody is thinking about the deal.

What repair actually consists of:

  • Acknowledge the effect, not the intent. Defending what you meant is the most common failed move. “I’m sorry you felt that way” names the feeling and disowns the effect, and the other person’s ledger records it correctly even when they can’t say why it made things worse.
  • Change the mechanism, not just the outcome. Restitution addresses what happened; preventing a repeat means visibly changing the thing that produced the harm. Restitution without a changed mechanism is prepayment for the next incident, and they know it.
  • Turn toward the attempt. What usually needs repairing is a chain of small failures to reconnect, and accepting a clumsy attempt does more than making a polished one.
  • Time before content. Nothing useful is said while flooded. A pause with a stated return is a repair move; a pause without one reads as an exit.

The part you do not control is the rebuild rate. The hurt person, not you, is the judge of when the matter closes, and asking to be forgiven on schedule is itself a fresh withdrawal — it makes your repair a demand that they manage your discomfort. Do the work, then stop performing the work. Some bonds close anyway; that can happen to an honest person who repaired well, and doing it well still matters, because of who it makes you for every relationship after this one.

Load, and the untallied ledger

Where people share the care of someone — an ageing parent, a child, a household — the load distributes by proximity, availability, and disposition, not by agreement: whoever lives nearest or notices first does the most, a little at a time. Then two things run in parallel. The near person accumulates a silent tally, because families run on an untallied ledger and saying a number out loud is itself felt as a violation. The far person has no visibility of a load made of small unremarkable events nobody reports, and calibrates from the highlights. Both accounts are honest. The resentment is produced by the ledger rule, not by anyone’s conduct — which is why it so often surfaces at an estate, the first time the accounting is made explicit and enforced.

What helps: make the load visible before it is contested — a shared written record, offered as information rather than accusation, because most distant contributors revise once they see the actual list, and the near one usually wants the load acknowledged more than halved. Name the operation — acknowledgement before renegotiating the split; an offer of help that skips the acknowledgement frequently makes things worse. Ask for specific substitutions: “help more” cannot be acted on, but “take the Tuesday appointments” or “handle the finances entirely” can, and distance is no obstacle to the second. And aim for a split both people explicitly agree to, which is a different and more reachable target than a fair one.

Underneath all of that is a rule so ordinary it is easy to miss. A favour received creates a pull toward returning it — uninvited as readily as invited, wanted as readily as not — and the pull works below deliberation, wherever anyone has looked for it. The strange and important property is that this ledger is not supposed to balance. Open balances running in both directions are what closeness is made of: I owe you a dinner, you owe me a favour, neither of us is counting and both of us are counting.

Which is why paying somebody back immediately and exactly reads as coldness bordering on insult. Settlement closes the account, and closing the account is how relationships end. The rule runs on flow, not on settlement — and that is the same fact underneath both halves of this page: why exact fairness between two people is a partnership already winding itself up, and why a well-made askstrengthens a bond rather than taxing it. The ask opens a balance, the balance creates future traffic, and the traffic is the friendship.

Two limits worth stating. The pull is a force and not a contract: some people take and keep taking, and the only enforcement available is your willingness to stop extending credit — which is the rule telling you something rather than the rule failing. And institutions feel none of it. A company registers your loyalty as a retention statistic, not as a debt, so extending person-rules to an organisation is a reliable way to be quietly farmed.

Asking for help is a skill

Its binding constraint is almost never logistical, and almost all the folk wisdom about it is about phrasing, which is the smaller variable. Who you ask dominates how you ask: a polished request to someone with no discretion, resource, or interest returns nothing, while a clumsy request to someone who has the thing and is inclined to give it usually works. So the first move is finding who actually holds what you need — often a named role rather than the person you were routed to. A refusal is information about the person asked — their capacity, their constraints — not a verdict on whether you deserved the thing. And people reliably over-estimate the burden a modest request imposes, so the arithmetic favours asking more often than most of us do.

The trainable core is specificity, and it is close to the whole of the craft. “Do you know anyone who has done this specific thing?” hands the other person a completable action — they either do or they do not, and either way they are finished in a minute. “Keep me in mind” hands them a standing obligation with no end and no way to discharge it, which is why it is the ask everybody sends and the ask nothing comes back from. Script it before you make it; the script is the practice. Ask early, while the ask is still small and the answer can still change your route, rather than at the point where only a rescue would help.

And it decays fastest in exactly the people who most need it: the competent one, the strong one, the one others lean on. Every promotion, every year of seniority, every caring role raises the felt cost of asking — which is backwards, since the stakes those roles carry make an outside view more valuable rather than less.

Four different things called love

One word is doing four jobs, and they behave nothing like each other. The search is an aim you are pursuing: it has a next move, it responds to effort and to where you spend your time, and it can be gone about well or badly. The falling is an event — it happens to you, it is not an achievement, and it is not evidence about anything except that it happened. The being-in is a condition: it changes how everything else looks while it lasts, and it is not sustained by trying harder. The building is the long shared project, which is the only one of the four that runs on the things the rest of this page is about — repair, an untallied ledger, load that has to be divided.

Most bad advice about love is one kind’s rules aimed at another: search tactics offered to someone in a condition, event-hunger applied to a decade-long build, or the build’s patience recommended to somebody who has not started the search. Sorting which of the four you are actually in is usually more useful than any advice about any of them.

Reading a room is a local skill

What a skilled reader of a room is extracting is not, mostly, emotions. It is the group’s local rule set: who defers to whom, which subjects are live and which are closed, whether disagreement is said out loud or expressed by silence, what a request looks like here, and whether “we should do that sometime” is a plan or a courtesy. It is the same object a workplace calls its unwritten rules, learned in twenty minutes rather than written down.

Its defining property is that the pattern library is local. Move country, industry, class setting or generation and the inferences keep firing at full confidence and are now wrong — which is worse than having no skill at all, because the wrongness is invisible from inside. That is the mechanism under one of the most reported and least anticipated experiences there is: a competent adult moves, and becomes socially clumsy overnight, and concludes something has happened to them. Nothing has. A local cache was invalidated at a boundary. What retrains it is exposure plus correction, in that order — a stated prediction, then watching what actually happened. Exposure on its own trains confidence rather than accuracy, because the room almost never tells you when you have misread it.

Where this does not apply. Someone with no family, a network dismantled by an abuser, or a recent arrival somewhere does not have a thin version of “ask for help” — they have none of it, and the real content is institutional and mutual-aid routes. And for anyone who is routinely disbelieved, a refusal is often about credibility rather than capacity, and “a refusal is just information” becomes false comfort; what they need is a witness, a document, or a different person to ask. None of this applies where the person you would ask is the source of the danger.

Try this as a decision — the campaign has people in it who can refuse, drift and leave, and no way to command any of it.

One home per idea. Every mechanism on this site is explained in exactly one place, and everything else links to it. If you find an explanation here that exists nowhere else on the site, that is a bug — tell us on the corrections page.

Evidence and limitsOur judgement

The site's reasoned synthesis of how something works — our judgement, with the reasoning shown, not a citation.

Last reviewed
2026-08-26
What would change this
These are patterns people repeatedly report, synthesised — not measured relationship outcomes. Any claim about how often repair succeeds, or how relationships end, would need its own evidence and is not asserted here. The reciprocity rule in particular is stated as 'wherever it has been looked for' rather than as a universal finding: the stronger claim would need a survey of the cross-cultural work, which this version has not done, and no figure is given for any of it.
Where this frame fails
Treating repair as a skill can quietly imply that any rupture is repairable with enough craft, which is false where the pattern is control, contempt, or fear — there the operation does not apply. See the known breaks in this model.