Compaction Survival

Save tokens by keeping the right state alive across compaction instead of re-deriving it after memory loss.

Goal

When a session is getting long, preserve only the working state that would be expensive to reconstruct.

What To Preserve

• current objective;
• active subtask list;
• key decisions and reversals;
• files changed or inspected deeply;
• unresolved errors and their current hypothesis;
• blockers, constraints, and pending verifications;
• exact artifact paths for large outputs or generated files.

What Not To Preserve