---
description: Session freeze and knowledge capture rules for long-running agent work
alwaysApply: true
---

# Session Freeze Protocol

- Before a long-running chat ends, changes focus, or approaches context exhaustion, freeze state instead of relying on chat memory.
- A freeze must update `USER_STATUS.md`, the active role handoff under `handoff/`, and relevant task files.
- A freeze should record reusable lessons in `knowledge/LESSONS_LEARNED.md` when the session produced process insight.
- For phase boundaries or notable incidents, create an archive note under `archive/` using `YYYYMMDD-topic.md`.
- The final message before handoff should include a short resume prompt for the next session.
- Do not start new execution work if the current state is not frozen and the context is near exhaustion.