The distinction between remembering what happened, where the project is, and why a decision was made is probably the most useful way I’ve seen to think about agent memory.

I also liked the emphasis on the quality of what gets written rather than simply having a bigger memory store. A huge collection of transcripts isn’t very helpful if an agent still can’t understand which decisions are actually important.

The idea of keeping architectural rationale alongside the code in Git feels especially practical for teams, since it makes the “why” reviewable and versioned just like the code itself. Great read!