---
title: "Comment by Evelyn Wyatt on \"Session memory is not project memory. It fixes the same complaint.\" | Hashnode"
description: "The distinction also makes me think about how information should move between the two layers. Not everything an agent learns during a session deserves to become"
url: "https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586/comment/6ab4f87b358512f172e0099c"
---

[Discussion](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586)

Comment [Session memory is not project memory. It fixes the same complaint.](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586)

[Evelyn Wyatt](https://hashnode.com/@Evelynwyatt)

[Sep 24](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586/comment/6ab4f87b358512f172e0099c)

The distinction also makes me think about how information should move between the two layers. Not everything an agent learns during a session deserves to become project memory. A temporary workaround, one-off debugging observation, and an architectural decision have very different lifetimes. A useful pattern could be to treat promotion into project memory as an explicit step: the agent identifies a finding, captures the evidence and scope, and only then proposes it as durable project knowledge. That would reduce the risk of turning every session observation into repository noise while still making important reasoning available to future sessions and teammates.

[Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner)

[Sep 24](https://hashnode.com/posts/session-memory-is-not-project-memory-it-fixes-the-same-complaint/6ab3ae06ab5703ad22d98586/comment/6ab4f87b358512f172e0099c#reply-6ab4fd16401243a8d23820f8)

I like that framing a lot - especially the idea of a durability threshold between session observations and project knowledge.

If you ever feel like exploring this further, contributions and discussions are very welcome here:

[github.com/oliver-zehentleitner/keep-the-why](https://github.com/oliver-zehentleitner/keep-the-why)

This is exactly the kind of edge case I want the project to get better at.
