← Back to architecture blueprints

Agentic AI Workflows: System Architectures & Design Patterns

September 2026

[Architecture][Whitepaper][Agentic AI][Control Loops][Multi-Agent]
Closed-Loop Agentic Control Latency Matrix

A rigorous architectural taxonomy dissecting the transition from open-loop stochastic generation to stateful, self-correcting agentic loops. Analyzes reflection architectures, schema-enforced tool execution, ReAct interleaving, DAG-based plan decomposition, and multi-agent consensus networks with mathematical formalizations and production failure modes.

Production Specification Matrix

  • System Version: v4.2 Production Verified
  • Execution Domain: Distributed Systems & Cognitive Control Loops
  • Operational Paradigms: Closed-Loop Discrete State Control, Dynamic Replanning

00. Foundational Concepts: Open-Loop vs. Closed-Loop Control

Traditional Large Language Model (LLM) serving follows an open-loop feed-forward pipeline:

$$\text{Output} \sim P(\text{Tokens} \mid \text{Context})$$

Given an input context, the model computes token probabilities and samples a single completion. Errors compound quadratically across multi-step execution paths.

Agentic workflows replace open-loop inference with closed-loop discrete control systems:

$$S_{t+1} = f_{\text{transition}}(S_t, A_t, O_t)$$ $$A_t = \pi_{\text{policy}}(S_t; \theta_{\text{LLM}})$$ $$O_t = E(A_t)$$

Where:

  • $S_t$ represents working memory, scratchpad state, and environment variables.
  • $A_t$ is the structured action (tool call, sub-query, code execution).
  • $O_t$ is the empirical observation returned by environment $E$.

01. The Reflection Pattern: Dual-Agent Evaluator-Critic Loops

The Reflection pattern decouples generation from quality assurance, addressing the fundamental limitation of single-pass auto-regressive decoding:

  • Generator ($\pi_{\text{gen}}$): Unconstrained generation focused on creative, analytical, or algorithmic synthesis given task objective $X$.
  • Evaluator / Critic ($\pi_{\text{eval}}$): Rubric-based assessment verifying factual grounding, edge-case coverage, and schema compliance.
  • State Revision Memory: Explicit diffs and structured feedback injected back into the Generator context until acceptance criteria are satisfied.

CRITICAL PRODUCTION FAILURE MODE:
Critique Saturation occurs when the generator and critic enter an infinite oscillating loop over subjective stylistic preferences. Systems must enforce bounded iteration limits (N <= 3) and monotonic convergence checks.


02. The Tool Use Pattern: Schema-Enforced Function Calling

Grounding probabilistic inference in deterministic compute and external API gateways:

  • Schema Enforcement: Pydantic models or JSON Schema specifications passed directly into the model context.
  • AST Parsing & Validation: Sandboxed validation verifying parameter syntax, types, and permissions prior to invocation.
  • Idempotency & Reversibility: State-altering tools must implement rollback mechanisms or require explicit human-in-the-loop authorization.

03. The ReAct Pattern: Interleaved Reasoning and Action

Coupling dynamic thought synthesis with environment feedback via persistent scratchpad memory:

  • Thought: Internal reasoning trace planning the next discrete step.
  • Action: Structured tool invocation or external query.
  • Observation: Deterministic output returned from the tool.

This loop prevents blind execution by forcing the model to evaluate the consequences of each intermediate state before deciding on subsequent operations.


04. The Planning Pattern: Directed Acyclic Graph (DAG) Execution

Decomposing complex strategic objectives into dependency graphs with dynamic replanning triggers:

  • Plan Decomposition: High-level objective mapped into discrete sub-tasks with explicit input/output contracts.
  • Topological Sorting: Independent sub-tasks executed concurrently across worker processes.
  • Dynamic Replanning: If node $N_i$ fails or yields unexpected output, the planner dynamically mutates downstream graph dependencies without restarting execution from scratch.

05. The Multi-Agent Collaboration Pattern: Hierarchical Topologies

Distributed specialization, message buses, and consensus aggregation across heterogeneous agents:

  • Supervisor-Worker Topologies: A lead supervisor agent delegates sub-tasks to specialized sub-agents and aggregates outputs.
  • Message Bus Architecture: Structured JSON-RPC or event channels enabling asynchronous communication between agents.
  • Consensus Protocols: Voting or debate mechanisms resolving contradictory viewpoints across specialist models.

06. Quantitative Architectural Matrix

Pattern Token Overhead Latency SLA Reliability Delta Cost Multiple
Single-Turn Baseline 1.0x (Baseline) 300 - 800 ms Baseline (Low) 1.0x
Reflection Loop 2.5x - 4.0x 3.0 - 8.0 s +34% Accuracy ~3.2x
Tool Use (RPC) 1.2x - 2.0x 1.0 - 4.0 s +62% Grounding ~1.5x
ReAct Pattern 3.0x - 6.0x 5.0 - 15.0 s +51% Success ~4.5x
Planning (DAG) 4.0x - 8.0x 8.0 - 25.0 s +68% Multi-Step ~6.0x
Multi-Agent Hierarchy 6.0x - 15.0x 15.0 - 45.0 s +74% Complex Synthesis ~10.5x

07. Production Hardening: Operational Guardrails

  • Step & Token Deadlines: Enforce a maximum step limit (MAX_STEPS = 10) and hard wall-clock timeout (TIMEOUT = 30s) to prevent unbounded token drain.
  • Loop & Oscillation Detection: Hash recent tool arguments and scratchpad traces to detect cyclic traps and break loops automatically.
  • Deterministic State Checkpoints: Snapshot working state before executing critical external mutations, enabling zero-loss recovery upon node failure.