The write-manage-read loop

The single most useful framework in this whole folder is the way the "Practical Guide" characterizes memory. It is not just "store and retrieve." It is a three-phase loop:

• Write: new information enters memory. This includes observations, results, and reflections.
• Manage: memory is maintained over time. It is pruned, compressed, consolidated, and reconciled.
• Read: relevant memory is retrieved and injected into the context window when needed.

The author's central observation, drawn from seeing many real systems, is that most implementations get write and read right and completely neglect manage. They accumulate information without curation. The result is noise, contradiction, and a bloated context. Managing is the hard part, and it is where most systems struggle or fail outright.

This is worth emphasizing because it is counterintuitive. When people say "let's add memory," they almost always mean "let's store things and look them up." The loop says that is only two-thirds of the job, and the missing third (deciding what to keep, what to summarize, what to merge, when to let things age out) is exactly the part that determines whether memory helps or slowly rots.

The author describes handling the manage step, before more advanced tooling existed, with an explicit heuristic control policy: rules for what to store, what to summarize, when to escalate something to long-term memory, and when to let it age out. The point is not that those specific rules are ideal, but that being explicit about management forces you to confront the hard decisions instead of ignoring them.