Ask a room of founders why they muted their alerts channel and you get the same answer every time: too much noise. But noise is not a property of the events. Your stack produced a payout failure and a routine deploy notification, and the tool treated them identically. Noise is what undecided events look like by the time they reach you.
The industry's answer has been thresholds. Write a rule, test it against history, arm it. That works, and we build on it — a rule you wrote down in advance is still the most trustworthy alert there is. But a rule only judges the one condition you thought to write down. Everything else flows through unjudged, and the unjudged flow is where the 3am mistake and the 3am false alarm both come from.
The alternative is to judge every event when it arrives, not just the ones that trip a wire. What kind of signal is this — money, reliability, security, cost, or background? How urgent is it? And the question no alerting tool used to ask: how sure are you?
That last question is the one that matters. A system that cannot say "I don't know" will eventually cry wolf, because it has to answer either way. When the judgment carries its own certainty, the product can be honest with you: this is worth a page and we are sure, this is worth a glance when you are free, this is filed and you never needed to see it. A maybe is shown as a maybe, not dressed up as a verdict.
This is what the timeline in InternalStatus now shows. Every event that arrives is read and marked: routine, noteworthy or urgent, with the certainty of that read next to it. The payout failure at 94% urgent is marked worth a page. The successful deploy at 98% routine is filed. The ambiguous one at 51% is labelled a maybe, because that is what it is.
Two things this is not. It is not a filter: nothing is hidden, muted or resolved by a verdict, and every rule you armed still fires exactly as before — the judgment is added, nothing is taken away. And it is not a black box you are asked to trust: the verdict and its certainty sit on the event itself, so when you disagree you can see precisely what you are disagreeing with.
Attention is the only resource a small team cannot buy more of. A tool earns its place on your lock screen by spending that attention carefully — paging you when it is sure and it matters, and having the discipline to say so when it is not. That discipline, not another dashboard, is what calm operations actually looks like.