Skip to content

v3.6.0 — ten-loop engine, scoped isolation, deterministic temporal planner

Choose a tag to compare

View all tags
@OnourImpram OnourImpram released this 25 Jul 18:37
· 17 commits to main since this release
v3.6.0
828ac47
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Memory you can inspect, now with scope isolation you can prove.

Added

  • mneme doctor --verify-isolation runs scope and redaction checks against an isolated temporary fixture, without reading or changing your vault.
  • mneme_checkpoint_list and mneme_working_set_load take an optional scope and fall back to the configured default.
  • A deterministic release-candidate benchmark gate reporting retrieval quality, latency, index build time, index size, memory, backend contribution, and ablations. LongMemEval and LoCoMo adapters validate against pinned official schemas.
  • Claude, Codex, and Antigravity plugin validators now run with repository integrity and package candidate checks.

Changed

  • All nine MCP schemas derive from the authoritative Zod contracts and are checked against runtime acceptance. Unknown fields stay accepted and discarded for compatibility.
  • Concrete scope reads fail closed against legacy unscoped FTS5 indexes and ask for a rebuild. Exact scope: "*" remains the only cross-scope read opt-in; durable writes reject it.
  • Turkish FTS5 retrieval preserves distinct I, i, U+0130, and U+0131 normalization through dual indexed forms.
  • Temporal queries apply valid time and transaction time through a deterministic planner. Supersession, contradiction, CCE checkpoints, KG staging, and Graphiti group identifiers are scope isolated.
  • Retrieval telemetry records attempted, succeeded, failed, and contributed backend states separately, with separate per-vault keyed HMAC query identifiers for Python and TypeScript.
  • RRF deduplicates canonical document paths, retains provenance and confidence, and gives the canonical AMBIGUOUS label precedence when any contributing backend reports ambiguity.
  • The release workflow publishes only from a tag push, consuming the exact bytes produced by one verified preflight job.

Availability

mneme-mcp-server@3.6.0 is on npm.

The PyPI distributions (mneme-core, mneme-cc-plugin, mneme-graph, mneme-code) are still at 3.5.0 for this tag: the GitHub account was renamed, which invalidated the PyPI trusted-publisher claims, and the MCP Registry entry likewise still points at the previous namespace. Both are being reissued. Until then, install from source or stay on 3.5.0 for the Python packages.

Verification

30 required checks green: CI across three operating systems on Node 22/24 and Python 3.11 through 3.14, CodeQL, six benchmarks (nDCG@5, latency, adaptive context, migration, head-to-head, compaction recall), and Neo4j knowledge-graph integration.

Assets 2
Loading