Skip to content

spec: define policy-aware SQLite memory redesign#180

Merged
Aaronontheweb merged 3 commits into
devfrom
feature/memory-policy-graph-redesign
Mar 7, 2026
Merged

spec: define policy-aware SQLite memory redesign#180
Aaronontheweb merged 3 commits into
devfrom
feature/memory-policy-graph-redesign

Conversation

@Aaronontheweb

Copy link
Copy Markdown
Collaborator

Summary

  • replace the backend-centric memory design with a first-party SQLite structured memory architecture centered on anchors, documents, records, and policy-aware recall
  • define automatic pre-turn recall, checkpoint-driven background curation, rules-first candidate filtering, and parent-session ownership of durable memory writes
  • add migration, compatibility, success criteria, and local Ollama-based eval gates for validating the redesign before rollout

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.
@Aaronontheweb Aaronontheweb marked this pull request as ready for review March 7, 2026 20:06
@Aaronontheweb Aaronontheweb merged commit 2d699db into dev Mar 7, 2026
4 checks passed
@Aaronontheweb Aaronontheweb deleted the feature/memory-policy-graph-redesign branch March 7, 2026 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant