A serious monitoring queue separates a small class of alerts from everything else and routes them straight to a human within the hour; most findings can wait a week, a few cannot wait a day. A ruin-class risk is not the largest risk in the file, it is the one whose realisation ends the relationship the reader is trying to protect, and the report treats it that way from the first line.
A small set of findings cannot wait. Anything that ends in seizure, debanking, lost custody, or a rail turning off is a class where the second pass happens after the fact and the fact is irreversible. Treating those the same as an address correction is the wrong shape.
We act one band earlier on ruin-class risks. If the calibrated confidence would normally get a client a heads-up at "elevated," on this class it moves at "monitor." The client would rather be told twice about a false alarm than told once about a real one after it closed.
The list of ruin-class risks is short and stable. It does not grow with the roadmap. It stays short on purpose, because everything on it distorts the pace of the review, and adding a fifth thing means the first four get less attention.
Most findings can wait a review cycle. A small class cannot, because acting after the fact is not a form of acting. The discipline is knowing in advance which category any given signal belongs to, so the response is set before the pressure of the moment is added.
The general form of this idea, useful well beyond private work, is that not all risks can be treated as statistical bets. A few live in a class where a single bad outcome removes the ability to play the game again. Those get separate rules, chosen calmly, ahead of time.