Observe
What information can the system retrieve, and what evidence must be present before it acts?
An agent is more than an LLM with tools. Learn to decide when agency is warranted, define the boundaries of action, allocate authority, design closed-loop behavior, and create the evidence needed for deployment.
The useful question is not “Can the model do this?” It is “What observation, decision, action, verification, and stopping authority should the system receive?”
What information can the system retrieve, and what evidence must be present before it acts?
Which choices may be delegated, and which decisions stay with a named human owner?
What tools can change the world, how are side effects bounded, and how does the system verify the result?
The first sequence creates a reusable design record before the learner chooses LangGraph, an agent SDK, or any other orchestration layer.
Distinguish deterministic automation, an LLM workflow, and an agent from the structure of the decision—not from the marketing label.
Set goal, knowledge, tool, authority, cost, time, and failure boundaries.
Allocate permission to read, analyze, recommend, modify, commit, communicate, spend, and delete.
Connect observation, interpretation, choice, action, verification, escalation, and stopping.
Turn APIs into bounded capabilities with typed inputs, authorization, idempotency, and explicit failure behavior.
Separate working state, episodic memory, semantic knowledge, and authoritative external records.
Assemble the smallest, freshest, most decision-relevant context for each step of the agent loop.