Home The signal Anatomy of an agent Reference architecture Risk-Tiers Guardrail stack Governance in action Best practices Standards and crosswalk Implementation From the field Roadmap Companion toolkit Straight answers Glossary References
02 · Core components

What an agent is made of

An agent is not one thing. It is nine parts that each fail in a different way. Naming them separately is what makes governance tractable, because every part gets its own owner, its own control and its own evidence.

AGENT nine parts C1 goal & task contract C2 reasoning loop C3 context C4 memory C5 tools & actions C7 policy enforcement C6 identity C8 evidence C9 human control
C1 Goal and task contract

The bounded objective the agent accepts, with its success criteria, its scope limits and its stop conditions written down before it runs.

Fails as goal hijack, scope creep, silent objective drift.

C2 Reasoning and planning loop

The model-driven cycle that decomposes the goal, picks the next action, reads the result and revises. This is where cost, latency and loop risk live.

Fails as infinite loops, runaway spend, plan hallucination.

C3 Context assembler

The component that decides what goes into the window on each turn: instructions, retrieved knowledge, tool schemas, prior state, and what gets compacted away.

Fails as context poisoning, stale grounding, token bloat.

C4 Memory

Working state within a task, plus durable memory across tasks. Both need a retention policy, a scope boundary and a way to correct or delete an entry.

Fails as memory poisoning, cross-tenant leakage, un-deletable personal data.

C5 Tools and actions

Every capability that touches the outside world: read APIs, write APIs, code execution, file access, payments. Each one is a separate permission and a separate blast radius.

Fails as tool misuse, excessive privilege, unexpected code execution.

C6 Identity and entitlement

A registered identity for the agent, the human or system accountable for it, and the credential it acts under. Delegated authority is explicit and time-bound.

Fails as privilege abuse, orphaned agents, confused-deputy attacks.

C7 Policy enforcement point

The runtime gate that sits between intent and action. It evaluates who is asking, what they are asking for, against which data, and either allows, blocks, redacts or escalates.

Fails as policy bypass, advisory-only controls, prompt-level enforcement.

C8 Observation and evidence

Structured traces of every step, decision, tool call and token, written to an append-only record that can answer "what did this agent do and why" months later.

Fails as unexplainable outcomes, failed audits, unreproducible incidents.

C9 Human control surface

Approve, pause, take over, roll back, shut down. If a person cannot do all five within seconds, the agent is not ready for anything that matters.

Fails as no kill switch, approval fatigue, trust exploitation.

The design rule that follows. Governance attaches to components, not to agents. An agent inherits its controls from the parts it uses. Add a write-capable tool and it inherits the approval requirement automatically, without a new review cycle.

Where would you start?

If you are standing up an agent platform, tightening the controls on one you already have, or preparing for an audit that now includes agents, I am happy to look at it with you.