Feature

Keep the buildon the plan.

The drift gate notices when the work moves away from the plan you agreed, and asks before it goes further.

Pro
// the problem

What goes wrong

Scope grows one file at a timeYou asked for a pricing page. Twenty minutes later the AI has also reworked the navigation and renamed a folder. Each step looked small, so none of them got a question.
The diff hides the detourA big diff is hard to review. The extra changes are mixed in with the ones you wanted, and you approve them by accident.
// what adams does

What Adams does

Holds work to the agreed planOnce a plan exists, Adams compares new work against it instead of trusting the last message.
Stops and asks on a deviationWhen the work leaves the plan, you get a question: extend the plan, or go back. The AI does not decide alone.
Records the decisionIf you extend the plan, the change is written down, so the next session starts from the real plan.
// worked example

An example

A detour caught

Illustrative session. Wording differs by project.

~/project~/your-project · example
Also tidy the whole navigation while you are there
Not in the plan: navigation rework
1. Add it to the plan (adds 3 tasks)
2. Keep to the plan, note it for later (recommended)
✓ Kept to the plan, idea noted
// faq

Questions

Does it block every change?

No. It looks for work that leaves the agreed plan. Work inside the plan is not interrupted.

What if I want the change?

Say so. You extend the plan with a yes and the work continues.

Do I need a plan first?

Yes. The gate compares work to a plan, so a short spec or a blueprint comes first.

// related

Keep reading