-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Hi Eric! 👋
I came across memspan and got curious, the philosophy of keeping memories portable, file-based, and user-controlled is exactly the kind of thing I've been thinking a lot about lately.
I've been working on a project called PAM (Portable AI Memory), an open specification that defines a standardized schema for AI memory files, identity, episodic memories, preferences, and so on. The core goal is for different tools to be able to read and write memories in the same format, without proprietary structures locking users in.
Repository: https://github.com/portable-ai-memory/portable-ai-memory
While exploring memspan, I noticed that you yourself identify in the README a pain point that PAM is trying to address directly:
"No integration: Doesn't integrate with other memory systems (though this is a possible near-term direction)"
Both projects seem to tackle complementary sides of the same problem: memspan solves the workflow of extracting, organizing, and loading context and PAM tries to solve the schema layer of the files themselves, precisely to enable that kind of integration between systems.
If you have a few minutes, I'd be really happy if you could take a look at the spec and share your thoughts, agreements, criticism, or whether you feel the scopes are more distinct than they appear. Any perspective would be valuable.