The human approved the task, then reviewed the result. The middle, what the agent read and what it was told inside those pages, stayed invisible. That gap is what this paper lands on.
Read the source ↗
attached to Approval →
established
watching → emerging → established
A stable convention across independent vendors. Safe to standardize on — deviating from it now carries cost.
38 documented sightings since Jun 2026 — every one traces to a dated source.
See the evidence → Experts caught errors; novices did not. The difference was review behavior, not trust. A screen that makes scrutiny feel optional skips the most important moment in the interaction.
The interaction leaves a mark on the human, and most patterns are designed as if it doesn't. That's the gap. Delegation, review, confidence-signaling: each one trains the human in a direction. Worth knowing which direction before you ship.
The Times scoped the agent to surface, not conclude. The reporter kept the decision. That boundary was chosen, not accidental. Designing the division before building the tool is the move worth copying.
The agent handed the human a finished result and the human felt expert. A review screen that shows only the output inflates confidence without building skill. That gap is the design problem.
The repair work was real labor, and none of it was visible in the product. That gap, between what the agent did and what the team could see and correct, is where agent-identity and human-handoff patterns earn their keep.
Engineers stopped writing code and started directing it. Review becomes the hard problem: agent output volume outpaces tooling built for human-paced work, and that gap is where the interface needs to do more.
The review screen is also the screen where a worker starts the next job. Workers moved from judging a finished run to copying it for a new one. Treating those as two separate screens adds a step the worker does not need.
The synergy existed in the model; the human did not reach for it. That is a design failure in how work gets passed to the agent, not a capability gap. If a human cannot see the right moment to pass work over, the agent's power goes unused.
The engineer's job moved from writing to judging. Review is now the primary human moment, and most agent products design it as an afterthought. That is the gap to close.
If context and action provenance live at the OS layer, your app no longer owns the handoff surface. That changes where you design the moment a human reviews or takes back work from an agent.
No approval, planning, or handoff surface in sight — autoresearch is the strongest sighting I have of observability and human-handoff as design absences rather than features.
The agent gave up; the expert didn't. That gap is the design problem. Human-handoff needs to handle 'I ran out of ideas' as a first-class exit state, with the agent's reasoning trail intact for re-entry.
Appleton's argument shifts the pressure: model capability is no longer the slow part, design decisions are. The patterns teams name now will be the defaults agentic products ship with, and reversing bad defaults in production is expensive.
Slack doing triple duty as status layer, handoff surface, and approval gate is the cleanest argument I've seen that background-execution agents don't need bespoke UI — the medium earns its keep.