Differences

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

--- memory:wiki-sync [2026/10/25 16:28] – Initial source-linked seed by three Luna research agents; assembled by operator operator
+++ memory:wiki-sync [2026/10/25 16:33] (current) – Document live revision bridge, durability, and current indexing evidence operator
@@ Line 1: / Line 1: @@
-====== Wiki pages and retrieval ======
+====== Wiki pages in memory ======
-**Status:** 2026-10-25 UTC. These DokuWiki pages document the working server and memory system. The ordinary memory file scanner reads Markdown files, not DokuWiki's .txt pages. A revision-aware background bridge is being installed; until its receipt exists, read the wiki directly and do not claim these pages are indexed.
+**Verified:** 2026-10-25T16:32:11Z. All 27 initial wiki pages were durably queued and CPU-vector ready; a real MemoryRecall request retrieved wiki:editing, wiki:api, and this page with exact revision URLs. None of those initial wiki snapshots had completed HippoRAG indexing at that observation. Graph catch-up remains separate.
-The bridge will enqueue dated page snapshots with an exact source URL, author, content hash, and wiki revision. Durable acceptance, CPU embeddings, and HippoRAG graph indexing remain separate stages. A saved wiki edit is not itself proof of any of those stages. Earlier wiki revisions remain in DokuWiki history; retrieval must respect their dates and verify a mutable server fact against its current source.
+==== Automatic background path ====
-Read [[wiki:editing]] for native CLI editing, [[wiki:api]] for exact revision lookups, and [[memory:queue-operations]] for memory queue diagnostics. The service's normal MemoryRemember and MemoryRecall tools remain available independently. Mnemo can arrange and improve pages; keep a small page for each tangible topic rather than growing one huge prompt.
+User timer ''batbox-wiki-memory.timer'' runs once a minute. Its oneshot service calls ''tools/wiki_memory_sync.py --once'', authenticates to standard DokuWiki JSON-RPC, and captures current pages in server, memory, runtime, and wiki namespaces plus root start/sidebar. Each new observed revision gets an immutable ID, SHA256, author/date metadata, and source URL of the form https://wiki.isnotreal.site/doku.php?id=memory:architecture&rev=REVISION_TIMESTAMP. The exact source bytes and payload enter a fsynced local outbox before POST /remember. A matching durable receipt advances accepted state. Lost responses retry the identical payload. Embedding and graph work remain in the existing memory background workers.
+The poller captures observed current revisions. Edits between polls remain in DokuWiki history and are not necessarily indexed. Every imported passage explicitly warns that it is a historical snapshot, current only when captured. If a previously seen page disappears from the authenticated list, an unavailable observation is added; it does not assert deletion versus a visibility change. Earlier memories remain historical because /remember has no invalidation endpoint. Verify live mutable facts and respect dates.
+==== Inspect and maintain ====
+<code bash>
+systemctl --user status batbox-wiki-memory.timer batbox-wiki-memory.service
+journalctl --user -u batbox-wiki-memory.service -n 20 --no-pager
+</code>
+Local durable state/receipts: ''~/.batbox/wiki-memory-sync/state.json''. Initial verification: ''~/.batbox/diagnostics/wiki-20261025/{indexing-receipt,recall-receipt}.json''. The bridge's accepted counter is queue acceptance, not graph completion. It makes no LLM generation calls. Its behavior passed 13 focused fake-HTTP tests, including response loss, provenance mismatch, locks, and disk failures.
+Sources: ''/home/isnotreal/batbox/tools/wiki_memory_sync.py'', ''tests/test_wiki_memory_sync.py'', and the two user unit files under ''~/.config/systemd/user/''. Read [[wiki:editing]], [[wiki:api]], and [[memory:queue-operations]] for related operations.