Memory P5 — Sovereignty verification — no network in memory path #265
Reference in New Issue
Block a user
Delete Branch "burn/20260409-2105-memory-sovereignty"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #257
What
Adds
scripts/verify_memory_sovereignty.py— a CI verification script that checks the memory path has no network dependencies.How
Scans 8 memory-path files:
tools/memory_tool.py(MEMORY.md/USER.md store)hermes_state.py(SQLite session store)tools/session_search_tool.py(FTS5 session search)tools/graph_store.py(knowledge graph)tools/temporal_kg_tool.py(temporal KG tool)agent/temporal_knowledge_graph.py(temporal triple store)tools/skills_tool.py(skill listing/viewing)tools/skills_sync.py(bundled skill syncing)For each file, the script:
Exit codes: 0 = sovereign, 1 = violations found.
Known exclusions
tools/graph_store.py— uses GiteaClient for persistence; documented as separate from core memory pathtools/session_search_tool.py— uses LLM summarization; FTS5 search itself is localThese are in KNOWN_VIOLATIONS with justification and excluded from the gate.
Results
Core memory path (MEMORY.md, USER.md, SQLite state.db, temporal KG) is fully sovereign — local filesystem and SQLite only, no network dependencies.
Auto-approved: clean diff, no conflicts, mergeable.