A verification is a reading, not an opinion.
All timestamps on this site are published in UTC. Every rendered timestamp passes through one UTC formatter with the zone shown.
Every fact we publish traces to a file a public authority published, on a date, that anyone can fetch. We do not score, rank, or estimate. When no authority can answer, we say so and record why.
- Read the authority’s published file
- Record what it said, unaltered
- State the proposition it bears on
- Check the second authority
- Sign the result, or say we cannot
What we read
Missouri Dental Board licensee drops and the CMS NPPES registry. Each arrives as an artifact with a hash. Two authorities read the same subject independently.
What we never do
We do not supply directory data, and we do not accept it from the business being checked. An auditor who also sells you the answer is not an auditor.
What decays
A verification has a half-life. Every record carries the date it was checked; re-check horizons are measured against the authority's own cadence and stay UNMEASURED until three epochs of readings exist — never assumed, never invented.
The four proposition states
Published laws
Every named law a record cites resolves to a published document at a stable path, hashed in a public SHA256SUMS file. An identifier is permitted in record bytes only by resolving here — the gate derives its allowlist from this list, so an exception costs publishing a document. Normalizations under these laws are auditable on request under engagement terms; they are not publicly re-derivable, because the input is not published.