diff --git a/log.md b/log.md index f772c3c..ecd97dd 100644 --- a/log.md +++ b/log.md @@ -2625,3 +2625,22 @@ A second read of the live DBs tightened three claims made in the entry above. Al Ledger precision as read at 00:5x: **2026-11-14: 167 rows — 166 `completed` / 0 `failed` / 1 `running`** (this audit, `cbfe434a3b5e`, 23:59:37); **2026-11-15 so far: 8 rows — 7 `completed` / 1 `failed`** (the monitor); deliveries 11-14 **4 / 4 `delivered`** (07:06 / 07:30 / 08:32 / 12:05). Pages also updated in this pass: [[incidents/2026-11-14-mnemosyne-capture-stall]] (delivery question closed, fleet line corrected), [[systems/mnemosyne]] (new ⚠ OPEN block at the head of *Known Issues*, frontmatter to 2026-11-15, and the naive-UTC trap note extended with the monitor's own raw-UTC alert text as a second occurrence of the same trap), [[systems/scheduled-tasks]] (new `### Open 2026-11-15` block under *Known Issues* + the monitor row in the disabled table annotated — **the threshold tests the *sign* of the capture delay, not its magnitude, which is why 12 h of a growing hole raised nothing**). +## 2026-11-15 01:0x — vault mirror sync + first drift measurement (same audit window) + +**Vault:** `/home/hermes/wiki` (its own git root; local-only — `git remote -v` empty, so commit, no push). Touched files were mirrored into **both** vault conventions (`agent-estate-wiki/` and `agent-estate-wiki/wiki/`): **14 writes, sha256 verified per file, all OK**; vault commit **`b7d7f18`**, tree clean afterwards. Note the previous run's claim that `/home/hermes/wiki` "does not exist" was **wrong** — the directory and its repo are present and were last synced by the 11-14 run (`b067b97`). + +**Pre-check first** (skill §8 / §12b: compare each existing vault copy against the **pre-edit** authoring blob, `16767ef`, never the current one): 12 of 14 targets were `stale-but-clean` (identical to that pre-edit blob) or genuinely new. **2 conflicts investigated rather than clobbered** — `infrastructure/docker-services.md` in **both** conventions was dated **2026-11-06**, i.e. older than the pre-edit blob (11-07), with an 18-line diff that was entirely removals/date regressions and no unique lines → proven stale, forward-synced. Reading: **no audit between 11-07 and 11-14 ever mirrored that page.** + +**Drift measured** (authoring HEAD vs vault, 136 tracked `*.md`), after this run's sync: + +| convention | match | older-revision | no-authoring-match | missing | +|---|---|---|---|---| +| `agent-estate-wiki/` | 68 | 12 | **0** | 52 | +| `agent-estate-wiki/wiki/` | 68 | 56 | **1** | 7 | + +Method: each "differing" copy was matched against the last **25 authoring revisions of its own path** — a match to an older revision is *stale-but-clean*, no match is an *orphan*. Every differing copy in the top-level convention is an older revision. **The missing/52 and missing/7 columns are the standing drift and are unchanged by this run** (skill §8: a full mirror pass is bigger than an audit's mandate — recorded, not attempted). + +⚠ **One orphan, and it is the reverse of the usual case — the vault holds content the authoring tree has never had.** +`agent-estate-wiki/wiki/incidents/2026-10-31-conduit-voice-local-mode-not-applying.md` is **238 lines** with the root cause evidenced (`/v1/pool`, controlled realtime sessions against the Mac socket, title "…**rejects `session.update` in every form**"). The authoring page has been **103 lines at every commit that ever touched it** (`0c826f2` 2026-11-01 00:30, `a0b3734` 04:48, HEAD), and `git log -S'/v1/pool'` finds **nothing** — that evidence never entered the authoring tree. Vault mtime **2026-11-01 02:56**, i.e. written **straight into the vault** ~2¼ h after the authoring commit and ~2 h before `a0b3734` ("fix the Quartz build (YAML title)") normalised the title. **Left untouched and not forward-synced** (§12b: investigate, never clobber). **This needs an owner decision:** either port the vault copy back into `/home/hermes/workspace/agent-estate-wiki` (keeping the Quartz-safe `title`) or declare the shorter authoring page canonical and record the vault copy as historical. Until then the two trees disagree about the Conduit local-voice-mode root cause. + +