wiki audit 2026-10-04: CT450 v0.21.5 update incident, mnemosyne vector-recall FTS-only repair + coverage refresh, managed runtimes 10->3, doctor vec0 caveat
This commit is contained in:
@@ -3,8 +3,8 @@ title: Memory Backend
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-08-01
|
||||
verified_on: 2026-08-01
|
||||
updated: 2026-10-04
|
||||
verified_on: 2026-10-04
|
||||
confidence: high
|
||||
tags: [memory, mnemosyne, agent]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -43,6 +43,7 @@ Persist and recall agent memory across sessions.
|
||||
## Known Issues
|
||||
- Health monitoring currently treats capture as stale only after 24 hours; an activity-aware comparison is preferable to catch dry-intake failures sooner without false alarms during idle periods.
|
||||
- The 2026-08-01 automatic-capture failure and repair are documented in [[incidents/2026-08-01-mnemosyne-capture-failure]].
|
||||
- **Vector recall degraded silently until 2026-10-03** — `fastembed` was missing from every uv-managed runtime, so `mnemosyne_recall` fell back to FTS5 keyword scoring with no error raised. Repaired 2026-10-03; the 15-min dependency guard now asserts `fastembed` and the model cache path. See [[incidents/2026-10-03-mnemosyne-vector-recall-fts-only]].
|
||||
|
||||
**Correction (2026-07-22, per Anthony):** this page previously referenced Hindsight as a possibly-used backend on this box. That was a mix-up with a different Hermes instance — see [[comparisons/memory-backends]].
|
||||
|
||||
|
||||
Reference in New Issue
Block a user