Skip to content

Memory Genome Engine v0.1.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 28 Jun 18:17
v0.1.2
35ad873

Memory Genome Engine v0.1.2 strengthens retrieval quality, failure recovery, and agent-facing recall controls while keeping the existing binary store format and hot -> checkpoint -> seal -> recall lifecycle.

Highlights

  • Added global lexical rank fusion for more accurate sealed-memory ordering.
  • Enforced recall output budgets consistently across focused, broad, and full-scope workflows.
  • Added the optional min_score recall floor to CLI, MCP, Python, and TypeScript integrations. Defaults remain unchanged.
  • Added rollback for incomplete seal transactions so failed sealing does not leave partially committed catalog/index state.
  • Exposed derived lexical-index diagnostics for validation and performance investigation.
  • Clarified one-command setup for Codex, Claude Code, Cursor, and generic MCP hosts.
  • Raised the additive integration schema contract to version 4.

Compatibility

  • No storage migration is required from v0.1.1.
  • Existing recall behavior is preserved unless min_score is explicitly provided.
  • Product archives contain only mge, mge-mcp-server, licenses, and user documentation. Development benchmark binaries are not distributed.

Verification

  • 203 workspace tests and 20 retrieval-evaluation tests passed.
  • Strict clippy, rustfmt, rustdoc, and Rust 1.95 MSRV checks passed.
  • Windows and Linux release archives were installed and exercised through plain/encrypted recall, checkpoint, seal, deep validation, wrong-key rejection, and MCP workflows.
  • macOS Intel and Apple Silicon archives were built and installer-smoked on GitHub-hosted macOS runners; local interactive macOS verification remains community feedback work.
  • All attached archives are covered by SHA256SUMS.

Retrieval evidence

On the repository's deterministic evaluation corpus:

  • hot focused hit/recall: 0.994 / 0.994
  • repeated sealed focused hit/recall: 1.000 / 1.000
  • repeated sealed broad hit/recall: 1.000 / 1.000

These numbers describe the included workload, not universal quality or a cross-project comparison.

Full changelog: v0.1.1...v0.1.2

Contact

For commercial integration, support, collaboration, and partnership inquiries:

Email   Telegram   GitHub repository

Assets 7
Loading