Directory · L
New here? Start with the premise →
Loss
2 min read · 337 words
Loss is the permanent removal of something the system had built into its operating model.
The Grief entry covers the system’s response. Loss is the event itself: the resource, the person, the capacity, the condition — gone. Not temporarily absent. Not in another form. Gone from the system’s inventory, and the model that still includes it now running a discrepancy it cannot reconcile by waiting.
The hardware registers loss in proportion to how deeply the thing was integrated. Something woven into the core of the model — a central relationship, a defining capacity, a circumstance the life was organized around — leaves a correspondingly large hole. Something peripheral leaves a small one. The accounting is proportional, and it runs on integration, not on what the thing was nominally worth.
This is why the math so often surprises everyone, including the one doing the losing. The childhood home sells and something buckles; a relative everyone assumed was close dies and barely anything moves. Outside observers read the external value. The system was only ever tracking how much of itself had been built on the thing.
Loss cannot be prevented. The Impermanence entry established the principle: everything the system takes into its model will eventually change or leave. Holding that as a feature of the model rather than a betrayal of it does not make loss hurt less at the core — it doesn’t — but it removes the second injury: the shock of a model that had quietly assumed a permanence none of its contents were ever going to honor.
After a loss: let the Grief entry’s processing run. Maintain the machinery through the recalibration. And when the processing has gone far enough, rebuild the model around the absence — not as a wound waiting to close, but as a new and permanent feature of the terrain.
The size of a loss is never the size of the thing.
It is the size of the hole it leaves in the model.