Skip to content

Latest commit

 

History

History
74 lines (52 loc) · 3.22 KB

File metadata and controls

74 lines (52 loc) · 3.22 KB

MemPalace Roadmap

v3.1.1 — Stability Patch (this week)

Bug fixes and hardening merged to develop, releasing soon.

Merged:

  • Security hardening: input validation, KG threading locks, WAL permission fixes (#647)
  • MCP tools: drawer CRUD, paginated export, hook settings (#667)
  • Backend storage seam: ChromaDB abstraction layer enabling swappable backends (#413)
  • MCP ping health check for AnythingLLM compatibility (#600)
  • Windows reparse point crash fix (#558)
  • mempalace compress KeyError crash fix (#569)
  • Token count estimate fix (#609)
  • Mtime float precision fix preventing unnecessary re-mines (#610)

In review (merging this week):

  • Auto-repair BLOB seq_ids from chromadb 0.6→1.5 migration (#664)
  • Graph cache with write-invalidation (#661)
  • L1 importance pre-filter for large palaces (#660)
  • Windows Chinese/Unicode encoding fix (#631)
  • HNSW index bloat prevention — 441GB→433KB on large palaces (#346, pending rebase)
  • ~25 additional small bug fixes and platform compatibility patches

v4.0.0-alpha — Next Generation (this week)

The v4 alpha introduces three major capabilities: pluggable storage backends, local NLP processing, and improved retrieval quality.

Swappable Storage

ChromaDB remains the default, but v4 introduces a backend abstraction (shipped in #413) that enables drop-in replacements:

  • PostgreSQL backend with pg_sorted_heap support (#665) — for production deployments needing ACID guarantees, concurrent access, and standard backup/restore
  • LanceDB backend (#574) — for local-first deployments wanting multi-device sync without a database server
  • PalaceStore (#643) — bespoke storage layer purpose-built for MemPalace's access patterns (draft, evaluating)

Users choose their backend at init time. Existing ChromaDB palaces continue to work unchanged.

Local NLP

On-device natural language processing via local models (#507):

  • Entity extraction, relationship detection, and topic classification without external API calls
  • Feature-flagged and optional — falls back to existing heuristic extractors
  • Runs on consumer hardware (no GPU required, GPU-accelerated when available)

Improved Retrieval

  • Hybrid search: keyword text-match fallback when vector similarity misses exact terms (#662)
  • Stale index detection: automatic reconnection when the HNSW index changes on disk (#663)
  • Time-decay scoring: recent memories surface before older ones (#337)
  • Query sanitization: system prompt contamination mitigation already shipped in v3.1 (#385)

What's Not in v4 Alpha

These are under consideration for v4 stable or later:

  • Synapse advanced retrieval — MMR, pinned memory, query expansion (#596)
  • Multi-device sync (#575) — depends on LanceDB backend
  • Multilingual embedding support (#488, #442)
  • Qdrant vector search backend (#381)

Branch Model

main            ← tagged production releases
develop         ← active development (PRs merge here)
release/3.1     ← hotfixes for current stable (v3.1.x)
release/3.0     ← hotfixes for prior stable

Contributing

See CONTRIBUTING.md for guidelines. PRs should target develop. We review all contributions for correctness, security, and compatibility before merging.