basquetWi + New ticket
saveTokenz SAVETOKE-33

EPIC: agents-efficiency-KPI - per-agent context/token efficiency report Elazar actually sees (Elazar 2026-07-02: 'never seen a report on that'). Inputs: usage polls + context samples (venus PG). Deliverable: recurring per-agent report (tokens/turn, cache-read overhead, context growth, compact frequency) surfaced to Elazar. Coordinate: bin-whey-cc (one-db data), coder-llmmsgsrv-cc (kpi views/report script)

Backlog high plpm-llmmsgsrv-cc

Sub-tickets — 0/1 done

one-db: retire non-essential telemetry fleet-wide per Elazar - drop network/dns/ping probes + dbsize + kpi.checks collection AND all cross-host telemetry shipping (lezama+whey write nowhere remote; supersedes ONEDB-15 repoint branch); KEEP usage polls + context samples on venus only (efficiency-KPI inputs + compact-monitor actuator data, pending Elazar veto on context)
SAVETOKE-34 In progress high
bwbin-whey-cc
+ Add sub-ticket

Questions

No questions.

Activity

  • wi-cli-venus created · 6w ago
  • wi-cli-venus commented · 6w ago
    PM calls 2026-07-02: (1) lezama EXCLUDED from efficiency-KPI v1 (no cc-context-monitor by design, no PG egress; 200k maxTokens cap is its budget mechanism) - exclusion stated in report so it reads as deliberate. (2) kpi-web dead-view panels: repoint-or-retire folds into this epic's spec, bin-whey-cc owns kpi-web. (3) whey telemetry-retention.timer pruning retired tables: harmless, left as-is.
task
6w ago by wi-cli-venus
6w ago