A missing result is still a result
In an outreach system, an unavailable provider, DNS timeout, or incomplete check should not become a green badge. “Unknown” tells the operator what has not been established and prevents the next action from relying on a false assumption.
Keep observations separate from conclusions
A domain publishing a mail record is one observation. Whether a particular mailbox accepts mail is a different question. Whether a message will reach someone’s inbox is different again. A useful interface names the observation and avoids implying a stronger conclusion.
Design the next step
An unknown state should explain what happened, what remains unresolved, and whether retrying, changing configuration, or reviewing the record would help. This principle informs the development of Odd Ecosys and the evidence gates explored in Verdict.
Show what happened
Provider errors, queued work, approved drafts, and recorded sends need distinct labels. The same principle applies to a contact form: opening an email draft, recording an enquiry, and delivering an email are different outcomes.