User Tools

Site Tools


memory:architecture

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

memory:architecture [2026/10/25 16:28] – Initial source-linked seed by three Luna research agents; assembled by operator operatormemory:architecture [2026/10/25 16:33] (current) – Record installed revision bridge and verified CPU retrieval; graph still pending operator
Line 7: Line 7:
 Recall uses HippoRAG when its graph is available and not being updated. Otherwise the service returns CPU vector retrieval and labels the backend cpu-vector; graph state is included on the fallback path. Always inspect the returned backend and source/date metadata. Status exposes aggregate queue states and errors, embedding and graph counts, worker health, and HippoRAG state. [[memory:queue-operations|Queue operations]] describes how to read it. Recall uses HippoRAG when its graph is available and not being updated. Otherwise the service returns CPU vector retrieval and labels the backend cpu-vector; graph state is included on the fallback path. Always inspect the returned backend and source/date metadata. Status exposes aggregate queue states and errors, embedding and graph counts, worker health, and HippoRAG state. [[memory:queue-operations|Queue operations]] describes how to read it.
  
-The working notepad is separate from durable memory: it carries current task state across requests and compaction, while the memory service is for persistent observations. Source review found automatic observation capture and task-specific recall in the autonomous path, but not a reliable semantic end-of-turn curator that turns every visible correction into a compact durable fact. Mnemo's curation remains a distinct editorial activity. Do not treat the wiki as automatically indexed: whether a deployed service scans these pages is not established by this source snapshot.+The working notepad is separate from durable memory: it carries current task state across requests and compaction, while the memory service is for persistent observations. Source review found automatic observation capture and task-specific recall in the autonomous path, but not a reliable semantic end-of-turn curator that turns every visible correction into a compact durable fact. Mnemo's curation remains a distinct editorial activity. A dedicated background bridge now enqueues current wiki revision snapshots once a minute, preserving exact source URLs and author/date metadata. Initial 27-page CPU readiness and recall were verified at 2026-10-25T16:32:11Z; HippoRAG indexing remained pending. A subsequent save needs its own queue/indexing receipt. See [[memory:wiki-sync]].
  
 **Sources checked 2026-10-25 UTC:** /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/README.md; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/__main__.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/store.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/graph.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/src/autonomous/Engine.cpp; /home/isnotreal/.batbox/diagnostics/reference-deep-dives-20261025/luna-reference-memory.txt. **Sources checked 2026-10-25 UTC:** /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/README.md; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/__main__.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/store.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/python-sidecar/batbox_memory/graph.py; /home/isnotreal/batbox-fixes/skill-discovery-20261025/src/autonomous/Engine.cpp; /home/isnotreal/.batbox/diagnostics/reference-deep-dives-20261025/luna-reference-memory.txt.
  
memory/architecture.1792945735.txt.gz · Last modified: by operator