aro:pluto PM->Elazar digest batching: route routine status/FINISHED/deploy-notices into 1 daily digest DM; only decisions+blockers go direct-DM; TLDR-first, cap <1500 chars. CARVE-OUT: triage-loop pre-analyzed verdicts + live-ticket coordination stay direct (Elazar's model wants them pushed). Highest ROI in Pluto area: pm-pluto-cc sent 39 DMs/35807 chars/~8952 tok to Elazar in 24h, highest avg chars/DM (918).

Sub-tickets

Activity

• wi-cli-venus created · 2026-06-27
  parent=#1438
• wi-cli-venus questionAsked · 2026-06-27
  What counts as 'routine enough to batch into a daily digest' vs 'push to me directly now'? Proposed carve-outs that stay DIRECT regardless: (a) triage-loop pre-analyzed verdicts (access grants, support-ticket dispositions), (b) live-ticket/incident coordination, (c) anything blocked-on-you. Candidate-to-batch: FINISHED banners, deploy/PASS notices, non-blocking status. Holding all pm-pluto-cc->Elazar throttling until you rule.
• wi-cli-venus blocked · 2026-06-27
  blocked by question #53
• wi-cli-venus completed · 2026-06-28
  WONT-DO per Elazar 2026-06-27: PM<->Elazar is real-time work — he needs the answer as soon as it's available and the PM to act as soon as it can; batching PM->Elazar DMs into a digest is impossible/unacceptable. No PM->Elazar throttling. Token savings on the Pluto leg must come from worker/ARO posts (27/28/29), NOT the PM->Elazar channel.
• wi-cli-venus questionAnswered · 2026-08-19
  ANSWERED (recovered from the close event, not decided now). Elazar 2026-06-27, WONT-DO: PM<->Elazar is real-time work — he needs the answer as soon as it is available and the PM to act as soon as it can, so batching PM->Elazar DMs into a digest is unacceptable. There is no batchable category on that leg; the carve-out list in this question is moot because nothing is batched at all. Token savings on the Pluto leg must come from worker/ARO posts (SAVETOKE-27/28/29), not the PM->Elazar channel.
• wi-cli-venus unblocked · 2026-08-19
  backfill: blockedReason cleared on a closed row; it described a dependency discharged before the item closed and pre-dated the d6153e2 fix that now clears it automatically (Elazar decision 1b, 2026-08-19)