Open-Loop Cognitive Load

A simple explanation

An open loop is anything you have started, committed to, or noticed but not yet closed. An email you intend to answer. A decision you've deferred. A promise you've made and not kept. A small repair you keep meaning to schedule. None of these requires more than minutes of actual work — but each of them stays open in the mind until it is closed, and each open loop costs a small amount of bandwidth to hold.

The cost is not what you pay when you think about the loop. It is what you pay continuously for not being able to fully think about anything else.

An everyday example

You sit down to read a book on a Saturday afternoon. The book is good. Twenty minutes in, you notice your attention has drifted — and what it drifted to was the unanswered message from Wednesday, the form you have to fill out for the kids' school, the conversation you owe a friend, the dentist appointment you have not yet booked.

You return to the book. You read another paragraph. The attention drifts again — to the same loops, in the same order. The book is good. The afternoon is yours. The loops are running in a background process you did not consent to start, and the part of you that wanted to read is sharing bandwidth with the part of you that is quietly tracking eleven things.

What an open loop costs the body

The cost of an open loop is metabolised, not just thought.

The body holds the loop the way it holds any unresolved threat — with low-grade vigilance. The autonomic system stays slightly elevated. The breath stays slightly shallower than it would in true rest. Cortisol drifts a small amount higher across the day. Sleep onset takes longer than it should, and the first half of the night runs at a higher activation level than the body needs.

Multiply by eleven open loops and the felt-experience is I am tired without having done anything. The body did something. It held eleven loops in standby. The cost is real even though no muscle moved.

The behavioral loop

The shape that runs through a loop-heavy life:

1. Commitment registered — you say yes, you notice the task, you intend to handle it.
2. No immediate closure — the task gets deferred to later; the loop opens.
3. Background vigilance starts — the mind silently begins tracking the open loop.
4. Loop occupies bandwidth — every subsequent focus block runs with slightly less working memory available.
5. New commitment registered — the loop count goes up; the vigilance load goes up.
6. Periodic intrusion — the loop surfaces during quiet moments (the shower, the walk, the attempted reading).
7. Postponement again — the surfacing is not the closing; the loop stays open.
8. End of week — the loop count is now in the dozens; the felt-tired has no obvious cause.

The defining feature is that postponement multiplies the load. Each loop is small; the load compounds because the loops do not close.

Emotional drivers

Three feelings, often layered:

• A diffuse background anxiety that does not point at any one thing — because it is the sum of many small things, none of which feels worth a specific worry.
• A quiet self-distrust — the mind has noticed that later keeps not arriving for these loops, and is no longer fully believing future-you's promise to close them.
• An evening tiredness with no obvious cause — the body's metabolic record of the day's vigilance load.

What your nervous system does

The autonomic nervous system treats open commitments as low-grade unfinished business — and unfinished business, ancestrally, was usually a threat. The body runs slightly elevated vigilance. The parasympathetic system has trouble taking over fully because the loops keep issuing small bids for attention. Heart-rate variability drops a small amount. Sleep architecture shifts toward more light sleep, less deep sleep.

The body is doing exactly what it is designed to do: hold the unresolved in a state of mild readiness. It does not know that the open loops are emails and forms rather than predators.

The DojoWell interpretation

Open-loop cognitive load is a clean instance of residue_accumulation — the density signature in which each unclosed commitment leaves a small ambient trace, and the traces compound until the baseline state is half-occupied.

The Meaning System is asking for the bandwidth required for sustained presence — with a book, with a conversation, with a child, with your own thinking. The Threat System, reading the open loops as unresolved obligations, refuses to release the bandwidth until the loops close. The two systems are working from different time horizons. The Threat System wins because the cost of releasing vigilance prematurely was, historically, fatal.

The substitute is ambient vigilance — the chronic low-grade tracking that consumes effort without depositing meaning. The felt-effort is small per loop, but real per loop and compounding across loops.

The equation is sharp. Effort runs continuously in the background. Deposit per moment is reduced because bandwidth is partly occupied. Residue is the load itself. The numerator collapses. Density: low. The fix is closure — either complete the loop, externalise it (a trusted system that the brain accepts as a real holder), or explicitly decide not to do it.

How do open loops affect sleep?

Sleep is where the body would normally do the integration that closes loops — and where open loops produce the most visible cost.

The night begins with the day's loop inventory still in working memory. Sleep onset takes longer because the system cannot fully release vigilance until the loops are either closed or trusted to be held elsewhere. The first sleep cycle runs lighter than it should. By the small hours, the brain may surface a loop into consciousness, and you wake at 3am thinking about an email.

The fix is not better sleep hygiene alone. It is doing one of three things with the loops before the day ends — close them, write them down somewhere the mind trusts, or explicitly decide they are not yours to carry. The bandwidth releases only when the loop is no longer pending.

Practical steps

1. Capture every loop into one trusted place. Not several places. One. The mind releases the loop only when it believes the loop is held somewhere reliable.
2. Close five small loops a day. Pick the smallest five. Most can be closed in under two minutes each. The bandwidth recovered exceeds the time spent.
3. Decide explicitly what you are not doing. A loop can be closed by completion or by refusal. Both release the bandwidth; postponement does not.
4. Schedule a weekly loop review. Once a week, walk through the captured list. Close, delegate, refuse, or schedule. The mind learns the list is real and the load drops.
5. Notice the felt-tired without cause. When evening tiredness arrives without a day that explains it, suspect the loop load before suspecting your stamina.

Reflection questions

• How many open loops can you name right now without writing anything down? How does naming them feel in the body?
• Which open loop has been on your list longest, and what would close it actually require?
• When did you last have an evening that felt fully closed — and what was different about that day?
• What loop are you carrying that is not actually yours to close?

Frequently Asked Questions