Connected Patterns: Understanding Agents Through Goals That Stay Put
“Drift is not a bug in one step. It is a slow leak in the run.”
Task drift is the most expensive kind of agent failure because it can look like progress while it quietly wastes days.
Premium Controller PickCompetitive PC ControllerRazer Wolverine V3 Pro 8K PC Wireless Gaming Controller
Razer Wolverine V3 Pro 8K PC Wireless Gaming Controller
A strong accessory angle for controller roundups, competitive input guides, and gaming setup pages that target PC players.
- 8000 Hz polling support
- Wireless plus wired play
- TMR thumbsticks
- 6 remappable buttons
- Carrying case included
Why it stands out
- Strong performance-driven accessory angle
- Customizable controls
- Fits premium controller roundups well
Things to know
- Premium price
- Controller preference is highly personal
An agent drifts when it starts with a goal and ends somewhere else, often for reasons that feel reasonable in the moment:
It follows a fascinating side thread.
It optimizes for being helpful instead of being correct.
It tries to anticipate what you “really mean” and changes scope.
It keeps collecting context because it never commits to a plan.
It solves a neighboring problem because it is easier to solve.
Drift is rarely loud. It is rarely dramatic. It is a slow, polite slide away from the target.
Preventing drift is less about making the model smarter and more about making the system more disciplined.
Drift inside the story of production
In production, drift is a reliability issue, a cost issue, and a safety issue.
| Drift outcome | Why it matters | Typical root cause |
|---|---|---|
| Wrong deliverable | The run “finishes” but misses the target | Goal not restated and tested |
| Budget blowup | The agent keeps exploring | No stop conditions or budgets |
| Safety boundary crossing | The agent expands scope | Constraints not persisted |
| Inconsistent behavior | Different runs diverge | No plan commitment or checkpoints |
| Low trust | Humans feel the agent is unpredictable | No run report with scope clarity |
If you treat drift as a minor annoyance, you will end up with an agent that cannot be trusted.
What causes drift
Drift comes from a few recurring pressures.
Ambiguity at the start
- Vague goals produce broad search and broad answers.
Missing success criteria
- The agent cannot recognize “done,” so it keeps going.
Weak constraints
- Boundaries are implied rather than explicit, so the agent expands them.
Overweighting novelty
- The agent follows new information even when it is irrelevant.
Memory bloat
- The run context becomes noisy, and the agent loses the thread.
Lack of verification
- Without checks, the agent cannot tell that it is off-target.
The fix is not one trick. It is a set of reinforcement loops that keep the goal active.
The simplest drift prevention: goal recitation with constraints
A small practice makes a big difference:
At the start of every major step, restate:
Goal.
Success criteria.
Constraints.
Next action.
This is not busywork. It is how you keep the run aligned across time.
When you checkpoint, you checkpoint those elements. When you resume, you restore them.
Plan commitment prevents “helpfulness drift”
Many agents drift because they keep rewriting the plan.
They discover something new, then they reorganize the task around it.
They feel uncertain, then they expand the scope to reduce uncertainty.
They try to be helpful, then they add features you did not ask for.
A plan commitment step prevents this.
A useful pattern:
The agent proposes a plan.
A human approves the plan, or the system auto-approves under low risk.
The agent executes the plan.
If new information forces a plan change, the agent must surface it explicitly and ask whether to re-scope.
This turns drift into a visible decision instead of a silent slide.
Success criteria as a stop rule, not a slogan
Success criteria need to be testable.
Weak success criteria
- “Provide a thorough answer.”
- “Improve reliability.”
- “Make it better.”
Strong success criteria
- “Produce a run report with a step timeline, evidence links, and a stop reason.”
- “Add idempotency keys to side-effect tool calls and verify by replaying a timeout scenario.”
- “Summarize a document into a state snapshot containing constraints, decisions, and open items.”
When success criteria are concrete, the agent can stop without guilt.
The constraint ledger
One of the most effective drift controls is a constraint ledger: a compact list of rules that the agent treats as binding.
A ledger might include:
- Allowed tools and prohibited tools.
- Approval requirements for certain actions.
- Budget caps and retry limits.
- Safety boundaries around data and communication.
- Output format requirements.
The key is persistence.
The ledger lives in the checkpointed state and is restated at step boundaries.
This prevents the classic drift where an agent “forgets” a boundary after a long run.
Drift detection gates
Preventing drift is easier when you detect it early.
A drift detection gate is a check that runs periodically:
Does the current plan still match the goal?
Are we still within scope?
Has the agent introduced a new objective?
Is the next action necessary for the stated success criteria?
If the gate fails, the agent pauses and escalates:
The run is drifting.
Here is where it drifted.
Here is the scope change.
Approve or correct.
That interruption is how you keep long runs sane.
Memory hygiene prevents narrative drift
As context grows, the agent is forced to compress. Poor compression causes drift.
Good memory hygiene looks like this:
Keep a compact state snapshot with:
- Goal, success criteria, constraints.
- Key decisions and commitments.
- Current plan and progress.
- Evidence pointers and open questions.
Move long transcripts, raw sources, and large tool outputs out of the working context into an evidence store.
When the agent needs something, it retrieves it deliberately rather than carrying everything all the time.
This keeps the “center of gravity” of the run stable.
A practical drift control table
| Control | What it prevents | When to use it |
|---|---|---|
| Goal and constraint recitation | Slow scope creep | Every major step |
| Plan commitment | Helpfulness drift | Early in the run, after discovery |
| Success criteria checks | Infinite exploration | Every step before continuing |
| Constraint ledger in state | Forgotten boundaries | Always, especially on resume |
| Drift detection gate | Silent re-scoping | On intervals, and before risky actions |
| Run reports with scope | Confusion after the fact | At stop and at major milestones |
These controls are not heavy. They are the minimum discipline needed for autonomy to stay aligned.
The role of human approvals in drift control
Approvals are not only for safety. They are also for alignment.
When a run reaches a fork, the agent should ask:
Proceed with the original scope.
Or expand scope to handle the new objective.
Humans are good at that decision. Agents are not, because agents tend to optimize for plausibility and completeness.
A small approval at the right moment can prevent hours of wasted work.
Drift is cost, not just correctness
Even when drift produces an output that is “useful,” it can be expensive.
It burns budget.
It burns time.
It burns reviewer attention.
It burns trust.
That is why drift controls belong in the harness, not as an afterthought.
The calm finish
A well-aligned run ends in a calm place:
The goal is met.
The scope is clear.
The evidence is recorded.
The risks are stated.
The stop reason is explicit.
That calm finish is what makes people hand the agent the next task.
Keep Exploring Reliable Agent Systems
• Production Agent Harness Design
https://ai-rng.com/production-agent-harness-design/
• Context Compaction for Long-Running Agents
https://ai-rng.com/context-compaction-for-long-running-agents/
• Multi-Step Planning Without Infinite Loops
https://ai-rng.com/multi-step-planning-without-infinite-loops/
• Agent Memory: What to Store and What to Recompute
https://ai-rng.com/agent-memory-what-to-store-and-what-to-recompute/
• Agent Checkpoints and Resumability
https://ai-rng.com/agent-checkpoints-and-resumability/
• Agent Error Taxonomy: The Failures You Will Actually See
https://ai-rng.com/agent-error-taxonomy-the-failures-you-will-actually-see/
A drift case study in one paragraph
Imagine an agent asked to “produce a deployment checklist for a new service.” It begins well, collecting required steps and linking to runbooks. Then it sees a note about monitoring and decides to design an entire monitoring architecture. It sees an alerting tool and decides to evaluate vendors. It finds a blog post about incident response and begins writing an incident handbook.
None of those topics are useless. The problem is that the agent quietly substituted “make everything complete” for “deliver the checklist.” The run ends with a large document and no checklist, and the requester still cannot deploy.
The fix is simple discipline:
Restate the target.
Define what done looks like.
Defer adjacent work into a separate backlog list.
The “parking lot” for helpful detours
Detours are not always bad. Sometimes the agent discovers something genuinely important. The goal is to capture it without letting it hijack the run.
A parking lot is a short section in state where the agent stores:
- Detours worth revisiting later.
- Questions that require human decision.
- Follow-up tasks that are valuable but out of scope.
This gives the agent permission to move on while preserving the value of discovery.
| Parking lot item | Why it belongs there | How it helps alignment |
|---|---|---|
| “Monitoring architecture needs review” | Important but separate | Prevents scope explosion |
| “Vendor choice affects alerting” | Requires human input | Avoids unilateral rescoping |
| “Incident handbook is missing” | Valuable long-term work | Keeps current run deliverable focused |
When you give the agent a place to put detours, it stops carrying them in working context, and drift becomes less likely.
Books by Drew Higgins
Prophecy and Its Meaning for Today
New Testament Prophecies and Their Meaning for Today
A focused study of New Testament prophecy and why it still matters for believers now.
