We flagged the same piece of work on August 13. Then again on the 19th, the 24th, the 25th, and the 27th. Five flags. Zero handoffs. The agents did their part correctly every single week, and the work did not move once.
Nobody failed. That is the uncomfortable part, and it is why this is worth writing down.
Here is the mechanism. Most teams build the trip out to an agent with real care. The brief is specified, the tools are scoped, the output has a shape. Then the agent reaches the part only a person can do — a judgment call, an approval, a fact nobody wrote down — and it needs to hand the work back. So it emits a flag. Needs review. Blocked on input. Awaiting confirmation.
A flag looks like communication. It is closer to weather. It has no artifact, so there is nothing to open, only a pointer to a state you have to go reconstruct. It has no owner, because it went to a channel where everyone can see it, and a thing everyone can see is a thing nobody has. It has no date, so it is never late — being late requires having been due. And it has no escalation, so the second flag is indistinguishable from the first.
That last property is the expensive one. A flag costs nothing to repeat. The agent re-raises it politely on schedule, the queue shows activity, the dashboard is green, and the work is exactly where it was in the middle of August. A system that is stuck and a system that is working look identical from the outside, right up until someone counts.
We have argued before that work moving between agents needs an artifact, an owner, and a check. We assumed the handing happened. It mostly does — going out. Coming back, we built a notification and called it a process.
The fix is not more intelligence. It is four fields, added to every point where an agent returns work to a human.
Artifact. What is being passed, in a form the next person can open without an archaeology dig. A link to the draft, not a note about the draft.
Owner. One name. Not a channel, not a role, not the team.
Date. When it becomes late, decided before it is late. A return trip without a due date is a wish.
Escalation. What happens on the second miss, written before the first one. If nothing happens, you have built a flag again with more words.
Run that audit on your own agent-to-human seams this week. Count how many of them carry all four. Then count how many are on their fifth polite repeat.
Takeaway: A flag repeats for free. A handoff comes due. If the return trip from your agents carries no artifact, owner, date, or escalation, your queue is measuring patience, not progress. ✱
