Add Formative Memory to Memory and Context Systems#88
Open
jarimustonen wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding Formative Memory to the Memory and Context Systems section.
openclaw plugins install formative-memoryWhat it is
A biologically-inspired memory plugin for OpenClaw. Pre-response auto-recall (hybrid BM25 + embedding, strength-weighted, one-hop association expansion), post-response provenance-based reinforcement that only strengthens memories that actually influenced the reply, and a nightly consolidation ("sleep") loop that decays, prunes, and LLM-merges memories. All mutation is deferred to consolidation so live chat stays read-only.
Single-file SQLite + FTS5 + sqlite-vec — no external services. Content-addressed (SHA-256) memory objects make duplicates structurally impossible. Memories can carry temporal states (future/present/past) that shift automatically.
Sits in the same neighborhood as the existing entries (mem0, memU, MemOS, MoltBrain, supermemory, qmd) but differs mainly in the provenance-based reinforcement loop and the deferred-mutation architecture.
Happy to adjust wording.