Its not Markdown files in nosql. The context is extrapolated from a session and broken out into a record Postgres. You decide in a session what memory/context to save to the vault, the next time you ask about it, you will receive that (and refresh the AIs current context in the process).
Consider the non-developer type jobs out there who may be using AI, but the AI their team is using has no clue what the other person is doing or has done. This tool helps them bridge that gap. If one person has a pile of markdown files (not talking about skills, agents, etc) and the others do not, they won't get the same benefit. Instead of having hundreds of 'solutions' or 'learnings' in a file, you store it in the cloud and depending on their role/group assignment, its available to their AI client to recall later.
Consider the non-developer type jobs out there who may be using AI, but the AI their team is using has no clue what the other person is doing or has done. This tool helps them bridge that gap. If one person has a pile of markdown files (not talking about skills, agents, etc) and the others do not, they won't get the same benefit. Instead of having hundreds of 'solutions' or 'learnings' in a file, you store it in the cloud and depending on their role/group assignment, its available to their AI client to recall later.