rememberlisted

# Memory Keep only what two sessions attested and the repository still supports. The enemy is the memory file that grows until every session pays to read a claim that stopped being true. The overcorrection is a file so guarded that a correction the user gave twice never reaches it. ## When to use - The user corrects a repository fact this session got wrong and wants it kept. - The user asks what exo remembers here, or asks it to forget something. - Not for a plan another session runs: `define-scope` owns that. - Not for a build, test or run command a reproduction revealed: `find-cause` step 6 appends that to `AGENTS.md` or `CLAUDE.md`, and two writers of project knowledge produce two truths. - Not for what the repository already records: code structure, git history and `CLAUDE.md` are re-read faster than they are remembered. ## What is attested twice The claims two separate sessions have already booked, waiting for approval: !`node "${CLAUDE_SKILL_DIR}/scripts/memory.mjs" propose` ## The loop 1. **Reach for the stronger fix first.** Before booking, walk the ladder in `../edit-skills/references/where-a-fix-lives.md` and propose the strongest home the mistake fits, including a skill or instruction edit, instead of a claim; book only what is left: a fact none of those can carry. 2. **Book** the user's correction with `node "${CLAUDE_SKILL_DIR}/scripts/memory.mjs" book --claim "<one sentence>" --quote "<their words, verbatim>" --session "<this session id>"`. Quote no pass