Loading content
An agent completely transfers control and relevant context to another specialist. Typical conditions for use: Responsibility clearly shifts between specialists; User interactions must switch to the appropriate agent. The central trade-off: Clear transfer of responsibility is achieved at the risk of losing vital context during the handoff.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
A handoff deliberately transfers a task from one agent or team to another, including the context needed to continue.
The approach comes from delegation, handoffs in distributed systems, and human-in-the-loop processes. Agentic workflows developed it into an explicit routing decision in which a specialised agent assumes responsibility.
The sending participant detects a boundary of responsibility, passes on the task and context, and ends or pauses its own work. The receiving participant continues with clear ownership and return rules.
The conceptual focus and typical structure of the approach.
Use in the relevant working context.
Handoff helps separate responsibilities in agent workflows and make transfers traceable through explicit context.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.