# Agentic workflow

A model-enabled process whose major control path is defined in code, even when models perform individual steps.

technical-term · Foundations · foundational · Reviewed 2026-08-09

## Definition

An agentic workflow orchestrates models, tools, and checks through substantially predetermined branches, sequences, or routers. It can use planning or generation inside a step without delegating the overall process to an autonomous agent.

Workflow orchestration is established; the term is sometimes blurred with agents in marketing and product language.

## Why it matters

Workflows trade some flexibility for predictability, inspectability, and simpler testing.

Many enterprise problems need a workflow with one bounded agentic step—not a fully dynamic agent.

## System anatomy

- **Explicit control flow:** Code decides the major sequence and branches.
- **Model steps:** Models transform, classify, generate, or evaluate within bounded nodes.
- **Deterministic transitions:** Typed conditions move work between steps.



## Important distinctions

- **AI agent:** An agent dynamically chooses more of its process and tool use; a workflow follows code-defined control flow.
- **Traditional workflow:** An agentic workflow contains probabilistic model steps even if its topology remains fixed.



## Implementation signals

- Prefer workflows when paths and approvals are known
- Make probabilistic nodes explicit and independently testable

## Failure modes

- Calling every multi-step automation an agent
- Hiding model uncertainty behind a deterministic-looking diagram



## Related knowledge

- [AI agent](https://aisdlc.ai/agentic-engineering/ai-agent) — A goal-directed software system in which a model dynamically chooses steps and tools, observes results, updates working state, and continues until an exit condition or human handoff.
- [Agentic system](https://aisdlc.ai/agentic-engineering/agentic-system) — A software system that delegates some path selection or action choice to one or more model-driven agents within an engineered operating boundary.
- [Orchestrator or supervisor agent](https://aisdlc.ai/agentic-engineering/orchestrator-supervisor) — A coordinating component that decomposes work, routes tasks, monitors progress, and resolves or escalates outcomes across agents or tools.
- [Structured output](https://aisdlc.ai/agentic-engineering/structured-output) — Model output constrained to a declared machine-readable schema so software can parse and validate its shape.

## Sources and further study

- [Anthropic — Building effective agents](https://www.anthropic.com/engineering/building-effective-agents) — A foundational distinction between fixed, code-orchestrated workflows and systems in which a model dynamically directs its process and tool use. **Use:** Primary definition. **Limitation:** The workflow-versus-agent distinction is a useful architecture boundary, not a universal taxonomy or proof that autonomous execution is preferable.
- [OpenAI — A practical guide to building agents](https://openai.com/business/guides-and-resources/a-practical-guide-to-building-ai-agents/) — Defines a practical agent around a model, tools, instructions, and a run loop that continues until an exit condition is reached. **Use:** Primary definition. **Limitation:** The guide is first-party product guidance and a simplified starting architecture, not a complete regulated-enterprise control model.

---

This library synthesizes cited research, standards, official documentation, and clearly attributed practitioner perspectives. Maturity describes the state of a concept—not vendor endorsement, production readiness, or permission to deploy. Benchmarks and demonstrations do not replace use-case evaluation, governed controls, independent verification, or named human release authority.