/pattern/agentic/execution/

Functional group

Execution · Action

The Execution phase stabilizes the bridge from reasoning to the world. It ensures that every planned action is carried out reliably, observed faithfully, and communicated safely. This phase matters because a perfect plan badly executed is indistinguishable from a bad plan — the user sees the same failure. Its absence causes silent tool failures, unsafe side-effects, and lost messages between agents. The three ADPs here cover the full action lifecycle: Executor runs and captures feedback, Tool Use enforces safe boundaries, and Coordinator structures multi-agent communication.

Executor

Reliable execution and systematic feedback collection, with structured retry and outcome capture.

Addresses
Action reliability — handling failure, retry, and outcome capture.
When it stabilizes
When external APIs are flaky, when partial failures must be distinguished from total failures, or when downstream nodes need the result to proceed.
Example
A LangGraph node wraps every tool call in a retry loop with exponential backoff, logging the exact response or error into shared state.

Tool Use

Proxy / adapter interface for safe external function calls, enforcing argument validation and capability scoping.

Addresses
Safe tool boundaries — argument validation, capability scoping, error normalization.
When it stabilizes
When tools are provided by third parties, when argument schemas drift, or when a tool's failure mode could corrupt agent state.
Example
An MCP client adapter validates every argument against the server's JSONSchema before dispatch, returning a normalized error if validation fails.

Coordinator

Management of structured multi-agent communication, ensuring message flow is inspectable and bounded.

Addresses
Communication structure between agents.
When it stabilizes
When more than two agents exchange messages, when message ordering matters, or when agents need to share partial results without exposing full state.
Example
A supervisor pattern routes messages through a central dispatcher that logs every handoff and enforces a max-handoff limit to prevent unbounded loops.

Search

Search patterns, frameworks, and pages.