Salvo clusters your alerts, proposes the root cause, and drafts the runbook.
A page at 3 AM is not a problem statement. It is a symptom of a system telling you forty things at once.
Most of those forty are downstream of the one that matters. On-call spends the first ten minutes de-duping Slack channels, pulling up dashboards, and asking the same question: which deploy broke this? Salvo answers it first, in writing, with evidence.
A cause without an evidence path is not a cause. The traversal is shown to you so you can disagree in public.
Top-cause and runbook both carry a score. Salvo flags the ones it would pause before running.
The agent drafts kubectl. You paste it. A human is always in the loop.
One of eight in the rotation. First ten minutes set the tone. Salvo makes the first ten minutes a read, not a triage.
Reads postmortems on Monday. Wants the scaffolding standard and the narrative human.
No dedicated on-call yet. Every page goes to the same phone. Salvo is the first responder that keeps that phone usable.
“The first ten minutes used to be: open six tabs, join three channels, ask who deployed. Now it is: read one page.”