Directory · A
New here? Start with the premise →
Avoidance
2 min read · 445 words
The machinery has a protocol for threats it cannot fight: route around them.
This was a functional solution. The organism that couldn’t outrun the predator survived by not encountering the predator. The wiring that produces avoidance is the flight response applied to everything the system has classified as dangerous — not just physical threats but emotional ones, social ones, informational ones. Conversations that might produce conflict. Tasks that might reveal inadequacy. Feelings that might overwhelm. The system routes around them all using the same mechanism: don’t go there.
The efficiency of avoidance is its danger. It works immediately. The threat is not encountered. The discomfort doesn’t arrive. The short-term signal says: safe. The long-term cost — that the avoided thing still exists and often grows — doesn’t register on the same timeline the machinery operates on.
The avoidance circuit runs below conscious choice. The one at the controls often doesn’t notice the rerouting — it presents as a reasonable decision. I’ll handle that later. This isn’t the right time. I don’t want to make things worse. Each explanation is plausible. Each is also the avoidance protocol producing a narrative that justifies the rerouting. The system is sophisticated enough to make avoidance look like wisdom.
To identify avoidance running: look for the pattern, not the individual instance. A single deferred conversation is scheduling. The same conversation deferred six times is avoidance. A single skipped task is prioritization. The same task migrating from list to list without execution is the system routing around something the hardware has classified as threat.
The diagnostic question: what would happen if this were done right now? Not later. Now. If the answer produces a physical response — chest tightening, stomach dropping, the urge to look away — the avoidance system is reporting. The thing being avoided carries a signal the hardware doesn’t want to receive.
The signal is not reduced by avoidance. It accumulates. The conversation not had becomes harder to have. The task not done grows in the system’s threat assessment. The feeling not processed builds pressure. Avoidance trades present discomfort for compound interest on future discomfort. The exchange rate is never favorable.
What the one in the chair can do is notice the rerouting as it happens — catch the plausible narrative, check the physical response, and make a conscious decision about whether to follow the avoidance protocol or override it. Not every override is necessary. Some things genuinely aren’t urgent. But knowing the difference between this can wait and the system is routing around something it’s afraid of is the operating distinction.