Part 10 of 15 · 1 min read
How to build it so it holds up
- Say what you remember, in which kind, and give each kind an update rule, because a fact stored the way an episode is stored comes back stale.
- Decide who may write, because untrusted text that can change memory can plant something that persists long after the page that carried it is gone.
- Store the source of every record, because a record you cannot audit for where it came from is a record you cannot later distrust.
- Keep history for facts only if you need audit, and know that history is also a copy to delete, because every place a value is kept is a place forgetting has to reach.
- Write a real forget: every version, every derived copy, checked at the level of the file's bytes, because a delete that only removes the current row leaves the rest of the data recoverable.
- List every place the data lives, because "forgotten" means nothing unless you can name every store, summary, log, backup and index it could still be sitting in.
- Measure extraction recall on paraphrases, because a rigid extractor fails silently on exactly the phrasing a real user is likely to use.
- Keep a searchable raw log as a fallback, under the same deletion rules as everything else, for what extraction misses.
- Let the user read and edit their memory, because a miss they can see costs a correction instead of a silent wrong answer.
- Plant defects in the store and the gate, including the defaults, because an untested default is where a safe design quietly becomes unsafe.