# 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.

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

## Definition

An agentic system combines one or more agents with deterministic software, tools, data, environments, policies, verification, evidence, and human decision rights. The system—not the model alone—is the correct unit for architecture, risk classification, evaluation, and accountability.

The system boundary is increasingly recognized, but product architectures and assurance patterns remain diverse.

## Why it matters

The adjective “agentic” describes where control flow is partly model-directed.

A useful design names which choices are dynamic, which effects are mechanically bounded, and which decisions remain human.

## System anatomy

- **Agent layer:** Model-directed planning and action.
- **Deterministic layer:** Software boundaries, transactions, limits, and enforcement.
- **Accountability layer:** Named owners, verifiers, and release authorities.



## Important distinctions

- **AI-enabled application:** An application may use a model without allowing it to choose a multi-step path or take actions.
- **AI agent:** The agent is one operating component; the agentic system includes every dependency and governing boundary.



## Implementation signals

- Draw the system boundary around every model, tool, identity, datastore, verifier, and human authority
- Evaluate end-to-end outcomes and side effects rather than model responses alone

## Failure modes

- Treating the model as the whole product
- Leaving vendor tools or human work outside the risk boundary



## 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 workflow](https://aisdlc.ai/agentic-engineering/agentic-workflow) — A model-enabled process whose major control path is defined in code, even when models perform individual steps.
- [Agentic engineering](https://aisdlc.ai/agentic-engineering/agentic-engineering) — The discipline of designing intent, context, memory, tools, execution, verification, control, and evidence so goal-directed agents can perform meaningful work while humans remain accountable.
- [Eval-driven development](https://aisdlc.ai/agentic-engineering/eval-driven-development) — An engineering loop that converts expected behavior and observed failures into repeatable evaluations combining deterministic checks, environment inspection, security testing, model graders, repeated trials, and human judgment.

## Sources and further study

- [Anthropic — Trustworthy agents in practice](https://www.anthropic.com/research/trustworthy-agents) — Describes a self-directed plan–act–observe–adjust loop and the engineering layers needed to make longer-horizon agents more trustworthy. **Use:** Primary definition. **Limitation:** This first-party synthesis describes design directions and failure surfaces; it is not a certification scheme or evidence that every described control is sufficient.
- [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.
- [NIST — Artificial Intelligence Risk Management Framework 1.0](https://www.nist.gov/itl/ai-risk-management-framework) — A consensus-based foundation for governing, mapping, measuring, and managing AI risk according to context, impact, and organizational priorities. **Use:** Standard or protocol. **Limitation:** A specification defines an interface or control pattern; conformance alone does not establish authorization, security, or fitness for a use case.

---

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.