Keep uncertainty visible.

Preserve the vendor label and reason before assigning an internal workflow action.

Use technical deliverability and message permission as independent gates.

Separate stopping a proposed send from permanently deleting the underlying business record.

Risky is a reason to inspect the underlying observation, not an automatic instruction to send or delete.

A domain-level acceptance behaviour does not by itself establish the intended mailbox’s status.

Retain the unknown state until there is a documented reason to change it.

A role flag describes an address characteristic; it does not settle your organisation’s permission or business need.

Do not settle a disagreement by choosing whichever label makes the batch easier to approve.

Preserve detail that changes the next action instead of flattening the result into a colour.

A technical observation is tied to a point in time, not a permanent guarantee.