| the problem you are addressing is interesting, but given this is NOT an OSS I found the post a bit difficult to evaluate because the core mechanics of the product are not very clear. You provide a lot of implementation details (authentication providers, database choices, frontend stack, etc.), but those are quite unrelevant to understand your tool. The key questions for a memory systems to me are: - What exactly is a "memory" or "context record" in ContextVault? - How is information added, updated, or removed over time? - How does retrieval work (vector search, ranking, rules, something else)? - How do you handle stale information, contradictions, or superseded knowledge? - What makes this different from a shared RAG knowledge base or a document store with MCP access? A few concrete examples or an architecture overview would probably make the product much easier to understand. For example, showing a before/after workflow of an agent using ContextVault would help clarify where the intelligence of the system actually is. Cheers |