Our public test set, a file we froze, has two halves, one measured and one synthetic. The measured half is 120 pairs written for this repository by an AI agent and labeled by kind (commit 474ffbd of 5 September 2026); no pair comes from a client or from a list, and the labels ship with the pairs so a debatable one can be argued on the record. Some are matches a screening system should catch: transliterations, changed word order, initials, typos, accents and marks, particles such as de or al, spellings by sound. Others are non-matching pairs it should ignore. The hard kind are near-matches, pairs that look alike but are not the same person, such as siblings, shared given names or near-identical spellings. The set counts each kind, so you can see how many of each it holds and which are missing.
Written pairs can only show so much, and the page with their figures repeats this next to each one. They prove what a matcher does on the variations they label, and they do not cover your alert history. The command that swaps our pairs for your history is one line, and it sends no data.
Check the test setThe test set is frozen (the tool's word is sealed). The repository's tool recomputes its content hash, a fingerprint of the file's bytes, and answers in one line.
run it yourself
npm run sceller -- releve-public.json --checksays: already sealed, and the seal matches
Where it livessrc/measure.ts:197 · src/measure.ts:123