In Mickey's Trailer, Goofy leaves the wheel and sits down with Mickey and Donald. Then he realizes all three of them are at the table.
“If you're here… who's driving the car?”
The trailer is still moving.
Most handoffs do not feel like handoffs. One system takes one decision, then another. Everything still looks normal, so few people check the wheel.
Some encrypted traffic is worth saving even if you cannot read it today. If better tools can break the old key exchange later, yesterday's traffic may open up.
That matters when the traffic stays sensitive longer than the cryptography protecting it.
People call this harvest now, decrypt later: save the encrypted traffic and handshake now, then hope better tools can open it later.
That is why Google and Cloudflare are not waiting for the quantum computer to show up. They have been adding post-quantum key exchange to normal HTTPS connections because traffic copied now could still matter later.
In March 2026, Google moved its post-quantum migration timeline to 2029 and prioritized authentication. Two weeks later, Cloudflare picked the same year across its products. I read that as a readiness deadline, not a claim that Q-day arrives on schedule.
The counter runs to January 1, 2029 because both companies name a target year rather than a specific deadline date.
We are doing a smaller, weirder version of this with agents: review the pull request, block the deploy, choose the next task, fix the dependency before it breaks.
Each handoff can be reasonable on its own. The hard part is keeping the trail clear enough that a person can understand it and undo it.
Maybe the useful line is not between driving and not driving. Maybe it is between a system that can show the turn and one that only delivers us somewhere.
If an agent avoids a problem I did not see, what record would make me trust the next turn?