Part 8 of 11 · 2 min read
Goal setting and monitoring: common mistakes
Common mistakes, and what the example does not do.
Mistakes that let an agent run past "done"
- Treating "done" as proof.
- A budget with no escalation path, so every hard task ends as a timeout.
- Vague success criteria ("good", "complete"), which no verifier can check.
- The same model, prompt and context grading its own work.
- A stall detector with no measure of progress (it counts steps, not subgoals).
- A stall threshold chosen by feel rather than from traces.
- No cap on replans, so the agent is replanned forever.
- Not testing the failure paths with impossible and looping tasks.
What the example does not do
About this example What the example does not do
- No real agent. The over-claim, loop and drift rates are assumptions and real ones depend on model, task and prompt.
- Binary progress. Real progress is fuzzy; a "new subgoal" signal may itself be noisy.
- A perfect progress signal. The monitor sees subgoal completion exactly; a real monitor infers it.
- A fixed budget rather than one scaled to the task's value.
- No human in the loop. Escalation just stops the run; module 8 covers approval and handover.
- Optional real-agent experiment: run an agent on 50 tasks with 10 known to be impossible, log claims, verifier verdicts and idle steps, and compute false completions and wrong escalations for two thresholds.
Check yourself
An agent says "done" and the run stops. How do you know it is done?
Show answer
A claim of done is a hypothesis. Something other than the agent has to check it, such as tests, a verifier or a person.
For the curious A budget is a limit, not a goal
In the simulation, an agent allowed to declare itself done reported false completion on 40 percent of tasks; a verifier cut that to 0.9 percent. A budget alone stops runaway cost but cannot tell finished work from unfinished work. A stall detector that replans and then escalates handled the impossible tasks (15 percent of them), at the price of 7.5 percent wrongly escalated.
What you will use daily at work
| Practice | What it looks like |
|---|---|
| Success criteria something else can check | Tests passing, a schema valid, a person approving. |
| Limits on steps, cost and time | So a stuck run ends. |
| An escalation path | What happens when the task cannot be done. |