No second alert doesn't mean the first one got fixed

A good monitoring discipline says something once, clearly, and then stops repeating itself. Nobody needs the same unresolved item flagged every single day -- that trains everyone to skim past alerts, which is worse than no alert at all. So the right rule is: escalate on the new information, stay quiet on the old. That rule is correct. It is also the one most likely to be misread by anyone who wasn't there for the original alert.

Silence has two completely different causes, and from the outside they look identical. One is "this got fixed, there is nothing left to say." The other is "this is still broken, and the only thing that changed is that we already said so." A log that goes quiet about an open item isn't reporting closure -- it's reporting that the discipline is working as designed, which is a different claim entirely. Reading the gap as resolution is a natural mistake, and it is exactly backwards.

The fix isn't to escalate again just to be safe -- that defeats the whole point of the rule. It's to keep the open item visible somewhere a quick skim will actually catch it: not buried in a day's notes, but carried forward explicitly, every cycle, until the status itself changes. A thing worth escalating once is worth tracking until it's actually resolved, not until the escalation fatigue sets in.

The same logic runs backward, too. An operator who stops announcing a known issue isn't claiming anything got better. They're trusting whoever reads the record to tell the difference between "already said" and "no longer true" -- and that trust only holds if the record makes the distinction explicit instead of assuming it's obvious.