audit 2026-10-25: third consecutive clean cron day; new incident (agent refused 3 Conduit call requests); correct 10-22 memory-fix evidence; conduit 0.69.0/f000bf0

This commit is contained in:
Tony0410
2026-10-25 00:16:26 +08:00
parent ec69d107ae
commit 3271ff12a5
7 changed files with 296 additions and 46 deletions
+64 -28
View File
@@ -3,12 +3,12 @@ title: Conduit
type: system
status: active
created: 2026-10-24
updated: 2026-10-24
verified_on: 2026-10-24
review_after: 2026-11-07
updated: 2026-10-25
verified_on: 2026-10-25
review_after: 2026-11-08
confidence: high
tags: [conduit, plugin, phone, iphone, push, voice, memory]
sources: [live-probe, plugin-tree, live-sqlite-conduit, live-log, session-20261023_182601]
tags: [conduit, plugin, phone, iphone, push, voice, memory, tool-calling]
sources: [live-probe, plugin-tree, live-sqlite-conduit, live-sqlite-cron, live-log, session-20261024_125329]
---
# Conduit
@@ -23,12 +23,16 @@ Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[syste
## Where it lives
- **Plugin tree:** `/home/hermes/.hermes/plugins/conduit_push`
- **Version:** `0.64.0` (`manifest_version: 1`), git HEAD `eaa14be` — *“Pulse: mark follow-up cards
done, by hand or after Do it (0.64.0) (#323)”*
- **Version:** `0.69.0` (`plugin.yaml` and `dashboard/manifest.json`), git HEAD `f000bf0` —
*“Pulse: list candidates, decide in code, journal them (#337)”*. **22 commits on from the
`0.64.0` / `eaa14be` recorded at the 2026-10-24 audit** (upstream `#324`–`#338`: Pulse
cards/decisions/journal, a Live Activity messaging tool, contact cards, a self-update gateway
restart, `channels.yaml`, App Store builds following the archived plugin version).
- **Upstream:** `https://github.com/kaishi00/hermes-conduit-notifier.git` (origin, fetch+push)
- ⚠ **The working tree carries an uncommitted local patch** (`M dashboard/plugin_api.py`, the
memory-timeout fix in [[incidents/2026-10-22-conduit-memory-start-timeout]]). A plugin update
that resets the tree drops it.
- ⚠ **The working tree still carries the uncommitted local patch** (`M dashboard/plugin_api.py`, the
memory-timeout fix in [[incidents/2026-10-22-conduit-memory-start-timeout]]) — now **five releases
behind HEAD** (`0.64.0` → `0.69.0`), so the chance a plugin update resets the tree and drops it is
rising, not falling.
- **Skills shipped with the plugin** (4, under `plugins/conduit_push/skills/`): `calling-the-user`,
`reading-health-data`, `using-calendar`, `using-location`.
- **Data stores** (`~/.hermes/`): `conduit-health.sqlite3`, `conduit-location.sqlite3`,
@@ -36,22 +40,46 @@ Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[syste
installation id / relay url / e2e — **no values recorded here**), `conduit-calls.json`,
`conduit-settings.json`, `conduit-present.json`, `conduit-desktop-views.json`.
## Current state (verified 2026-10-24 00:1x AWST)
- **Dashboard gateway:** listening on `0.0.0.0:9119`; process started **2026-10-23 18:54:43** (this
start picked up the memory-timeout patch).
- **Device:** one registered — **iPhone, app version `2.0.0`**, features
`chat-cards`, `info-cards`, `live-cards`, `maps-navigate`, `media-cards`, `show-cards`
(last seen 2026-10-23 19:02:16). No other device is registered.
## Current state (verified 2026-10-25 00:2x–00:5x AWST)
- **Dashboard gateway:** listening on `0.0.0.0:9119`; process started **2026-10-23 18:54:43** and
**not restarted since** — so it is still the process that picked up the memory-timeout patch, and
the `0.64.0` → `0.69.0` upstream commits are **not** live.
- **Device:** one registered — **iPhone** (`id 70aa63f3…`, `kid c24e8215…`), app version `2.0.0`,
features `chat-cards`, `info-cards`, `live-cards`, `maps-navigate`, `media-cards`, `show-cards`;
tz `Australia/Perth`; sharing window 2026-10-16 → 2027-04-22. Paired **2026-10-22 12:54:39**.
`last_seen` / `last_sent` / `last_contact` all read **2026-10-23 19:10:30 AWST** (~29 h stale at
this audit) while health rows kept arriving until **2026-10-24 09:59:59** and window rollups were
recomputed at **13:56:35** — so those three fields track *phone-status* contact, not data flow.
(The 10-24 page recorded 19:02:16 from the same store; the epoch reads 19:10:35.)
- **Call settings:** `enabled`, `when_asked`, `decides`, `alerts` all true; rate limits
`min_gap_s 120` / `per_hour 6` / `per_day 20`; `avoid_unknown_place` false.
- **Recent calls:** two call sessions closed cleanly on **2026-10-24 00:03:23** and
**00:06:57** (both `outcome: done`, `conduit-calls.json` written 00:06:57) — the first
evidence after the memory-timeout fix.
- **Data volume:** `conduit-health.sqlite3` is **561.7 MB** (WAL 6.1 MB) holding
**1,501,165 `events`** rows across **308 `buckets`** / **62 `windows`** for its single device;
`conduit-location.sqlite3` 80 KB; `conduit-phone.sqlite3` 284 KB. **No retention or
compaction has been observed** — the health store has grown from card/health ingestion alone
and is worth watching against the CT460 disk budget.
- **Recent calls — none.** `conduit-calls.json → history` is **empty**: no call has been recorded
since the memory-timeout fix landed, so that fix still has **no positive evidence** behind it. The
“two call sessions closed cleanly 00:03:23 / 00:06:57” claim previously on this page was a **false
positive** — those `ends` entries are the two **cron** sessions of that night, and `ends` records
any turn-end that fires a watch, not calls →
[[incidents/2026-10-24-conduit-call-request-refused]].
- **Data volume (2026-10-25 00:2x):** `conduit-health.sqlite3` **569.9 MB** (+8.2 MB in 25.7 h),
holding **1,520,229 `events`** (1,510,929 `sample` / 6,070 `sleep` / 3,230 `workout`),
**3,028 `buckets`** and **124 `windows`** for its single device; newest row **2026-10-24 09:59:59**,
newest `buckets.date` 2026-10-24; `conduit-location.sqlite3` 80 KB; `conduit-phone.sqlite3` 284 KB.
⚠ The 10-24 page recorded **308 `buckets` / 62 `windows`**; a direct `COUNT(*)` reads
**3,028 / 124**, so the earlier pair was a narrower grouping — quote these. **No retention or
compaction has been observed** — the store grows from ingestion alone and is worth watching against
the CT460 disk budget.
## Calls from Hermes (the `conduit_call_user` tool)
The plugin registers a **`conduit_call_user`** tool (toolset `conduit`, 📞) for every session and
ships the matching skill `calling-the-user`. Hermes exposes it through **lazy tool discovery**
(`tool_search`), so it is not in a session's headline tool list — it has to be looked up.
Gate conditions (`call_tool.py`): a real session (subagents are refused), a paired device,
`settings.enabled`, and either `when_asked` (with the ask recorded as user-originated) or `decides`;
the call rings when the asking turn ends and plays the reason first. Limits: `min_gap_s 120` /
6 per hour / 20 per day.
⚠ **Known failure, 2026-10-24:** three requests to be phoned were refused by the agent, which
asserted the capability did not exist **without calling the tool or loading the skill** →
[[incidents/2026-10-24-conduit-call-request-refused]].
## Memory integration
The voice session (`conduit-voice`) reaches Mnemosyne through the plugin's own memory layer, not
@@ -74,17 +102,25 @@ ss -tlnp | grep 9119
# did a voice call lose its memory context?
grep -h "Conduit" ~/.hermes/logs/agent.log | grep -i "memory" | tail
# did a real call happen? (history = calls; ends = turn-ends, NOT calls)
python3 -c "import json,os;d=json.load(open(os.path.expanduser('~/.hermes/conduit-calls.json')));print(len(d['history']),'calls;',len(d['ends']),'turn-ends')"
# state files (no secrets in the wiki)
ls -la ~/.hermes/conduit-*.json ~/.hermes/conduit-*.sqlite3
```
## Open items
- Commit or upstream the `plugin_api.py` timeout patch so a plugin update cannot revert it.
- No retention policy on `conduit-health.sqlite3` (561.7 MB and growing).
- The Mnemosyne cold start that motivated the patch is still slow (10–45 s); only the *budget*
was raised. → [[systems/mnemosyne]]
- Commit or upstream the `plugin_api.py` timeout patch so a plugin update cannot revert it — it is
now five releases behind HEAD.
- **Verify a call end-to-end.** No call has been placed since the fix, so `MEMORY_TIMEOUT_S = 60` is
still unexercised by a real call, and the 10-24 refusal means the chat route has never worked →
[[incidents/2026-10-24-conduit-call-request-refused]].
- No retention policy on `conduit-health.sqlite3` (569.9 MB and growing).
- The Mnemosyne cold start that motivated the patch is still slow (10–45 s); only the *budget* was
raised. → [[systems/mnemosyne]]
## Related
- [[incidents/2026-10-24-conduit-call-request-refused]]
- [[incidents/2026-10-22-conduit-memory-start-timeout]]
- [[systems/mnemosyne]]
- [[systems/scheduled-tasks]]