Agent architecture

Index of articles on architectures for multi-step, tool-using systems, including control-plane placement, memory boundaries, and orchestration patterns.

Engineering notes on architectures for multi-step, tool-using systems, including control-plane placement, memory boundaries, and orchestration patterns.

Core articles

Section resources

Context, reusable contracts, related links, and external baselines for this topic.

About this section About this section

Focus

  • Orchestration patterns (control-flow mechanisms) — where control flow lives and how workflows are sequenced.
  • State & lifecycle management — what persists across steps and boundaries (session/thread/run), what resets, and when.
  • Tool invocation lifecycle — selection, authorization/enforcement, validation, error handling, retries, and egress constraints.
  • Write paths — where and how the system can persist changes to external systems.

Terminology

  • Orchestrator: the component that owns control flow (decides next action/tool call) and enforces policy.
  • Model-led: the model proposes next actions/tool calls within constraints enforced by the orchestrator.
Related links Related links
External baselines External baselines
Subscription

Unlock the full version and working files

This article is public. The subscription unlocks the protected workflows, full versions, and working files across Andy's AI Playbook.

How access works: sign in with your email first. If paid access is already active for this account, the site restores it. If not, the account page opens the PayPal checkout next.