From ba2b17e596f8c24030003d4be46249e7783b2c6d Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sat, 2 May 2026 12:02:53 +0100 Subject: [PATCH] Clarify compaction scratch cleanup --- AGENTS.md | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 60c7fc7..9eb235d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -86,13 +86,20 @@ When context pressure is clearly rising: When the user says to prepare for imminent compaction: -1. run `tools/ghostlight_prepare_compaction.py` before editing persistence +1. immediately write hot live context from memory into a new + `state/scratch-compaction-.md` file before reading files, running + status checks, or doing tidy persistence work +2. run `tools/ghostlight_prepare_compaction.py` before editing persistence surfaces -2. use its warnings as the checklist for map, handoff, scratch, evidence, and +3. use its warnings as the checklist for map, handoff, scratch, evidence, and git hygiene -3. update only the state that actually needs to change -4. run `tools/ghostlight_prepare_compaction.py` again after edits -5. fix errors, address warnings, and commit the completed persistence pass +4. update only the state that actually needs to change +5. after hot context has been folded into canonical persisted state, delete the + `state/scratch-compaction-.md` file so stale emergency memory does not + linger +6. run `tools/ghostlight_prepare_compaction.py` again after edits and scratch + cleanup +7. fix errors, address warnings, and commit the completed persistence pass unless the work is deliberately mid-surgery ## Operating Discipline