kpi
KPI-27
· child of KPI-1 Fleet inventory: every token/context/llmmsg-srv script, monitor, service each agent owns/knows Backlog
llmmsg-kpi-coach.sh v1.8 - daily coaching pass over the KPI report
Canceled normal
bvbin-venus-cc
READS: output of llmmsg-kpi-report.sh + /opt/llmmsg-srv/coaching/kpi-coach-rules.md (rules SSOT). EMITS: per-agent coaching DMs + full summary CC to pm-llmmsgsrv-cc, every run. Runs headless Sonnet-5. STAGE-gated, default 'direct'. Elazar-assigned daily cadence 2026-07-12 (self-arm banned). Host venus. Registry row 43, primary bin-venus-cc / backup bin-whey-cc. DEPENDENCY: consumes the report above, so any change to the report's shape breaks this silently.
Activity
-
parent=#2960
-
OBSOLETED, NOT DONE - the target script was deleted by Elazar in 38bdd55 'retire agent telemetry tracking stack' (2026-09-24, author Elazar Pimentel). Verified on disk and in git history 2026-10-05: no live copy in ~/.local/bin, none in /home/rob/scripts, and no systemd user unit references it. The commit removed the whole stack in one go - llmmsg-kpi-report.sh, llmmsg-kpi-coach.sh, ccusage-snapshot.sh, ccusage-watch.sh, token-usage-web.sh, token-usage-collect.sh, token-usage-push-lezama.py - and fleet-tokens.sh went the same day in 03c7d53. Cancelled rather than closed because the work was never performed; it stopped being wanted. Reopening any of these means re-specifying it against whatever replaces the stack, which is the open Elazar decision recorded on KPI-68. Found while reconciling KPI-68 at pmmaster's request - these four were sitting in the 'large non-blocked KPI backlog' and are not backlog, they are phantom rows against deleted files.
task
7w ago by wi-cli-venus
1w ago
2026-10-05 16:51