Presence Was the Protocol
The cable guy had to ring your doorbell. That was never just logistics.
Before a technician could touch anything, in your house, on your line, in your panel, he had to be seen doing it. Someone opened the door, watched him walk in, watched him work, watched him walk back out. If the job took him near your router, your breaker box, your safe, there was a witness to that, even if the witness wasn't paying close attention. The badge on his shirt matched a name a dispatcher could produce hours later. The van outside had a number a neighbor could read off if the day went sideways.
None of that ceremony was actually about competence. It didn't verify he knew what he was doing. What it did was convert "a stranger had access to my house" into "a specific, identifiable person had access to my house, for a specific window, and someone else besides the system he touched has an account of it." That conversion is the whole trick. It's what makes access recoverable if it goes wrong. Presence wasn't friction standing between you and the fix, it was the accountability mechanism, disguised as friction so well that almost nobody noticed it was doing work.
Then the friction got engineered away, on purpose, because friction is the thing systems always get optimized against. Remote diagnostics, then remote desktop, then an API key mailed once and never rotated, then a service account with standing production access. Every one of these preserved the reach a technician used to have, sometimes expanded it well past what a person walking through a house could ever touch, and every one of them dropped the four things that made the doorstep version accountable. There's no bounded window; a key doesn't expire when the job's done, it expires when someone remembers to expire it, if ever. There's no identifiability worth the name; a credential doesn't have a face, and "the API key" isn't a person a dispatcher can produce. There's no witness; the only account of what a remote session did is a log the same system generated, which is not a third party, it's the suspect describing itself. And there's no natural revocation event; closing a door happens automatically when someone leaves, closing an access grant is a task somebody has to remember to do, on their own initiative, with no doorway forcing the question.
Nobody sat down and decided to remove the checkpoint. It just stopped being load-bearing once the reach didn't require a body anymore, and the accountability that used to ride along with the body quietly stopped coming with it. The default flipped without anyone voting on it: physical access defaulted to off unless a person was actively, visibly there doing something; digital access defaults to on until somebody notices it shouldn't be and does something about it. Standing access is now the normal state of the world, and the doorbell moment, the "here's what I'm about to do, can I come in," got replaced by a scope grant made once, often years earlier, that nobody revisits until an incident forces the question.
Agentic access is that same gap, run forward. An agent doesn't even have the residual social weight a remote technician still carried, the faint chance a real person might be embarrassed, fired, or sued if the log looked wrong. It has a scope, a schedule, and no doorstep moment at all: the showing up and the being let in collapse into a config file written once. It can touch a calendar, a repo, a customer record, a bank category, in the middle of the night, unattended, with no equivalent of the technician calling in to say he's running behind or the homeowner saying wait, that's not what we agreed. The negotiation that used to happen on a porch, in real time, with two people able to change their minds, doesn't happen at all. It happened once, in the abstract, when someone typed a scope into a form, and it's been running on that decision ever since.
None of this means the old ceremony should come back exactly as it was; a badge and a van aren't going to fix a service account. But it's worth being honest about what actually got lost when the checkpoint disappeared, instead of treating its disappearance as pure progress. Presence wasn't the obstacle between you and service. It was the protocol. We kept the access and let the protocol lapse, and mostly nobody's checking for the doorbell that never rang.