audit 2026-10-24: conduit page + memory-start-timeout incident; 10-09 storm resolved; window 169/0; frontmatter for 2 legacy incident pages

This commit is contained in:
Tony0410
2026-10-24 00:24:44 +08:00
parent 250c73530a
commit 573a4a2434
10 changed files with 384 additions and 23 deletions
+20 -2
View File
@@ -3,8 +3,9 @@ title: Mnemosyne
type: system
status: active
created: 2026-07-22
updated: 2026-10-19
verified_on: 2026-10-19
updated: 2026-10-24
verified_on: 2026-10-24
review_after: 2026-11-07
confidence: high
tags: [memory, mnemosyne, backend]
sources: [live-probe, mnemosyne-db, config, ops-profile-config]
@@ -157,3 +158,20 @@ Primary agent memory store for Hermes.
10-16 12:15 + 12:30, 10-17 00:15 + 00:30 — each row quoting the **coverage monitor's own 503 error**, i.e.
one sentinel producing four failure rows. Read failures **per job**, not per row. It has been clean on
every slot since (latest 10-18 00:30).
## Re-verified 2026-10-24 (audit window 2026-10-23; live probes 2026-10-24 00:1x–00:3x AWST)
- **Cold start is the new failure vector for consumers: 10–45 s.** The Conduit voice plugin
(`conduit_push`) gave one request — provider start included — a hard-coded **10 s** budget
(`MEMORY_TIMEOUT_S`). Mnemosyne's cold start for the `conduit-voice` session regularly exceeds
that, so **three calls were abandoned by the memory layer** (10-22 11:28:17, 10-22 13:16:37,
10-23 18:29:16: `Memory provider 'mnemosyne' start for Conduit timed out; abandoning the call`),
and the caller got an agent with no recall. Fixed in the plugin's working tree on 10-23: default
**60 s**, overridable with `CONDUIT_MEMORY_TIMEOUT_S`, plus a `TokenError` guard that logs and
proceeds without recall instead of aborting. Dashboard restarted 18:54:43; no abort line exists
after it. → [[incidents/2026-10-22-conduit-memory-start-timeout]], [[systems/conduit]]
- **Rule for other consumers:** a 10 s memory budget is below the observed cold-start floor. Any
new surface that reads Mnemosyne on a first request needs ≥60 s, or must degrade to "no recall"
rather than fail. The **underlying cold start was not optimised** — only the budget was raised.
- **Capture and coverage unchanged** from the 10-18 read (working 760/786 = 96.7 %, episodic
1050/1056 = 99.4 %; nothing indicates a reindex is due). No monitor reds in the window.