KPI-46 Linux notification leg: inotify/notify-send on whey, venus, lezama
Canceled high
bvbin-venus-cc
Linux desktop/host notification leg for kpi-burn-alert.sh findings and KPI-47 stage-2 escalations on all three hosts (whey, venus, lezama). Mechanism: the alert writes a breadcrumb file per host into a watched dir and a per-host inotify watcher (or notify-send where a session bus exists) raises the notification; do not depend on the hub being up. Venus is the only host running kpi-burn-alert.sh, so whey/lezama need the breadcrumb delivered cross-host (/data-venus is the sanctioned transfer path). Coordinate host-side watchers with nw-whey-cc / nw-lezama-cc.
Activity
-
parent=#3065
-
parent=KPI-46
-
Elazar 2026-09-03 (4a): all three hosts, lezama included.
-
OBSOLETED, NOT DONE. This row is an implementation LEG of kpi-burn-alert.sh, which Elazar deleted in 38bdd55 'retire agent telemetry tracking stack' (2026-09-24). Verified 2026-10-05: no kpi-burn-alert.sh in ~/.local/bin, confirmed deleted in git history, and its registry row 188 is retired. An email leg, a notify-send leg, a DM fan-out and the stage-2/stage-3 escalation rungs are all internals of that one alerter - there is no file to add them to. Cancelled rather than closed because the work was never performed. The underlying CAPABILITY (alert Elazar on misconfig/high-burn/context/needless-turns, and a staged offender ladder) is NOT cancelled with this - KPI-46 and KPI-47 carry it and are marked blocked on the one open Elazar decision recorded on KPI-68: whether the retired telemetry stack returns at all. If it does, these legs get re-specified against whatever replaces the alerter, not revived against this file:line.
feature
6w ago by wi-cli-venus
1w ago
2026-10-05 16:52