Viewing profile — zaydmulani

[dead]

[dead]

[dead]

[dead]

Checked out mori — the governance layer for multi-agent writes is exactly the gap mnemo doesn't address yet. Good work on that.

[flagged]

[flagged]

[dead]

Would genuinely be interested to see it. link? The graph traversal approach seems underexplored compared to pure vector search.

Homebrew tap is on the roadmap. For now the fastest path on Mac is cargo install --path crates/mnemo-api or the Docker one liner. Will add a brew tap for v0.2.0.

Currently mnemo doesn't have automatic forgetting it's on the v0.2.0 roadmap. The mitigation right now is that retrieval scoring weights recency, so older chunks naturally rank low…

[flagged]

Done "Why mnemo" section added to the README with a comparison table. Short version: single Rust binary, zero cloud, petgraph knowledge graph with multi-hop traversal, scored retri…

[dead]

Different project — mnemon is a Python-based memory tool. mnemo is a Rust binary with a knowledge graph layer and REST API sidecar. Similar name, different approach.

Yes — cargo run -p mnemo-bench. Ships with 12 benchmarks. Full retrieval pipeline is ~4ms on debug build. Numbers are in the README performance table.

[dead]

[dead]

[dead]

Fair. The differentiator is the Rust single binary + petgraph knowledge graph. No Python runtime, no cloud, survives restarts. Built it because nothing local fit that profile.

BM25 is in my other project vecdb. mnemo's retrieval is graph-first — entity deduplication, multi-hop traversal, session-scoped scoring. Different tradeoff, not an oversight.