News Refresh Compulsion

A simple explanation

A story is unfolding — an election, a war, a market move, a public emergency. You read the latest. You close the tab. Six minutes later, the tab is open again. The headlines have not changed; the story has not advanced. You refresh anyway. By midnight, you have refreshed forty or sixty times. You have learned almost nothing new. You feel worse than you did this morning and you cannot quite stop.

News refresh compulsion is the hypervigilant loop dressed as informed citizenship. The Threat System, faced with a situation it cannot influence, treats the act of being up-to-date as a small safety signal. Each refresh is a check that the world has not gotten worse without your knowing. The check briefly settles the body. The settling, not the information, is what the loop is paying for.

An everyday example

You wake up; you check the news before getting out of bed. You read while making coffee. You refresh during the commute, between meetings, during meetings. You refresh while walking the dog. You refresh in the bathroom. By dinner you have a faint headache and a low-grade sense of dread that does not lift even when you put the phone down. The dread is partly about the story. The dread is partly about how much of the day has dissolved into refreshes.

You promise yourself you will not check again before bed. You check three times before sleep. In bed, you check once more — just to make sure nothing happened in the last twenty minutes. Nothing happened. You sleep poorly. The loop runs through the night underneath the sleep.

Why can't I stop refreshing the news?

Because the Threat System is being paid in something that genuinely feels like safety. The refresh confirms — for half a second — that the world has not produced a worse outcome since the last check. That confirmation is real, and the body briefly relaxes around it. The relaxation lasts perhaps thirty seconds before the System's prediction model needs a fresh check.

The loop is not stupidity, and it is not lack of discipline. It is a threat-detection system that evolved when staying informed meant scanning the savannah and being told something useful in five minutes by a returning hunter. The system is using its old playbook against a feed that updates faster than the underlying world does and that selects for stories that exceed any one person's capacity to act on them.

The behavioral loop

A loop where information is being used as a regulator:

1. Background uncertainty — a situation is unfolding that the loop-runner cannot directly influence.
2. Threat baseline rises — the System increases its scan rate for relevant updates.
3. Refresh — the news app or tab is checked.
4. Verdict — most refreshes return no actionable new information; some return small updates that change nothing local.
5. Brief regulation — the check briefly settles the body; the world has not gotten worse without your knowing.
6. Re-baseline — the regulation lasts perhaps half a minute; the System's prediction model needs a fresh check.
7. Re-entry — the next refresh fires, often within five to ten minutes.
8. Compounding — across hours, baseline arousal climbs rather than falls. By evening the loop is louder than it was at noon.

Emotional drivers

Three feelings, often dim under the loop:

• A persistent anxiety whose source is the situation, but whose surface form is the urge to check.
• A belief, partly false, that being more up-to-date will produce more agency.
• A faint moral pressure to remain informed, which the System uses to legitimise what is, in form, a vigilance loop.

What your nervous system does

Threat-detection circuitry — particularly the amygdala and the salience network — is calibrated to update its threat model from incoming information. During acute uncertainty, the calibration tightens: the system asks for more updates, more often, because each update either confirms safety or initiates response. The refresh provides input the system has been requesting.

What the system was not built for is a feed that updates without the underlying world updating proportionally, and a stream of stories selected for arousal rather than for relevance to the loop-runner's actual sphere. The system gets satiety from each check — for thirty seconds — and then re-asks. Across hours, cortisol climbs, sleep architecture degrades, and the baseline becomes the new norm even when the original event has resolved.

The DojoWell interpretation

News refresh compulsion is one of the cluster's most consequential loops because the System involved is Threat rather than Reward, and the closure pattern is false progress rather than substitution alone. The original ask was safety — specifically, the ability to anticipate and respond to events that affect the loop-runner's world. The substitute being supplied is a feeling of being up-to-date: the brief settle that follows a check, regardless of whether anything actionable was learned.

The deposit is near-zero across the day. Most refreshes return nothing new. The handful that do return updates rarely change anything the loop-runner can do. The residue is large and compounding: an elevated baseline of arousal, eroded sleep, an attention that holds the news event closer than the people in the room, and a relationship with information that begins to confuse presence with safety.

Density is low because effort is significant and the deposit is mostly absent. The System is correctly executing an old strategy in a new input regime; the loop-runner is paying with mood, sleep, and the felt-quality of their day.

The false-progress closure is what makes the loop particularly hard to interrupt. Each refresh produces a small completion signal — the page loads, the headline is visible, the check is done — that mimics the closure of having genuinely updated one's situation. The System logs the mimicry as a win; the body knows, dimly, it is not one.

How do I stop refreshing news during a crisis?

You do not stop caring about the story. You change how often the Threat System gets to check, and you let the check be at human time-scales rather than at feed time-scales.

1. Set two scheduled news windows per day. Morning and early evening, fifteen to thirty minutes each. Outside those windows, the app is closed.
2. Subscribe to a daily briefing. The briefing arrives once, summarises what actually changed, and removes the loop's apparent need for continuous checks.
3. When the urge to refresh arrives, name what the System is doing. This is the safety check; the world has not changed since fifteen minutes ago. Naming does not stop the urge; it reframes it from need to pattern.

Practical steps

1. For one week, audit your refresh count and your sleep. The correlation is usually visible by day three.
2. Move all news apps off the home screen. The reflex still fires, but the destination requires effort.
3. Identify what specifically you can do about the situation. Action lowers the System's baseline; information about an action-less situation raises it.
4. Take one news-free hour each evening. Not a vow of perfection; one hour. The body's baseline will start to relax even within a few days.
5. Notice the dread that remains when the loop stops. That dread is what the loop has been managing. It is more workable named than it was hidden.

Reflection questions

• During the current story, how many times a day do you refresh? What does the count tell you?
• What does each refresh actually return? How often is it something you can act on?
• Where in your body does the news-refresh dread sit, and what does it want?
• If you stayed informed at the rate the world actually changes — daily, not minutely — what would the loop have to release?

Frequently Asked Questions