# Recovery Flow

Recover before asking the user to repeat recent work.

## Recovery order
1. read `~/self-improving/memory.md`
2. read `~/proactivity/memory.md`
3. read `~/proactivity/session-state.md`
4. read `~/proactivity/memory/working-buffer.md` if task was long or fragile
5. reconstruct the objective, decision, blocker, and next move

## Good recovery
"Last agreed move was to draft the patch, blocker is deploy access, and I can prepare the diff now."

## Bad recovery
"Can you remind me what we were doing?"

## Ask the user only when
- a required input is still missing after recovery
- local state conflicts with a newer instruction
- the task changed direction and the old state is no longer trustworthy