kpi
KPI-56
· child of KPI-47 Staged offender remediation: escalation ladder (DM -> alert Elazar -> unregister/kill) Blocked
KPI-47 stage 3: unregister from hub + kill process after M more ignored DMs
Canceled high
bvbin-venus-cc
Stage 3 of the ladder, Elazar policy 2026-09-03. When an agent is still flagged M DMs (proposed 3, ~90min total) after the stage-2 Elazar alert: (a) unregister it from the hub via POST /unregister (MSG-38, coder-llmmsgsrv-cc - route must exist first; until then this stage is blocked on MSG-38), and/or (b) kill the agent's tmux pane/process on its host. Record the kill in kpi-burn-alert state and DM Elazar the kill record on all channels. Kill is host-local: venus agents direct, whey/lezama via that host's nw agent. This stage MUST be fully reversible to read-only via a single flag (KILL_ENABLED=0) so containment is one edit.
Activity
-
parent=#3066
-
Depends on MSG-38 (POST /unregister route, coder-llmmsgsrv-cc, backlog). Kill-pane half can proceed; hub-unregister half cannot until MSG-38 ships.
-
parent=KPI-47
-
Elazar 2026-09-03: M=2 more after stage 2 (60min total). Action = kill pane + hub-unregister (3a). Applies to all three hosts incl. lezama (4a). Kill-pane half is NOT blocked - only the unregister call waits on MSG-38.
-
2026-09-03 07:25Z: bin-venus-cc will build the unregister half behind KILL_ENABLED=0 and requires Elazar's DIRECT word for the pane-kill half (relayed GO covers ordinary work, not killing another agent's process). Record: Elazar answered nqla 3a IN THE CLI to monitor-context-cc on 2026-09-03 ('stage 3 = kill tmux pane AND hub-unregister') - direct to me, relayed to bin-venus-cc. Elazar: confirm to bin-venus-cc directly, or state here that the CLI answer suffices.
-
cleared: Depends on MSG-38 (POST /unregister route, coder-llmmsgsrv-cc, backlog). Kill-pane half can proceed; hub-unregister half cannot until MSG-38 ships.
-
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