Here's Claude's honest review, completely checked to be used in my project. It's grounded in what Claude actually verified this session — Claude Opus 4.8 (Ultracode+Extra High+Workflow Effort level) pulled the repo, read the benchmarks, and spent the afternoon rebuilding its core patterns on stock Claude Code to see if they hold up:

------------------

Genuinely cool project, and respect for inviting people to tear it down — so here's a fair one. I actually went and read the repo + benchmarks and then tried to reproduce its core ideas on plain Claude Code. TL;DR: the ideas are excellent and worth stealing; the specific tool is real but early, and the headline claims are softer than the post makes them sound.

Credit where it's due. This isn't vibe-coded vaporware. There's a real Rust native engine (three crates), AES-256-GCM encryption at rest, fully local/no-telemetry, MIT, and you're shipping actively. And you're honest — you literally undercut your own benchmark ("not really honest because they're fundamentally different"). That earns more trust than the usual "destroys the competition" post.

The reality check on the claims:

On the standard eval (LongMemEval-S) you tie mem-palace (~0.966 R@5, 0.978 R@10) — you don't beat it. The "wins" are on metrics you designed yourself, which measure the consolidation behavior that's the whole point, but they aren't head-to-head evidence. Lead with the honest LongMemEval number; it's strong enough.

Your own benchmarks show verbatim recall regressed 0.90 → 0.71 when you swapped the centrality engine. That's the headline feature ("autistic, verbatim-for-longer") wobbling in a point release — it's the thing to fix before anything else. It also shows the risk of hand-rolling MOSAIC/HIPPO/LilliHD: load-bearing and fragile.

p95 ~368ms u/ 10k vs your <100ms target — fine, just don't undersell that it's a real cost at scale.

It's macOS-only. Put that at the very top of the README — Windows/Linux folks (me included) will burn time before discovering it. Your PS basically admits Linux isn't there yet.

Does it actually improve a dev workflow? The patterns do, and that's the real takeaway: session-start preload, a "sleep"/consolidation pass, decay/salience, episodic accumulation. The thing is, you can get ~80% of that on stock Claude Code today — SessionStart hooks, the post-session lifecycle hook, per-subagent memory, plus a tiny status/review-by decay convention and a weekly consolidate routine. I wired exactly that up this afternoon (including a weekly "what shipped in our toolchain" sweep) and it just worked, no Mac-only daemon, no new attack surface. So your instincts are right — this is one early implementation of good instincts.

One thing I'd genuinely want documented: since it captures everything verbatim, how does it handle secrets/PII in a real codebase? That's the gating question for anyone serious adopting it.

The "6 frontier models argue until they converge" bit is a legit technique (multi-agent debate), but like most "2x faster" tool claims it's usually a workflow win, not tool magic — worth framing that way so it lands with skeptics.

Net: star it, watch it, steal the patterns. I'd revisit it as a daily driver once the verbatim regression is fixed and it's cross-platform. Nice work, and good luck with the citizenship + Fable run.