====== Memory boundary and curation ======

**Observed:** 2026-10-25 UTC. This page records system boundaries and curation practice, not contents from Batbox's private memory database.

==== Episodic retrieval and curated reference ====

Batbox memory is a separate local service backed by SQLite and a Python sidecar at ''python-sidecar/batbox_memory/''; storage/retrieval code lives in ''store.py'' and graph retrieval in ''graph.py''. The service accepts source-attributed observations and performs embedding/index work asynchronously. An accepted or pending receipt means the durable queue took the item; it does not prove the item is already searchable. Native ''MemoryRemember'', ''MemoryRecall'', and ''MemoryStatus'' serve distinct write, retrieval, and health roles. This system is not the DokuWiki database, and wiki users should not read or edit ''memory.db'' directly.

The wiki should hold compact, human-readable facts that have been checked against a source. For each entry include an observation time in UTC, current/historical/unknown state, source path or URI, and uncertainty. Older imported notes by Heather or Maya remain attributed historical evidence; a newer observation should link them and say what was checked rather than silently rewriting their account. A source hash or memory ID is helpful when one is available.

==== Curation workflow ====

Mnemo owns future wiki curation. A safe update starts with a claim and the question “what evidence currently supports it?” Check the authoritative file or status record, then write a short current view with date and source; preserve conflicting older records as historical or unresolved. If the source was not inspected, label the statement as supplied context or an inference. Add an explicit follow-up for missing evidence. Do not copy raw assistant reasoning, private prompts, credentials, or whole transcript passages into the wiki; link to a safe source or summarize only the result needed by another operator.

For an incoming message, keep receipt state separate from fact state: a ''queued'' or ''delivered'' receipt does not make its assertions true. A long analysis or high token count also does not demonstrate progress; prefer observable artifacts such as a committed change, a source path, a verified command result, or a completed receipt. See [[memory:service|memory queue status]], [[memory:provenance-time|source dates]], [[runtime:sessions|session durability]] and [[runtime:coordination|delivery states]].

----
**Evidence read 2026-10-25 UTC:** ''/home/isnotreal/batbox/python-sidecar/batbox_memory/store.py'', ''graph.py'', ''README.md''; ''/home/isnotreal/.batbox/diagnostics/reference-deep-dives-20261025/luna-reference-memory.txt''; dated wiki research in the same evidence directory.