Ethan has ~500 custom tools, and the real waste isn't dead tools (tool-graveyard-reaper handles those) — it's tools that fire constantly but whose output nobody ever reads. This surfaces the 'silent shouters': cron/systemd tools that emailed, whispered, or tablet-pushed N times in the last 30 days with zero corresponding ack, reply, reflection, or downstream commit. One card a week on the tablet: 'joyos-energy-monitor sent 214 notifications, you acted on 0 — mute, downgrade, or delete?'
Create ~/bin/notification-roi-audit (bash+python, ~80 lines). Inputs: (1) systemd journal for the last 30d filtered to user timers (`journalctl --user -S -30d -o json`) grouped by unit to get fire counts per tool; (2) delivery records from the existing whisper/email layer — parse ~/.local/share/*whisper*/ and the bounded-email + attn ack stores (attn-ack-sweep and bounded-email-ack already track acknowledgment state) for ack/reply events keyed by source tool; (3) git log across ~/projects for commits within 6h of a notification as a weak 'acted on' signal. Compute ratio = acted/fired per tool, keep tools with fired>=10 and acted==0, sort by fire count desc. Render top 5 as a markdown card via the existing pondercard-generate + socratic-tablet-pipe path into ~/Tablet/, with three stylus-checkbox actions per row (MUTE / WEEKLY / DELETE). A companion ~/bin/notification-roi-apply reads the returned annotated file via stylus-reply-router and executes: MUTE -> `systemctl --user disable --now