wiki: publish pending edits (2026-10-20)

This commit is contained in:
Tony0410
2026-10-20 18:38:11 +08:00
parent 667ab7f41d
commit fbd4f297eb
46 changed files with 1012 additions and 197 deletions
+15 -2
View File
@@ -3,8 +3,8 @@ title: Memory Backends
type: comparison
status: active
created: 2026-07-22
updated: 2026-08-12
verified_on: 2026-08-12
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [comparison, memory]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -30,6 +30,19 @@ The three archived scripts (`hindsight-watchdog.py.archived`, `hindsight_migrati
- Risk assessment flagged: schema mismatch, embedding drift, scope leakage, provenance loss, and one-way/no-rollback migration with no dry-run snapshot.
- **Verdict:** stay on Mnemosyne. Config verified `memory.provider: mnemosyne` (2026-08-12). No migration was performed.
> **Re-verified 2026-10-20 — Mnemosyne is still the only backend, and the OpenViking decision still
> holds.** `memory.provider: mnemosyne`, `memory_enabled: true`, `flush_min_turns: 6`,
> `memory_char_limit: 5000`, `user_char_limit: 3000`, `user_profile_enabled: true`,
> `nudge_interval: 10`; Mnemosyne sub-block `auto_sleep: true`, `default_scope: session`,
> `vector_type: int8`, `sleep_threshold: 50`, `profile_isolation: true`,
> `shared_surface_path: data/shared/mnemosyne.db`, `shared_surface_read: true`.
> No `openviking` key anywhere in `config.yaml`. No migration performed.
>
> **New since 2026-08-12:** `mnemosyne.skip_contexts: [cron, flush, subagent, background,
> skill_loop]` and `reflect.disabled_for_cron: true` — Mnemosyne capture is deliberately skipped
> in cron contexts, which is why scheduled jobs produce no working memories. See
> [[concepts/agent-memory]] and [[systems/mnemosyne]].
## Related
- [[systems/mnemosyne]]
- [[systems/memory-backend]]