spec: define policy-aware SQLite memory redesign#180
Merged
Conversation
Replace backend-centric memory with a first-party SQLite architecture so recall, curation, and privacy policy can be evaluated locally and behave predictably across sessions.
Assume a greenfield SQLite-first rollout, clarify when explicit memory tools should be used, and add prompt guidance plus a populated knowledge graph example to the redesign.
Clarify which sub-agent and skill-system issues block the memory work, what should be pulled forward, and what follow-up implementation issues should be split out.
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
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.
Summary