wiki: nightly audit 2026-11-05 window — network-map re-verified by live probe (9377=Camofox not Stratos, 8790/5174 gone, +9120/9222/7777/6767/8085/9900, full Tailscale Serve table, two dead routes 8769/9123); commit pending 11-04 stocktake re-verifications; log + skills-index
This commit is contained in:
@@ -3,8 +3,8 @@ title: "Mnemosyne Capture Pipeline Broken (Aug 18)"
|
||||
type: incident
|
||||
status: superseded
|
||||
created: 2026-08-18
|
||||
updated: 2026-10-12
|
||||
verified_on: 2026-10-12
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [memory, mnemosyne, hermes, incident, capture]
|
||||
sources: [mnemosyne-db, health-monitor, run_agent.py]
|
||||
@@ -68,6 +68,29 @@ embedding coverage **98.3 % working / 99.6 % episodic**, FTS aligned (`fts_worki
|
||||
The three guard conditions diagnosed below were never individually confirmed as the fix — the path resumed
|
||||
capturing and has captured through every window since.
|
||||
|
||||
### Re-verified 2026-11-04 — capture still healthy, and the counts have moved on
|
||||
|
||||
Live state of `~/.hermes/mnemosyne/data/mnemosyne.db` (the path in the Verification snippet above is still
|
||||
correct; note the DB is under `data/`, not the `~/.hermes/mnemosyne/*.db` glob path):
|
||||
|
||||
| Metric | 2026-10-12 (page) | 2026-11-04 (live) |
|
||||
|---|---|---|
|
||||
| `working_memory` | 786 | **970** |
|
||||
| `episodic_memory` | 1,056 | **1,146** |
|
||||
| `memoria_facts` | — | **446** |
|
||||
| `memory_embeddings` | — | **943** |
|
||||
| Working-memory vector coverage | 98.3 % | **98.6 %** (`vec_working` 956 / `working_memory` 970) |
|
||||
| Episodic vector coverage | 99.6 % | **100 %** (`vec_episodes` 1,146 / `episodic_memory` 1,146) |
|
||||
| `fts_working` | 786 | **970** — aligned with `working_memory` |
|
||||
| `fts_facts` | 876 | **927** (vs `memoria_facts` 446 — FTS indexes a superset) |
|
||||
| Last `working_memory` entry | 2026-10-11 | **2026-11-03 17:12:40** |
|
||||
|
||||
`mnemosyne stats` independently reports **Total 2,562 / Working 970 / Episodic 1,146**, and the `vec0` extension
|
||||
loads cleanly (`sqlite-vec` from the agent venv), confirming vector search is live rather than silently FTS-only.
|
||||
**Working-memory coverage is above the 95 % reindex threshold**, so no `mnemosyne reindex` was triggered by this
|
||||
audit. **Capture has continued to work without incident for a full month** — the original failure has not
|
||||
recurred.
|
||||
|
||||
**Caution for the next alarm:** the health monitor raised a false EXCEPTION on 2026-10-11 00:08 by comparing
|
||||
naive-UTC `created_at` against AWST `now` ("stalled 10.7 h" — real gap 2.7 h). Do not triage that as a repeat
|
||||
of this incident; see [[systems/mnemosyne]].
|
||||
|
||||
Reference in New Issue
Block a user