docs(readme): rewrite Semantic Memory section for v2 - #25
Merged
Conversation
The README still described the pre-v2 memory system (wrong table names, the dead 'prepend to message' enrichment, no namespaces/decay/pinning, stale consolidation). Rewrite it to match what shipped: namespace scoping, decay/reinforcement/pinning, the 250ms-budgeted auto-recall with a recalled-context chip, LLM-backed consolidation with concat fallback, versioned storage, and the new overview/pin endpoints.
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
1 participant
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.
The README's Semantic Memory section still described the pre-v2 system and, in places, was factually wrong after the v2 rebuild:
fragments.lance/consolidated.lancetables (nowfragments_v2/consolidated_v2+ versionedmeta.json)This rewrites that subsection to match what shipped in 0.3.0/0.3.1. Other CI layers (Deliberation, Capability Discovery, Shared Context) are unchanged. Bumps to 0.3.2 so the npm package page picks up the corrected README.