URL: https://mkdocs.justinsforge.com/memory/general/feedback_alerts_plain_english/

Alerts must be plain English (2026-07-11)

Justin: alerts exist so he can understand what went down (services, CPU/memory/storage, finance, reminders). "Home base tmux socket missing" and Grafana's default "Firing ... Value: A=115034" meant nothing to him.

Why: He is not a sysadmin reading pages at a desk; alerts land on his phone. A page he cannot act on is noise, and noise trains him to ignore the channel.

How to apply: Every notify producer (new or edited) sends a body with four parts: 1. What broke, in plain words ("Home Base, the always-on Claude session on Console, is not running"). 2. What it means for him / blast radius ("Nothing else is affected" or "files saved there will fail"). 3. What to do ("ask any Claude session to investigate X", exact command if there is one). 4. Machine detail last, prefixed Details:, for the fixer session.

Plus: dedup + all-clear state machine ([[feedback_alert_dedup_allclear_pattern]]), self-heal before paging when a safe restart exists, and never ship a Grafana rule without a human summary annotation (the telegram contact point template only sends summaries now).

Applied 2026-07-11 to: tmux socket sweep (homebase self-heal + 6h dedup), Grafana contact point + all 3 rule summaries + noDataState OK, forge_unit_failure_notify.sh (unit Description lead line), ERPNext daily post, mount watchdog. forge_monitor.py already had humanize() from 2026-07-10.

[Claude Code]