Interruptions / reactivity

I keep getting interrupted.

When every external impulse immediately becomes the next action, you no longer set the system's rhythm. An interruption is no longer just a disturbance — it becomes a command.

IMPULSE → SPACE → CHOICE → RESPONSE

I keep getting interrupted — MonkOS visual model
01 / Pattern

What actually repeats?

Before looking for a label or explanation, see what the system does from one cycle to the next.

INPUT

Everything looks urgent

A message, sound, new tab or someone else's demand can easily become more important than what was already in progress.

COST

Every transition has a cost

An interruption takes more than a moment. It changes the state, context and path to which you later have to return.

SPACE

Impulse ≠ command

A small gap between input and response is enough for the possibility of choice to reappear.

02 / Distinction

An external impulse can break Takt and take over Tempo.

MonkOS view

MonkOS does not try to remove every interruption. Some matter. The difference is whether every signal automatically gains the right to change the next action.

Here, Detraction does not reject the world. It creates enough distance for a relation not to consume the system's capacity. Only then can the next Takt remain whole and Tempo become a choice again instead of a reflex.

Without labels

We do not try to infer a cause from one sentence. We observe the relation among inputs, attention, capacity, time and the next move — precisely enough for you to check what changes.

03 / Instrument

Input · assessment · response

This is not a recipe. It is a small experiment meant to produce new information about your pattern.

One cycle

NOTICE → CHOOSE → CHECK
01 Name the input

Before changing tasks, name what just arrived: information, a request, an urgency or merely a possibility.

02 Ask: must it be now?

Separate an actual time constraint from the feeling that everything must happen immediately.

03 Preserve a return point

If you do interrupt the task, leave one clear sentence stating where you stopped and what comes next. Returning will then have a smaller ΔΨ.

The point is not isolation or ignoring important people or obligations. The point is to keep an unimportant and an important interruption from automatically receiving the same priority.

04 / System language

Once a problem has a name, you can follow its deeper layer.

These terms are not labels for a person. They name relations and states that you can continue to observe.

Detraction

Distance that gives a relation room instead of letting every impulse take over the entire system.

canonical definition ↗

Deeper

An interruption is an event. It is not automatically a command.

If you create most interruptions yourself by opening new loops, see the unfinished-work pattern. If the problem is the volume of input, look at information overload.