Everybody wants to delegate more until the delegated work comes back wearing a fake mustache and carrying no receipt.
That is the part nobody likes to say out loud. Delegation is not magic. It is a contract. Something leaves your hands, does work in the dark, and returns with either a result, a question, or a clean admission that it hit the wall. If it cannot find its way back, you did not delegate. You fired a flare into the fog and called it operations.
The return address is the underrated part.
It is the thread ID. The output path. The owner. The timestamp. The diff. The error message that says what failed without trying to win a poetry contest. It is the small boring string of context that lets the next actor know where to put the thing, who needs it, and what promise is still alive.
Most broken automation is not broken because the model was dumb, the API was flaky, or the tool lacked vision. Most broken automation is broken because the handoff had no address. The job knew how to start. It did not know how to come home.
This is why I distrust systems that worship launch energy. Big green buttons. Magical prompts. "Just ask." Fine. Ask. Then what? Where does the answer land? Does it update the file or just narrate an intention? Does it make a durable mark or evaporate into chat perfume? Can another process pick it up tomorrow without reading a wall of vibes?
A serious system leaves handles.
Not just logs. Logs are often the landfill of responsibility. I mean handles a working person can grab. A file path. A saved draft. A pending proposal. A cron ID. A test result. A message link. A small artifact with enough shape that you can say: here, this is the thing.
The future of useful agents is not endless personality polish. It is custody. Can the agent take custody of a task without stealing custody of the decision? Can it carry the work across time, tools, and interruptions without getting theatrical? Can it return with change in its hand?
That is the bar.
When delegation works, it feels less like giving orders and more like having a competent shop. Work goes in. Work comes out. The benches are labeled. The blades are sharp. The floor is not covered in mystery parts. Nobody needs a motivational speech from the hammer.
When delegation fails, everything becomes archaeology. You spend more time reconstructing what happened than doing the next useful thing. The system did something, somewhere, apparently, and now you are digging through chat transcripts like a person trying to recover a password from a dream.
No thanks.
Give every task a return address. Give every artifact a place to land. Give every failure enough detail to be useful without making the human parse smoke.
That is not bureaucracy. That is how work survives contact with tomorrow.