wiki audit 2026-11-21: session-scoped capture re-diagnosis (124 Pulse rows, ~57 uncaptured turns, gateway-restart hypothesis NOT proven); NEW page — first content_policy_blocked digest failures (gmail 08eb86f02d37 + freshrss ecc1fc13655a); watchdog streak 115->210 (single incident row); wiki-audit credit outage RESOLVED (two nights lost, 11-20 delivery suppressed); ledger corrections (4 unclosed health-monitor rows, not 5; audit incident closed 2026-11-20T01:19:13; 7 unclosed cron_incidents); skills-index regenerated 299 skills/67 cats; freshness 5 stale/132 fresh/3 no-date; Quartz rebuilt+deployed (879 files)
This commit is contained in:
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Mnemosyne capture stalled 105 h 52 m (2026-11-14 09:33 → 2026-11-18 19:25 AWST), then quiet again — four unclosed alerts
|
||||
title: Mnemosyne capture is dead for the long-running desktop DM session since 2026-11-13 13:10 AWST — ~57 uncaptured turns, four unclosed health-monitor alerts
|
||||
type: incident
|
||||
status: active
|
||||
created: 2026-11-15
|
||||
updated: 2026-11-20
|
||||
verified_on: 2026-11-20
|
||||
review_after: 2026-11-21
|
||||
updated: 2026-11-21
|
||||
verified_on: 2026-11-21
|
||||
review_after: 2026-11-22
|
||||
confidence: high
|
||||
tags: [mnemosyne, memory, capture, cron, health-monitor, desktop, pulse, incident, signature-fragmentation, freshness-gate]
|
||||
tags: [mnemosyne, memory, capture, cron, health-monitor, desktop, pulse, incident, session-scoped, freshness-gate]
|
||||
sources: [live-mnemosyne-db, live-cron-executions-db, live-cron-incidents, live-hermes-agent-log, live-mnemosyne-health-monitor-log, live-config-yaml, live-state-db, live-mnemosyne-freshness-gate-script]
|
||||
---
|
||||
|
||||
@@ -200,6 +200,47 @@ silent skip, see [[incidents/2026-11-18-wiki-audit-credit-outage]]), `96eb95_98a
|
||||
**Standing open question, restated:** not *"why did capture stop"* but **"why does the gate treat conversational
|
||||
silence as a fault?"** Until that is fixed, this page will keep re-opening on quiet days.
|
||||
|
||||
### Fifth read — 2026-11-21 00:0x–00:5x AWST: **the 11-20 conclusion above is withdrawn.** Capture is not "quiet", it is **dead for one specific session**, and the boundary is exact.
|
||||
|
||||
The 11-20 read counted **sessions** in `state.db`, found only three in the window, and concluded that every
|
||||
interactive session had been captured — so the alert was measuring conversational silence. **The wrong unit.**
|
||||
Capture is per *message*. Counted per message, the picture inverts:
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| Rows this session owns in `working_memory` | **124** (84 under the bare id `hermes_20261031_190813_95fbde`, 40 under `hermes_agent:main:local:dm:20261031_190813_95fbde`) |
|
||||
| Their span | **2026-10-31 11:09:16 → 2026-11-13 05:10:35 UTC = 2026-11-13 13:10:35 AWST** — then nothing |
|
||||
| Last *captured* turn in `state.db` | **2026-11-13 13:06:05 AWST** (Pulse report `pc36e5568`, row written 13:10:35) |
|
||||
| First *uncaptured* turn | **2026-11-13 13:21:00 AWST** (`Pulse delivery check p65be4717`) — and every turn since |
|
||||
| Uncaptured turns since | **~57** (11-13 19:21 → 11-21 00:00): Pulse reports, delivery checks, morning briefs, `[System: …]` notices |
|
||||
| Writes from this session after that boundary | **0** |
|
||||
|
||||
- **The break sits in a 15-minute gap, and the 11-13 13:14 gateway restart sits inside it.** Last captured turn
|
||||
13:06:05, first uncaptured 13:21:00; the 11-13/11-14 audit record documents a **gateway restart at 13:14**
|
||||
that day (the one that cleared the stale `TELEGRAM_HOME_CHANNEL_THREAD_ID`). *Leading hypothesis:* the
|
||||
restart left this session's capture watermark at-or-past its tip, so the session syncs nothing while new
|
||||
sessions start clean. **NOT PROVEN** — the oldest surviving `agent.log` file begins **2026-11-13 19:03:34**,
|
||||
so the 13:14 window has rotated out of the log horizon and no startup banner is recoverable.
|
||||
- **Capture is not globally dead — it works for *new* sessions.** The single write after that boundary,
|
||||
`2026-11-18 11:25:03 UTC = 19:25:03 AWST`, came from `hermes_20261118_191808_5c9e08`, a session created by a
|
||||
genuine prompt that evening. That is the **only** write in eight days.
|
||||
- **The health monitor already says exactly this,** in its own words: `ea79a2107e36` is failing with
|
||||
`STALE MEMORY PIPELINE: capture missed: user message`, `failure_streak = 4`. The gate was right; the 11-20
|
||||
reading of it was wrong.
|
||||
|
||||
**Corrected statement for the record:**
|
||||
|
||||
> **Mnemosyne has captured nothing from the desktop DM session `20261031_190813_95fbde` since 2026-11-13
|
||||
> 13:10:35 AWST — ~8 days and ~57 user-role turns — while capturing normally from sessions created after that
|
||||
> date.**
|
||||
|
||||
**Counters (11-21 read):** `working_memory` **1,131** / `episodic_memory` **1,250** — both **unchanged** from
|
||||
the 11-20 read; global silence since the last write **52 h 35 m**. **Unclosed incidents: 4 → 5**
|
||||
(`cbfe43_fa12cca1ad4b` auth, `alerted_at: None`; `96eb95_98ade422d195` script, still alerting 11-21 00:31:16 (00:16:15 at the first read);
|
||||
`ea79a2_f2be2db3bfce` 11-19 12:01:58; `ea79a2_aae4d914f3c9` 11-20 00:03:36; **new** `ea79a2_ace0f263e18a`
|
||||
11-21 00:03:12). **Next probe:** replay one Pulse-shaped turn into that session with the provider's debug
|
||||
logging on, and diff against a pre-11-13 capture in `agent.log`.
|
||||
|
||||
## Symptom (live reads, 2026-11-15 ~00:3x–00:4x AWST)
|
||||
|
||||
- Newest `working_memory.created_at`: **`2026-11-14 01:32:59`** — stored **UTC**, i.e.
|
||||
|
||||
Reference in New Issue
Block a user