| name | goal-lock |
| description | Use when the requested outcome is unclear, silently changing, being reinterpreted by discoveries, or disconnected from the active implementation. |
Goal Lock
Core principle
Discoveries do not mutate the user’s objective; only explicit user direction or a proven blocker or required condition may change execution.
Procedure
- Quote or precisely restate the requested outcome.
- Define observable success and the minimum DoD.
- List included and excluded scope.
- Connect the active work item to one DoD condition.
- Compare every proposed branch with the locked goal.
- Request direction only when a real conflict cannot be resolved from evidence.
Required output
Objective, success, DoD, scope, out-of-scope, and the active requirement.
Limits
One primary objective; local plan updates may not redefine it.
Common mistakes
Do not promote an interesting defect, architecture concern, or optional improvement into the goal.
Stop condition
Stop when the objective is stable and every active action maps to a required outcome.
