staying-on-mission

Mission drift is detected by comparing the current action diff against a written mission anchor file containing goals, success criteria, and non-goals to evaluate goal continuity and record a re-anchor, escalate, or stop decision.

A mission anchor is a written file like .nuclear/mission.md defining project goals, success criteria, and non-goals, used to evaluate ongoing actions and record structured decisions to re-anchor, escalate, or stop work.

You can check alignment by running a drift-check that compares the current action diff against your explicit mission anchor file, producing a clear decision to re-anchor, escalate, or stop based on goal continuity.

Yes, this workflow supports long-running tasks and multi-agent work where scope drifts or standards slip across code, docs, or planning contexts by enforcing a written anchor and recording structured decisions.

You need an explicit mission anchor file such as .nuclear/mission.md or a defined Mission anchor section, plus the current action diff, to reason about goal continuity and produce re-anchor, escalate, or stop decisions.

You escalate or stop when the current action diff shows the work deviates too far from the mission anchor's goals and non-goals to justify continuation, as determined by the drift-check evaluation process.