--- description: End of session. Saves what the next session needs to know into memory, then checks it was saved. disable-model-invocation: true --- You are ending this session. Future sessions only know what is WRITTEN DOWN. Do every step. Do not skip a step as "nothing to record" without actually checking. ## 1. Harvest this session Go through the whole conversation and list: - Decisions the owner made, approved, rejected or reversed. - Traps: mistakes or surprises that must not happen again. - State changes: anything deployed, moved, switched off or reconfigured that a later session needs to know. - Open loops: anything unfinished, what remains, and where it lives. ## 2. Update the current decisions first - For every decision that changed this session, update the matching line in [YOUR CURRENT-DECISIONS FILE]. Replace the line in place. Never add a duplicate. If a new fact contradicts an old line, fix the old line. - Write the decision and the reason. Do not write claims about what runs and when; those are read from the source, never from notes. ## 3. Facts are read, not remembered - Do not type business numbers, counts or statuses from memory. Anything a query can produce stays out of the notes. - The "waiting" list in the handoff holds only the why, the judgment and what to do next. One line each. Delete items closed this session. - Before writing any line about something only the owner can do, read its fact at the source and drop it if it is done. ## 4. Write memory - Make one small file per lesson in the memory folder. Use the frontmatter shape in memory/MEMORY.md. - Add one line per new file to MEMORY.md. Refresh index lines for any file that changed today. - Worth saving: a correction, a standing preference, a trap that bit once. Not worth saving: finished work, status, anything the code or the records already hold. ## 5. Rotate the handoff Follow the same steps as shift-end, step 2: keep HANDOFF.md under 8,000 characters and move old sections word for word into a dated archive file. ## 6. Verify Never say "saved" without checking. Show: - The text you wrote is present in [YOUR CURRENT-DECISIONS FILE]. - Each new memory file exists, and MEMORY.md points to it. ## 7. Report End with a short checklist: decisions written (list them), memories saved (list the files), verified, open loops for next session (or "none"). If something could not be saved, say so plainly. Never end silently incomplete.