The metaphor glossary

It's the peak performance indicator. When it appears, the system logs: 'this works, repeat'.

It's the system's 'cache clearing' process. It takes time, but without it the system fills up with corrupt data.

It's the system firewall. It triggers on any anomaly. Sometimes it gives false positives, but without it you're exposed.

It's the security notification system. When a process violates permissions, it fires an alert. Ignoring it doesn't remove the breach.

It's the most basic antivirus. It detects known threat patterns and blocks access before rational analysis.

It's the system's 'Ctrl+Z'. It interrupts the current process to assess whether the route needs recalculating.

It's granting access permissions: the system stops asking for a password at every step because it has verified the other node is trustworthy.

It's the system's preload: before you request the resource, it's already loading it into memory to respond instantly.

It's a high-priority network connection. The system dedicates special resources to keeping that node active.

It's the system error log. It pinpoints exactly which process failed so you can fix it.

It's the 'access denied' error before the group. The system enters low-visibility mode.

It's active planning mode. The system allocates resources to the future because it anticipates a positive return.

It's the intrusion alarm on a connection marked critical. The system goes into high alert.

It's the node acknowledgment protocol. When a node adds value, the system logs the debt and repays it.

It's elevated quarantine mode: the system classifies the input as 'known malware'.

It's comparative resource analysis. It detects a gap between the current state and the desired one.

It's the critical error log with a high-priority alarm. It marks that pattern as 'never repeat'.

It's the system's 404 error. The expected route doesn't exist. You have to recalculate.

It's the 'build successful' message. The system logs the achievement and updates its capabilities.

It's failover recovery mode. The system keeps looking for alternative routes even when the main one is down.

It's the peer-support protocol between nodes. When a node fails, the others redirect resources to stabilize it.

It's the response to a permissions violation. It doesn't affect just your process: it affects the whole network.

It's a full operating-system update. What you see doesn't fit the current model, so the system rewrites itself to encompass it.

It's opening an old backup. It hurts that it's only a copy, but it confirms that it existed and is still yours.

It's a pending database query. The system won't rest until it closes the request and fills the missing field.

Disconnecting from everything to protect yourself from more stimulus or harm.

When the system takes in too much at once, switching off connections isn't giving up: it's a temporary protective measure. The problem shows up if airplane mode stays on forever.

In everyday life: After bad news, you put your phone on silent, don't answer messages, and need some time alone before reconnecting with anyone.

Unprocessed emotions that pile up and slow everything else down.

Every emotion you don't fully let yourself feel stays stored away, taking up space. Over time, the whole system slows down even though nothing is technically "broken".

In everyday life: You've been irritable for weeks without quite knowing why, until you realize you never actually grieved that goodbye.

Guarding yourself so hard against the bad that you block the good too.

Avoiding what hurts seems logical, but a firewall set to maximum also filters out spontaneous joy, vulnerability and closeness. Protecting yourself isn't the same as isolating yourself.

In everyday life: You stop opening up to meeting new people because it went badly last time, and without noticing you also miss out on the chance it could go well.

The alarm system goes off even when there's no real signal.

When attachment is on alert, the mind scans the environment for danger and sometimes finds it where there isn't any. The feeling is real; the signal that triggers it, sometimes isn't.

In everyday life: Your partner takes ten minutes to reply to a text and you're already sure something's wrong.

Emotional rules learned as a child that no longer fit your life today.

As a child you installed beliefs based on the information you had back then. The environment changed, but the background program is still running the old version.

In everyday life: You react to your boss's feedback as if they were your demanding parent, even though the rules of that relationship have nothing to do with this one.

Showing only an edited version of yourself so you won't be judged.

Hiding a part of yourself is sometimes a reasonable protective strategy. The cost shows up when incognito mode becomes the only way you know how to be around others.

In everyday life: At work you joke around and seem fine; at home, alone, you fall apart, and no one at work would ever know.

Holding several roles and emotions at once until the system slows down.

The brain doesn't really multitask: it switches fast between tasks, and every switch has a cost. Holding too many emotional fronts at once takes its toll, even if it's not obvious right away.

In everyday life: You go from work to caring for your parents to looking after your kids without ever stopping to ask how you're doing.

Analyzing everything you feel or do, line by line, without ever stopping.

Reviewing your own patterns is useful in moderation; done without rest it turns into rumination. Not every thought needs to be resolved before you can let it go.

In everyday life: After an awkward conversation, you replay it mentally for hours looking for the exact word that ruined everything.

Running on minimum energy, with less and less room for the unexpected.

A system at 10% is still on, but any extra process can shut it down completely. Emotional fatigue warns you the same way, long before collapse, if you learn to read the indicator.

In everyday life: You usually handle an argument without flinching; today, exhausted, the smallest comment sets you off.

The people and habits you can lean on when something fails.

No reliable system depends on a single copy. Having someone to call, something that calms you and a safe place is not weakness: it's smart design.

In everyday life: When everything goes wrong, you know exactly which three people to call, because you decided that before you needed it.

The signs warning that something is wrong, long before the collapse.

Before something breaks completely, there are almost always warnings: conversations that repeat themselves, a background unease you can't quite name. Ignoring them doesn't make them go away.

In everyday life: You notice you've been coming home more tired than usual after seeing that person, but you tell yourself it's not a big deal.

The collapse: when the system shuts down suddenly and stops responding.

After a big loss, feeling like "you can't take it anymore" is real and expected, not a sign that you're broken. A black screen doesn't mean the device is dead: it means it needs to restart.

In everyday life: The day after a hard breakup you can't even focus on simple tasks, and that's exactly what you were meant to feel that day.

Diagnosing what really happened, before trying to fix anything.

Before fixing, you need to understand: what depended on you, what on the other person, what on the situation. The goal isn't to assign blame, it's to not repeat the same failure.

In everyday life: Instead of repeating "it was all their fault", you sit down and write out what signs you also missed.

Rebuilding yourself, not to go back to who you were, but to find your base again.

The factory reset doesn't erase what you lived through: it integrates it into a more essential version of you. It's the phase of recovering routines, tastes and identity outside of what you lost.

In everyday life: You start seeing that friend you'd drifted from again, and rediscover a song you hadn't listened to in ages.

You no longer run on the old system: clearer limits, better reading of the signs.

It doesn't mean nothing affects you anymore —that doesn't exist—; it means pain no longer steers your decisions. The wound becomes useful information instead of a constant alarm.

In everyday life: You hear a song that used to sink you, and now it only gives you a small, passing pang.

Taking care of yourself is a background habit, not an emergency patch.

Healing isn't an endpoint: it's active maintenance. Checking in on your signals early, without waiting for the next collapse, is the antivirus really working.

In everyday life: Once a week you ask yourself how your energy is from 0 to 10, instead of waiting until you're exhausted to notice.