Part 9 of 15 · 1 min read
What the example does not do
About this example What the example does not do
- No real extractor or summariser. Both are patterns, so they are predictable and brittle (Part 3).
- Word overlap, not meaning. Recall of episodes and procedures works because the question repeats words from the record. Module 4 fixes this.
- Always includes all facts. Fine for six, impossible for six thousand.
- No expiry. "This week I am in Berlin" is a fact that should disappear on its own; it never does here.
- No conflicts between two trusted sources. If the user says one thing and a calendar says another, which wins? Here the user always wins by being the only trusted writer.
- One user, no isolation. A real service keeps each user's memory strictly apart; a bug here is a data leak between customers.
- No consent or privacy design. What is worth remembering, how long, and how the user sees it are product and legal questions that code cannot settle.
- The forgetting claim is narrow. One database file, checked by scanning its bytes on one filesystem.