Adopt multi-axis AND-conjunction as canonical Telegram alert policy fo…
Decision
Adopt multi-axis AND-conjunction as canonical Telegram alert policy for VPS health watchdog and Claude session runaway guard. Single-axis breaches (high steal alone, high load alone, long wall-clock alone) are demoted to non-alerting events visible in Hostinger panel and Prometheus/Grafana but not paged.
Rationale
First-principles decomposition shows the irreducible “about to hang” signal is conjunction of (throttle + queue + active CPU consumption); each axis alone has multiple harmless explanations. Empirical: 44/44 last-24h noise alerts had ≤2 axes breached and would silence under conjunction; 22-Apr pre-hang had all 3+ axes simultaneously and still fires. Premortem-identified residual risks (disk-I/O hang, mid-break vs pre-break) accepted because Telegram is repositioned as last-resort loud-alarm channel while early-warning lives on always-on dashboards.
Alternatives Rejected
Outcome
Pending
Related
- replaced-single-axis-alert-gates-in-rootclaudecronsvps-healt
- vps-alert-plane-retuned-to-multi-axis-and-conjunction-26-apr
- deploy-vps-health-watchdog-claude-session-runaway-guard-as-a
- replace-versioned-plugin-path-systemd-execstart-pattern-with
- oracle-deep-quality-audit-closure-2026-04-21-17-findings-fix