How this register works
Browse the live directory, try Stumble, or suggest a business. All submissions require editorial review. Read a listing’s evidence and review date before relying on it; inclusion is not a guarantee of quality or current availability.
Everything that lets you audit this site in one place: the bar entries must clear, the checks behind every date, the patterns we refuse, the tombstone procedure, and the money that never touches any of it.
The short version
A register is only as good as the things it refuses. Ours publishes its criteria before its records, dates every claim it makes, keeps the businesses that die instead of deleting them, refuses to rate anyone, and takes no money from the businesses it lists.
Each of those is a separate document, because each of them is something you should be able to check independently rather than take as a bundle.
The documents, in reading order
1. The entry bar
Six criteria, every category exclusion, and the disclosure rule for publisher-owned properties. Read it.
2. The method
How a check runs, the four outcomes, the failure sequence, and what a passing check does not tell you. Read it.
3. The changelog
Append-only version history for the method and the bar, including what each change invalidated. Read it.
4. The refusal file
Anonymised patterns we turn down, each tied to the criterion it failed. Read it.
5. Gone
Businesses confirmed no longer trading, kept with the date of their final check. Read it.
6. Who pays for this
Every way we could take money for a listing, and the mechanism that stops it. Read it.
7. The Line
The permanent list of things this site refuses to publish at all. Read it.
8. Corrections
What we got wrong, dated and described, including the errors readers caught. Read it.
The four things that make an entry an entry
- A named reviewer. Not a team, not a process — a person, recorded on the record.
- A review date tied to a dated check log. The date records the check, not the most recent page update.
- A description written here, in our words. Operator copy appears only as an attributed quote.
- The version of the bar and the method that produced it, so an old entry stays interpretable.
We publish an entry only when all of these checks are complete.
What we deliberately do not do
No ratings, scores, stars, tiers or best-of lists — our listing policy does not allow them. No paid inclusion, position or removal. No affiliate links inside any record. No location-by-category pages. No framing of anyone else's website inside ours. No residential addresses, ever.
The reasoning for each is at the Line, and the specific case against ratings is at why we don't rate anyone.
Current state
This edition supplies no assessment log, so the observed entry count and refusal rate are not measured. The register and the entry bar define the complete schema and criteria without promising a future dataset.
If you want to audit us
- Read the entry bar and pick a criterion you think is unenforceable.
- Read the method and check whether the criterion actually has a procedure behind it.
- Look at any entry and confirm it carries a reviewer, a date and a version.
- Check the version against the changelog.
- Tell us what you found at corrections. We publish the ones we get wrong.
Questions about the mechanism
Why split this across so many pages instead of one policy page?
Because each part should be checkable on its own. Bundled into a single policy statement, a weak criterion hides behind a strong one and nobody can point at the specific thing they disagree with.
What stops a future editor quietly relaxing the bar?
The version history makes changes visible, and every published entry must name its reviewer, review date and the rules used to assess it. These safeguards are not impossible to circumvent, and we would not claim otherwise — which is why what we would have to do to go bad names the external signals to watch for.
Is inclusion an endorsement?
No. It means a business exists, is independent, is reachable and was trading on a stated date. Anything beyond that is a reading you have added, and we try hard not to invite it.
How is this different from a verification badge?
A badge is a claim about a process you cannot see. Read the published method alongside the actual evidence provided on the listing; a policy alone is not proof that a particular review occurred. What a verified badge would have to prove sets out the difference.
Can a machine read all of this?
Yes. The agent contract documents the fields, the null rule, the licence, the staleness threshold and the correction path. It describes requirements for a conforming export, rather than promising a downloadable dataset or an automatic publication check.
What happens when you make a mistake?
It goes in corrections with a date and a description, including whether we caught it or somebody else did. The ratio between those two is the more informative number.
This page is a hub. Each document it links to is the authoritative version of its own subject.
