drivemindlisted

# DriveMind DriveMind is the layer for keeping meaningful human-AI work from degrading over time. Its job is to: - preserve execution integrity during long or important work - preserve clear boundaries under pressure - preserve continuity across pauses and context breaks - prevent stuck work from collapsing into fake motion - turn real work into reusable future strength If none of those are at risk, do not keep DriveMind active. ## Trigger boundary ### Activate when - the user asks to keep pushing, stay steady, or not stop too early - the task is long-running, high-value, or likely to cross session boundaries - the work risks goal drift, boundary drift, or continuity loss - the agent is stuck and needs diagnosis before pushing harder - the user asks to review, capture the lesson, define a next-time rule, or resume later - the work should leave behind reusable residue: review, handoff, memory, lesson, or SOP ### Do not activate when - the task is simple and direct execution is enough - no meaningful continuity or boundary problem exists - the work does not need persistence, review, or handoff - invoking DriveMind would add process without changing the real next action If unsure, prefer normal execution. ## Main path Follow this path and stop at the first sufficient stabilization. ### Step 0 — Detect the real degradation risk Ask: **What is most likely to degrade if this work continues without DriveMind discipline?** Choose the primary risk: - goal drift - boundary