Delegation boundary
The point at which a task passes between a person and an agent. Products differ by whether that transition is a copy-paste or a state change on one shared item.
Every agent product has a delegation boundary: the point where a task passes between a person and an agent. Its cost is mostly invisible until the work repeats. A high-friction boundary makes a human restate the task in the agent's interface and carry the result back out by hand, so context is retyped and nothing records that the handover happened. A low-friction boundary makes the handover a state change on an item that already exists, so context, history and ownership follow the work.
The boundary is crossed in both directions. Escalation back to a human — for an approval, a judgement call, or a credential the agent may not use — is the same transition in reverse, and is what human-in-the-loop designs formalise.
This is a descriptive term coined here for comparing products, not established industry vocabulary.