Evidence supports use.
The observed technical signals satisfy the active Clean policy without material unresolved risk.
Inspect evidence before acting.Clean separates observed evidence, confidence, policy and recommended action so a technical signal never masquerades as certainty.
The decision state is an action-oriented summary. It does not erase the evidence or uncertainty underneath it.
The observed technical signals satisfy the active Clean policy without material unresolved risk.
Inspect evidence before acting.Signals are mixed, contextual, or policy-sensitive enough that an operator should inspect the evidence.
Do not silently upgrade to safe.The active policy finds enough technical risk to recommend keeping the address out of the intended workflow.
Policy remains explicit.Clean preserves uncertainty when the available signals cannot support a stronger claim.
Unknown stays unknown.A durable verification is more than a status word. Clean keeps observation and policy separate so teams can understand how a decision was formed.
Address structure, Unicode handling and normalized evaluation input.
Domain state, MX routing, null-MX handling and implicit routing evidence.
Disposable, role-address, free-provider and typo-related signals.
Bounded SMTP RCPT evidence when authenticated verification is allowed to perform it.
The explicit rules that convert observations into safe, review, suppress or unresolved.
Receipt and audit context for later explanation and system accountability.