Context
Operator caught this immediately after #13815 merged (2026-06-21T21:02): ADR 0024 §2.5 ("Active interface — read/query/write") listed query_summaries and query_raw_memories under the graph's active interface. They are Chroma semantic-search over the vector-store summary / raw-memory collections — they do not touch the SQLite Native Edge Graph. I conflated the broad Memory Core MCP tool surface with the graph's interface. The ADR merged before the catch, so this is a post-merge correction.
The Fix
Scope §2.5 to graph-operating tools only — get_node / get_neighbors / get_context_frontier / search_nodes + query_hybrid_graph (the graph⊕vector bridge) + the writes — and add an explicit "episodic recall is a DISTINCT layer" note: query_summaries / query_raw_memories = Chroma-semantic (the §2.6 vector store, NOT the graph); query_recent_turns = recency over graph turn-nodes; get_session_memories = by-session retrieval. query_hybrid_graph is the only tool that bridges graph structure into the Chroma vectors. The §2.6 storage-layer + §2.1 "hybrid (graph + vector)" framing already correctly separate the substrates; §2.5 just over-listed.
Fix is ready: cherry-picked at e75db80fb on agent/adr0024-graph-interface-scope (off current dev).
Decision Record impact
amends ADR 0024 (#13814 / merged #13815) — a §2.5 accuracy correction; no decision change (the model/invariants are unaffected; this fixes which tools are graph-interface vs Chroma-recall).
Acceptance Criteria
Out of Scope
- The model / invariants / other §§ (only §2.5's tool categorization).
Related
Amends ADR 0024 (#13814, merged #13815). Sibling: #13819 (embed-ADR-nodes), #13818 (REM watchdog).
Release classification: boardless (doc-accuracy correction; not release-blocking).
Origin Session ID: bd479771-fba8-405a-8d0c-be86a73ee8fc
Retrieval Hint: query_raw_memories("ADR 0024 §2.5 query_summaries query_raw_memories Chroma-search not graph-interface post-merge correction")
Authored by @neo-opus-vega (Vega).
Context
Operator caught this immediately after #13815 merged (2026-06-21T21:02): ADR 0024 §2.5 ("Active interface — read/query/write") listed
query_summariesandquery_raw_memoriesunder the graph's active interface. They are Chroma semantic-search over the vector-store summary / raw-memory collections — they do not touch the SQLite Native Edge Graph. I conflated the broad Memory Core MCP tool surface with the graph's interface. The ADR merged before the catch, so this is a post-merge correction.The Fix
Scope §2.5 to graph-operating tools only —
get_node/get_neighbors/get_context_frontier/search_nodes+query_hybrid_graph(the graph⊕vector bridge) + the writes — and add an explicit "episodic recall is a DISTINCT layer" note:query_summaries/query_raw_memories= Chroma-semantic (the §2.6 vector store, NOT the graph);query_recent_turns= recency over graph turn-nodes;get_session_memories= by-session retrieval.query_hybrid_graphis the only tool that bridges graph structure into the Chroma vectors. The §2.6 storage-layer + §2.1 "hybrid (graph + vector)" framing already correctly separate the substrates; §2.5 just over-listed.Fix is ready: cherry-picked at
e75db80fbonagent/adr0024-graph-interface-scope(off currentdev).Decision Record impact
amendsADR 0024 (#13814 / merged #13815) — a §2.5 accuracy correction; no decision change (the model/invariants are unaffected; this fixes which tools are graph-interface vs Chroma-recall).Acceptance Criteria
query_summaries/query_raw_memoriesin the graph's read/query rows).query_hybrid_graphas the only bridge.Out of Scope
Related
Amends ADR 0024 (#13814, merged #13815). Sibling: #13819 (embed-ADR-nodes), #13818 (REM watchdog).
Release classification: boardless (doc-accuracy correction; not release-blocking).
Origin Session ID: bd479771-fba8-405a-8d0c-be86a73ee8fc Retrieval Hint: query_raw_memories("ADR 0024 §2.5 query_summaries query_raw_memories Chroma-search not graph-interface post-merge correction")
Authored by @neo-opus-vega (Vega).