Why file/markdown memory breaks on provenance

>> Yep. Uh thank you for the great talk. Um just wanted to ask a question. So it seems like a common theme these days in uh memory systems is more filebased memory and wikis and knowledge bases and uh I'm just wondering have is Zep working on something like that and also uh could some of the ideas here be represented in that paradigm? >> Yeah. uh markdown suffers from provenence. File-based um file-based uh memory starts to break down with provenence. It's very difficult when you m mutate lines in a file to understand the lineage or the provenence of why those changes occurred. Um, not only that, but in multi- aent, multi-user, and multi-source scenarios, it can be very challenging to manage markdown files at scale. I think they work really well um for desktop usage. Uh, they sometimes work well in uh agentic use cases that are server based, not necessarily desktop or single user, single agent scenarios. Um but what we found is that it's um they just break down with the types of enterprise problems that we solving in particularly in particular provenence as an example. Does that answer your question?