There’s a specific email that arrives sometime midweek, usually from someone above you, and it says something like: adding you here in case Sarah’s out Thursday. Nothing is asked of you. No task, no deadline. You are simply named as coverage. A redundancy the system keeps warm in case the primary unit fails.
You read it twice. The second read is when it lands: you weren’t chosen for anything you can point to. You were chosen because you exist in the right shape, at the right access level, occupying the right slot. Sarah could be replaced by you. You could, presumably, be replaced by someone else who fits the same slot. The email isn’t about Sarah, or you. It’s about the slot staying filled.
That feeling has a name and an origin, and neither is recent.
The whole week ahead sits inside one question: once a system starts optimizing for continuity instead of people, what happens to the people who used to think they were the point? Not fired. Not failed. Just quietly reclassified from agent to node, from someone doing the work to a component that keeps a function running when another component goes offline.
Norbert Wiener built the mathematics of feedback and control in the years right after the war and then spent the rest of his life warning everyone who’d listen that he’d built something dangerous. Not dangerous like a weapon. Dangerous like a mirror. A system built on feedback loops doesn’t need to know who you are. It only needs to know that the loop closes. Wiener saw that coming before anyone had a word for automation that wasn’t science fiction, and he saw it applying to offices and hospitals and armies long before it applied to software.
This week we sit inside that warning properly, and one thread we’re pulling is uncomfortable enough that it deserves its own room. On Wednesday, the deep dive asks what actually happens to ambition once you suspect the thing measuring your performance was never built to recognize you specifically, only to recognize whether the metric moved. That’s a different question than “am I doing a good job,” and it doesn’t have a comfortable answer waiting at the end of it. It’s for members, and it earns the length it takes.
Friday’s episode opens from a claim that sounds paranoid until you sit with it for longer than a minute: that the modern workplace doesn’t want your loyalty, it wants your redundancy, and it has spent two decades training you to offer both without noticing the difference.
Here’s the piece worth carrying into your own week, free of charge. Ambition used to assume a witness. You worked hard because someone, somewhere, would notice it was you who did it. A system optimized for feedback doesn’t need a witness. It needs an input. And an input that produces the correct output doesn’t require a name, a history, or a reason to keep going tomorrow beyond the fact that the loop needs closing again.
That’s the quiet violence in being called “coverage.” Not that you’re replaceable. Everyone is replaceable in some sense, always has been. It’s that the system has stopped pretending otherwise, and started designing around it. Once you notice that design, you can’t fully un-notice it. The question that leaves you with is the one we’re spending the week on: if you’re a node now, what exactly are you supposed to be ambitious for?
We don’t have that answer yet either. That’s the point of sitting with it for a week instead of a sentence.
Members get the Wednesday deep dive, the Friday episode, and the full archive, and over a few weeks, a working set of tools for thinking clearly about attention, speed, and modern life.
Just some monads considering interaction.