An agent is not a tool list
A better representation is this: an agent is a work unit placed inside context, roles, artifacts, and feedback loops.
- Tools focus on capability
- Workflows focus on position
- Systems focus on feedback
Community / Jun 8, 2026
Export slides PDF-
-
02 / Resources
Three primary objects
A real workflow is not a chat trace. It is a set of objects that can be identified, assigned, checked, and reused.
1
Context
Goals, sources, constraints, decisions, and current state.
2
Role
Reader, Planner, Reviewer, and Writer are work boundaries.
3
Artifact
A document, task, judgment, code change, or reusable record.
-
03 / Flow
How one collaboration flows
Work is not a single exchange but a loop you can run again: goals go in, judgment comes back.
Input
Set the goal
Name what to solve and where the edges are.
Context
Gather context
Hand the agent the material, limits, and past decisions.
Run
Run and record
Run the tools and produce a checkable artifact.
Feedback
Write judgment back
Human trade-offs become the next round's context.
-
04 / Doer vs Tutor
The Doer / Tutor boundary
The same agent behavior can help you form a mental model, or let you bypass one.
Doer
Hands over the answer
It removes search, but also removes understanding.
Tutor
Provides scaffolding
It lowers extraneous load while leaving judgment to you.