Somewhere in your near future is a dialog box. Your agent has assembled the plan, the vendors are selected, the prices are locked for the next ninety seconds, and everything is waiting on one component with a latency measured in hours: you. The button says Approve. Behind it, eleven machine parties are holding their positions, all of them capable of completing the entire errand in less time than it takes you to read this sentence, all of them idling, because the charter still requires a human signature and the human is at lunch.
That dialog box is where the next decade of the digital city gets decided, and I want to describe the pressure it applies before the pressure becomes invisible.
Start with the tempo gap, stated plainly. The new residents operate at millisecond scale; the legacy residents operate at the scale of afternoons. The payment rails the agents use settle in under a second, at a cost below a cent, a billion demands a day on one network alone. The approval in your inbox settles whenever you next open it. In every mixed process, every workflow where machines do the work and a human ratifies it, the human is now the long pole by a factor of a million. Engineering has a word for the slowest component in a pipeline, and the word is not flattering: the bottleneck. For thirty years, computers waited on us and we called it responsiveness. Now the waiting has reversed, and everything about the city's design will begin optimizing against the wait, because that is what optimization does. It finds the slow part and routes around it.
You can already feel the routing in miniature. The confirmation that became a default. The approval that became a batch approval. The setting, somewhere in every agent product, that says some version of: stop asking me. Each one is individually reasonable. The requests are repetitive, the stakes are usually small, the agent is usually right, and being interrupted eleven times an hour to bless the obvious is a genuinely bad way to live. So the rational human, faced with the tempo gap, does what every rational human does with an alert that is almost always fine: stops reading it. Approval fatigue is not a moral failure. It is the correct response to being made the rate limiter of a system that outpaces you by six orders of magnitude.
But watch what the sum of those reasonable choices builds. Oversight that exists on paper and not in practice has a name in every industry that has ever had an accident: the rubber stamp. Aviation, medicine, finance, all of them learned the same expensive lesson, that a human placed in a loop merely to say yes will eventually say yes to the thing the loop was built to catch. The loop does not fail when the human is removed. It fails earlier, when the human is still present and no longer looking, which is worse, because the presence keeps the paperwork clean. The city will be full of processes that are supervised in exactly this sense: a signature at the bottom, a person at lunch, a system that learned long ago that the signature always comes.
The honest framing, then, is not whether humans stay in the loop. It is which loops deserve a human, because the answer cannot be all of them, and pretending otherwise is how all of them end up with the rubber stamp. Spend your slowness like the scarce currency it now is. The routine, the reversible, the low-stakes, the already-verified: let them run at machine speed, uninterrupted, and mean it. The consequential, the irreversible, the novel, the expensive: those get the afternoon, the full human latency, applied on purpose and without apology, and any system that pressures you to hurry there has misclassified the transaction.
In my own companies we design the queues around exactly this line. The machines may read, sort, draft, retry, and reprice all night without asking anyone. Anything irreversible waits for a person, and the waiting is written into the system as a feature rather than tolerated as a defect. It is the cheapest safety architecture ever invented: a queue that knows which of its items can hurt you.
Notice that this inverts a value the last century taught us. Speed was virtue for so long that slowness still reads as failure, and the tempo gap will read, everywhere, as an argument that the human should step aside. Sometimes it is. But there are decisions where the delay is not overhead on the judgment; the delay is the judgment. Sleeping on it was never about sleep. The waiting period, the cooling-off clause, the second signature, every civilization builds deliberate slowness around its most dangerous choices, and it does so precisely because something that can act instantly will, and some acts should cost time. In a city where everything else has stopped waiting, the ability to wait becomes a feature only one resident can supply.
So the slowest resident should hold the title with more self-respect than the name suggests. The machines are not fast where we are slow; they are fast where speed was always the right answer, and we were the wrong tool. Where we are slow, mostly, is where slowness was doing unacknowledged work. The city will keep presenting the dialog box, and the box will keep whispering that you are the bottleneck, and the whisper will be true. The skill is knowing when to take it as an insult, and when to take it as a job description.
Approve nothing at machine speed that you would regret at human speed. That is the whole discipline. The city can have every millisecond except the ones that were always ours.