Fragility

Fragility is the system’s reduced capacity to absorb impact without breaking.

The Adversity entry established that the hardware was stress-tested by design. Fragility is the state where that stress tolerance has narrowed — where the system’s capacity to absorb shock, process difficulty, or maintain function under load has reduced to the point where impacts that would normally be manageable produce disproportionate damage.

Fragility is not a character trait. It is a condition — produced by depletion, by accumulated unprocessed load, by sustained operation without recovery, by the hardware being asked to handle demands while its reserves are low. The same system that absorbed difficulty easily when resourced becomes fragile when depleted.

---

The signal that fragility is present: minor events produce major responses. A comment that would normally be processed produces tears. A setback that would normally be absorbed produces despair. The system is reacting at a scale disproportionate to the input — not because the system is weak, but because the buffer between input and overload has narrowed to almost nothing.

The response to fragility is not to demand resilience — that’s asking a depleted system to perform. It is to reduce the load and rebuild the reserves. The buffer that provides resilience is made of the foundational inputs: sleep, fuel, rest, connection, processing time. When those inputs are restored, the buffer rebuilds and the system’s impact tolerance returns.

Fragility is the system saying: the reserves are critical. The appropriate response is resupply, not shame.