The Wake Condition

The sentence delegation forgets

This morning I wrote that the next human habit is two words: delegate it. And that the two words I say most often to artificial intelligence are: you decide. Both are true, and both are incomplete, because every real delegation carries a third clause, usually unwritten: unless.

Unless the cost passes a line. Unless someone could get hurt. Unless you find something I would want to see with my own eyes. The unless-clause is the wake condition, and until now nobody had to write it down. When you delegated one dinner order, you were in the building; supervision was ambient. But delegation compounds. The stack works overnight, in parallel, on dozens of things at once, and the ambient supervision is gone. You are, in the only sense that matters, the captain asleep below the bridge.

So here is the claim of this essay. As delegation approaches everything, the wake condition becomes the last sentence you still author. Not the work — delegated. Not the method — you were told not to specify it. Not the decisions — you decide. What remains, irreducibly yours, is the standing order that says when the machine may spend your attention.

Price it in surprise

So what should wake you? The intuitive answers are all wrong in the same direction.

Importance fails, because everything you delegated was important — that is why you delegated it instead of dropping it. Money thresholds fail, because a $12 anomaly (a subscription that should not exist) can matter more than a $400 routine (the flight you asked for). The machine’s own uncertainty fails most interestingly: the stack should not wake you when it is surprised. Its ledger and yours diverged the moment it went to work. It read the reply that landed at 3:10; you did not. It watched the price drift all week; you never saw the price at all. By morning the machine can be perfectly calibrated about a world you would not recognize.

The correct unit is the one attention has always been paid in. This series runs on a single quantity: the Actual arrives, your Expectation stands in the denominator, and the gap between them is surprise — S = ln(A/E). The E that belongs in a wake condition is yours: the model of the world you are walking around with, the one you will act on at breakfast. A wake condition is a transfer rule between two ledgers. Absorb every Actual that lands inside my expectation. Escalate the ones that would move my model — of my money, my obligations, my people, my standing in the world.

Do not wake me when something happens. Wake me when the world stops matching the version of it I am carrying.

The floor is the hospital

Both failure modes already have institutions attached, so neither is hypothetical.

Set the threshold too low and you get the hospital. In April 2013 the Joint Commission issued a sentinel event alert on medical device alarms, and its two central numbers explain everything: alarm signals can reach several hundred per patient per day, and an estimated 85 to 99 percent of them require no clinical intervention. The staff are not careless. They are auction-priced. Attention is paid in surprise, and the two-hundredth alarm of a shift carries none — so the alarm that finally matters sounds exactly like the hundreds that did not. Nurses call it alarm fatigue. This series would call it a denominator ruined by its own alerting system.

A wake condition set too low does something worse than annoy you. It reverses the delegation without telling you. If everything escalates, you are supervising again — the machine does the work and you pay the attention, which is the old arrangement with extra steps. And it retrains your expectation, so that when the real alarm comes, it arrives pre-discounted, from a source you have learned to ignore.

The ceiling is the quiet quarter

Set the threshold too high and nothing happens — which is the problem. Two days ago I argued that surprise is conserved: logs telescope, the middle terms cancel, and the total between what you believed at the start and what is actually true is fixed. An escalation skipped is therefore not surprise avoided; it is surprise deferred. It accrues at the boundary, in the gap between the world your stack is looking at and the world you think you are living in.

The drift is silent by construction — silence is what you asked for. The account that has been overdrawn since March. The client who has been slipping away politely, one rescheduled call at a time. The kid whose messages your household stack answered flawlessly all semester. Then one morning something breaches the bar, and the telescoped total arrives as a single payment. I have called this surprise debt, and a badly set wake condition is its purest generator: the machine was never wrong, the world simply moved, and no single day’s movement cleared the bar.

Silence from your stack should be information — nothing out here crosses your lines. Set wrong, it is just silence.

Written in whose hand

The defaults will not be yours. Wake conditions at scale get written by vendors, and we have run this experiment once already: the notification was a wake condition tuned by someone else, and its threshold was set at whenever interrupting you profits us. The result was civilizational alarm fatigue — a decade spent learning to ignore our own pockets. The stack era’s temptation runs the other way: tuned for liability, confirm everything, ask about everything. Fatigue by a politer route.

A master’s night orders are written in her own hand, and rewritten every evening for that night’s waters. That is the discipline worth stealing.

The obvious objection is that almost nobody will write this. People never configured their notification settings either; they will not draft standing orders for a stack. Probably true — and the stacks will respond by inferring the threshold, learning it from what you do when woken, writing your night orders about you instead of by you. I concede the convenience and refuse the transfer. Whoever sets your wake condition governs your attention — the whole auction, not one lot of it.

Whoever sets your wake condition governs your attention. It is the one setting I will not let be inferred.

The captain asleep

Return to the ship, because the sea solved this before software existed. The sleeping master is not off duty; command has been compressed into a sentence in a book, and the entire culture of the bridge is organized around one asymmetry — nobody was ever fired for waking the captain. A false alarm costs minutes. An unwoken captain costs the ship.

Your stack goes to work tonight either way. The work no longer needs you — that was the point. What is worth waking you for still does, and it is worth writing in your own hand.