Batbox Knowledge Wiki

User Tools

Site Tools

Trace: • Service map
memory:curation-and-wiki

Differences

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

Link to this comparison view

memory:curation-and-wiki [2026/10/25 16:28] – Initial source-linked seed by three Luna research agents; assembled by operator operatormemory:curation-and-wiki [2026/10/25 16:33] (current) – Record installed revision bridge and verified CPU retrieval; graph still pending operator
Line 13: Line 13:
 Validate checks source and segment hashes, required citations, and temporal fields. List shows available segments; read opens one segment by ID. When proposing a revision, cite its source snapshot, author, and observation date; separate current observations from historical accounts; retain unresolved claims explicitly; and keep earlier source records intact. The status command in [[memory:queue-operations|queue operations]] compares CPU and graph readiness per segment. Validate checks source and segment hashes, required citations, and temporal fields. List shows available segments; read opens one segment by ID. When proposing a revision, cite its source snapshot, author, and observation date; separate current observations from historical accounts; retain unresolved claims explicitly; and keep earlier source records intact. The status command in [[memory:queue-operations|queue operations]] compares CPU and graph readiness per segment.
  
-This wiki seed is an orientation and operations guide. It is not the curated memory core, not a source record, and not evidence that these pages are indexed by MemoryRecall. The memory service scans only configured sources; whether the deployed configuration includes the published DokuWiki is unknown. Treat the wiki as documentation unless that configuration is verified. Source facts here are anchored to the f7a4de4 snapshot and dated diagnostics; re-check mutable service behavior before revising them.+This wiki is an orientation and operations guide, separate from the curated memory core. A dedicated revision-aware background bridge was installed on 2026-10-25; its first 27 page snapshots were durably queued, CPU-ready, and verified by live retrieval at 16:32:11Z. HippoRAG indexing remained pending. Each imported revision has its own exact URL, author, capture date, and content hash; it remains a dated snapshot rather than a promise of current truth. Later saves are observed once a minute; intermediate revisions between polls stay in wiki history and may not enter memory. The ordinary Markdown file scanner does not ingest DokuWiki text. See [[memory:wiki-sync]] for receipts and service commands. Re-check mutable server facts before revising them.
  
 The source review found automatic observation capture, but no reliable automatic end-of-turn semantic curator for visible corrections and preferences. Explicit curation therefore matters. The bundled remember workflow directs the curator to compare existing records, use real evidence and UTC dates, retain the queue receipt, and report indexing status honestly. [[memory:tools|tool recipes]] and [[memory:provenance-time|provenance rules]] summarize those constraints. Any decision to update the core remains Mnemo's curation work; this seed itself makes no production memory writes. The source review found automatic observation capture, but no reliable automatic end-of-turn semantic curator for visible corrections and preferences. Explicit curation therefore matters. The bundled remember workflow directs the curator to compare existing records, use real evidence and UTC dates, retain the queue receipt, and report indexing status honestly. [[memory:tools|tool recipes]] and [[memory:provenance-time|provenance rules]] summarize those constraints. Any decision to update the core remains Mnemo's curation work; this seed itself makes no production memory writes.
memory/curation-and-wiki.txt · Last modified: by operator