Holographic Memory as an optional backend for organizational knowledge

[dcondrey]

I'm working on Holographic Memory (HMS), an Apache-2.0 Rust library with Node bindings for local search and agent memory. I'd like to explore whether it could be a useful optional backend for your organizational knowledge prototype, particularly Knowledge Indexing and MCP Retrieval.

V0.6.4 supports BM25 search, hybrid search with supplied embeddings, metadata filters, source text offsets, and document replacement and deletion and the separate memory API supports supersession history and explicit forgetting, including a purge option with documented storage limits. Deleting an indexed document and forgetting derived facts remain separate operations.

I've also prepared integration examples for the prototype's current flat curated JSON. They preserve source metadata and content identifiers, keep stable identities separate across applications, and preview explicit deletion before applying it. Local tests cover provenance, Unicode curated-text byte offsets, replacement, scoped retrieva, and deletion across reopens and languages. This is not included in v0.6.4, does not yet support the nested model proposed in issue #8, and is not wired into your MCP server.

The proposed fit would preserve your collection and normalization pipeline, authoritative provenance, and existing MCP tools. HMS would hold a rebuildable index alongside the existing backend option.

Your indexer already replaces changed documents and supports pruning; the comparison would focus on retrieval and lifecycle behavior using the same corpus, chunks, embeddings, filters, and relevance judgments.

HMS also has vector-symbolic binding and bundling operations and associative memory.

Would a small optional-backend experiment be useful?