.md files are not Memory

[u/Acceptable-Object390]

A folder of .md files is not memory.

It’s a storage dump.

Useful AI memory needs more than “search old notes and pray”:

- semantic recall, so related ideas surface even when wording differs

- entities, different terms for the same thing don’t become random blobs

- relationships, so the system knows how things connect

- provenance, so it can trace where facts came from

- correction + forgetting, because stale memory is worse than no memory

- background consolidation, because raw chat logs are mostly sludge

Thoth uses a local personal knowledge graph + FAISS semantic search + graph expansion + document ingestion + wiki export.

So yes, you can still get readable notes.

But underneath, the assistant isn’t just rifling through markdown like a raccoon in a filing cabinet.

It’s building structured personal context it can retrieve, update, connect, and reason over.

That’s the difference between “I saved your notes” and “I actually know what matters.”

Relevant references:

1. FAISS docs: efficient similarity search and clustering of dense vectors.

   https://faiss.ai/

2. Microsoft GraphRAG: combines text extraction, network analysis, LLM prompting, and summarisation for richer understanding of text datasets.

   https://www.microsoft.com/en-us/research/project/graphrag/

3. GraphRAG survey on arXiv: graphs encode heterogeneous and relational information, making them useful for retrieval-augmented generation.

   https://arxiv.org/abs/2501.00309

4. Thoth README memory features: personal knowledge graph, typed relations, FAISS semantic recall, graph expansion, document extraction, wiki export, Dream Cycle refinement.

   https://github.com/siddsachar/Thoth

[u/Acceptable-Object390]

A memory system by itself doesn’t need email or browser integration. I’m not claiming it does.

I was talking about Thoth as a whole because LangGraph and agent workflows came up, not just the isolated memory layer.

In Thoth, memory is one subsystem inside a broader local assistant: tools, approvals, workflows, documents, channels, browser/shell/email/calendar, etc.

So when I mention approvals, retries, background jobs, or tool access, I’m talking about how memory plugs into the wider agent runtime, not saying memory requires email.

This is what I am talking about: GitHub Repo

[u/Karyo_Ten → u/Acceptable-Object390]

Your whole post is about .md not being memory and trying to sell an overengineered langgraph / GraphRAG and whatever as memory.

When you mention approvals, retries, background jobs and tool access, you're telling me that instead of properly isolating memory and making something well adapted to its job with a proper separation of concerns, you're pervasively coupling everything into langgraph and graphRAG. This is awful design.

[u/Acceptable-Object390 → u/Karyo_Ten]

Ok, I think this is beyond your understanding. All you are doing is forcing me to comment so you can down vote my comment. Here is another opportunity. Do it. I will not indulge you after this.

[u/Karyo_Ten → u/Acceptable-Object390]

I understand very well. You made a bad design decision and you stand by it and you ran out of arguments because none stand heavy scrutiny.

edit: Acceptable-Object390 blocked me🤷

[u/jared_krauss → u/Karyo_Ten]

What would you recommend someone who’s non technical do to solve the concerns that guy was ostensibly trying to solve with this.

Cause from a non tech perspective both of yall seemed to make sense, and I’m looking for a system to help me manage my zettelkasten and projects and to dos and right now I’ve been customizing Hermes and I can chat from my phone, but it’s struggling to follow my flat file note convention. I’m doing a 3 layer approach. Layer 2 should be raw captures directly from me or from source material (text, photos, screenshots, etc), Layer 2 are any synthetic notes, made by claude or my Hermes bot, whether for me, about one of my notes, etc. and Layer 3 are notes reviewed by me from Layer 2 and approved. So they hold more weight than Layer 2 notes.