Directory · I
Not sure this is the right entry? Run the check · New here? Start with the premise
Impermanence
1 min read · 296 words
Nothing you've built your model on is going to stay in its current form. Holding that as a feature rather than a betrayal doesn't make loss hurt less — it removes the second injury.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Nothing the machinery encounters will remain in its current form.
The body changes — cells replace themselves, tissues age, capacities shift, the hardware’s specifications drift from the original configuration over the organism’s entire operating life. Relationships change — other control rooms arrive, reconfigure, depart. Conditions change — what was stable becomes unstable, what was absent becomes present, what was present disappears.
The mind’s model resists this. The system builds maps of reality and treats them as permanent — because stable maps are easier to operate from than maps that are constantly updating. The organism plans around the assumption that current conditions will continue. When they don’t, the system produces surprise, grief, disorientation — the signals of a model that has been invalidated by change it didn’t expect.
The operator who integrates impermanence into their operating model — who builds plans that account for change rather than assuming stability — experiences fewer model-invalidation shocks. Not because the changes stop, but because the model expected them.
The Death entry covered the ultimate instance. Impermanence is the principle applied to everything else: the body’s capacity, the relationship’s current form, the job, the health, the conditions that the system has built its comfort around. None of it is permanent. Some of it will change slowly enough that the system can adapt incrementally. Some of it will change suddenly enough that the Grief entry’s recalibration process fires.
The signal in this is not despair. The Meaning entry’s conditions — connection, contribution, creation, alignment — are available in every configuration, not just the current one. What changes is the form. What persists is the capacity of the one at the controls to find the conditions again in the new arrangement.
The model assumes a permanence nothing honours
Everything you encounter changes form. The body's specifications drift across its whole operating life. Relationships arrive, reconfigure and depart. Conditions that were stable become unstable; what was present disappears.
Your mind resists this for a practical reason: stable maps are much easier to operate from than constantly-updating ones. So it builds a model and treats it as permanent, then plans on the assumption that current conditions continue.
When they don't, what you get is surprise, disorientation and grief — the signals of a model invalidated by change it hadn't allowed for. Which means a share of the pain in any loss isn't about the thing lost; it's the shock of discovering that the arrangement was never guaranteed.
That second injury is the part that's available to remove. Holding impermanence as a property of everything, rather than as something that happened to you specifically, doesn't soften the core of a loss at all. It does stop you being blindsided by the structure of reality on top of it.
Notice what you're assuming will stay
Not a morbid exercise. An audit of the assumptions underneath your plans.
Real questions
Isn't thinking about impermanence depressing?
In practice people report the opposite — it tends to produce clearer priorities and more willingness to do things they'd been postponing. What's genuinely bleak is the version where you hold everything as permanent and get blindsided repeatedly by ordinary change. The distinction is whether it changes an allocation. If it makes you do the thing this week, it's working. If it just runs as a mood, that's rumination wearing the idea.
How does accepting impermanence help with loss?
It removes the second injury rather than the first. The core of a loss hurts exactly as much either way — that part isn't negotiable. What it does remove is the additional disorientation of discovering that your model had assumed a permanence nothing in it was ever going to honour. That shock is a real and separate cost, and it's the one that's available to reduce in advance.
Doesn't this just mean nothing matters?
It points the other way. Things mattering and things lasting are different properties, and only one of them was ever on offer. A conversation that happens once is not worth less for not recurring. Most people find the conclusion is to hold things with more attention rather than less — the reasoning that leads to detachment usually has an error in it where lasting got substituted for mattering.
How do I stop waiting for things to settle?
By noticing that the waiting has no endpoint, which is the actual finding. Conditions don't settle — they change, then change again, and the stable period you're waiting for is a feature of the model rather than of reality. The practical move is picking the thing you've been deferring until things calm down and doing a small version of it under current conditions, because these are the conditions.
Can you prepare for change?
Not in a way that removes the impact, and in a way that removes the surprise — which is a meaningful share of the total. Knowing that arrangements are temporary changes what you do while they're running: what you say, what you postpone, how much you assume will still be there. That's preparation in the only sense available, and it operates on your allocation of time rather than on your resilience.
Why does ordinary change feel like betrayal?
Because the model treated the arrangement as a settled fact rather than as a current state, so change reads as something being broken rather than as the normal behaviour of everything. The sense of betrayal is a response to the model being invalidated, not to anyone having done something wrong — which is worth knowing, because it tends to get aimed at whoever is nearest when the change arrives.