Watch the idea
The concept
Think
Plan the next step
Tool
Search, write, call
Check
Did it actually finish?
Human gate
Before it leaves the building
An agent is a loop, not a soul
Think: plan the next step. Act: call a tool (search, calendar, code). Check: did the tool result actually answer the job? Repeat until a stop rule. That is a clerk with a checklist.
Tools without gates are accidents
A campus agent that can send mail, book rooms, or edit grades needs a human gate before anything leaves the building. Confidence is not permission. Stop rules belong in the prompt and in the code.
Start tiny
One job: office hours FAQ over the course handbook, with retrieval and a refuse path. Not an unsupervised registrar. Tiny, gated, measurable agents are how you learn the pattern before you scale it.
Worked example
The handbook bot
Student asks when the lab is due. Agent retrieves the syllabus span, answers with a citation, and stops. If the syllabus is silent, it says it does not know — it does not invent a midnight deadline.
Picture to keep
Campus bot loop
- 1Job: handbook only
- 2Retrieve + check
- 3Refuse if empty
