The figure usually cited is 10,000+ ads per day. Exact counts depend on how you measure, and no one has a clean number. The direction is not in dispute: you are being addressed by systems that profit when you look at them.

So when you can’t hold a thought for twenty minutes, the question isn’t “what’s wrong with me?” It’s “who is drawing on my bandwidth, and did I authorize it?”

Your focus isn’t failing. It’s being harvested.

Most productivity advice starts from a bad premise: that distraction is a character flaw, and the fix is more discipline.

Look at the architecture instead. Feeds, banners, autoplay, red badges, and infinite scroll are engineered interfaces. Teams of people are paid to make them harder to ignore. You are not losing a fair fight with your own willpower. You are running a single brain against systems tuned, test after test, to capture it.

That is a security problem, not a moral one. And security problems get solved with audits and firewalls, not guilt.

Continuous partial attention: the background process that never terminates

Continuous partial attention is the state of keeping a slice of your focus allocated to incoming signals at all times. Not because you decided to, but because something might arrive.

Think of it as a process that never exits. Even when no notification fires, part of your cognitive load is reserved for the possibility of one. You sit down to write, but a portion of your attention is on standby for the phone, the inbox, the feed.

The cost isn’t only the interruption itself. It’s the lower ceiling on everything you do between interruptions. Deep work needs sustained, undivided processing. A system that is always partially allocated elsewhere can’t reach it.

The inputs you didn’t choose are still programming you

Repetition is how any system learns. A slogan you’ve heard four hundred times doesn’t need your agreement to become familiar, and familiarity gets mistaken for truth. Fear-framed headlines work the same way. They don’t have to be accurate to leave a residue. They just have to be frequent.

Over time, your default assumptions about what you need, what you should fear, and what you’re behind on are partly written by parties with a financial interest in your answers. You didn’t write that code. You inherited it.

Sovereignty over your own mind starts with one plain admission: the default configuration was not set by you.

Override, don’t just block

Blocking is necessary, and the audits below are about blocking. But a cleared channel doesn’t stay quiet. Something fills it, and if you haven’t chosen what, the loudest source wins.

This is why we build around self-voice. Research on self-referential processing suggests the brain treats its own voice differently from a stranger’s, and our working premise is that this lowers the critical filter that rejects outside instructions. A generic track in someone else’s voice is one more external signal. Your own voice, recorded by you and layered over engineered audio, is an internal one. That’s the difference between consuming input and writing your own. You can read more on the science page.

But the tool comes second. First, you need to know what’s currently running.

Three audits to run this week

No new apps required. A notes file and honesty will do.

Audit 1: The input inventory (one day)

For one ordinary weekday, log every source that addresses you. Don’t judge it yet. Just capture it. For each entry, note:

At the end of the day, mark every row where the trigger was external and the return was nothing. That’s your first list of leaks.

Audit 2: The interrupt perimeter (thirty minutes)

Open your phone’s notification settings and go app by app. For each one, ask: if this never alerted me again, what would actually break?

Keep alerts for people and for time-critical systems. Revoke everything that exists to bring you back to an app. Anything that can summon you without your consent is a hole in the firewall. Close it, then watch how often your hand goes to the phone anyway. That count is useful data about habit versus signal.

Audit 3: The boundary hours (seven days)

Write down what you consume in the first thirty minutes after waking and the last thirty before sleep. These are the windows where your defenses are lowest, and whatever enters then gets the least scrutiny.

After a week, read the log back. Is this input you’d install on purpose? If not, replace it with something you selected: a recording, a plan, silence. Even one boundary window under your control changes the baseline.

Run the audit, then own the channel

None of this requires abandoning technology or moving to a cabin. It requires treating your attention as a system with an owner. That owner is you.

Run the three audits. Cut what leaks. Then decide what goes in the freed bandwidth, because the signal you write beats the signal that’s sold to you.

We’re building the interface for that last step: your voice, engineered into audio you control. Join the waitlist, or see how the app is shaping up.

Leave a Reply

Your email address will not be published. Required fields are marked *