The measured half rests on pairs we wrote and we declare: match pairs a screening system should catch (transliterations, token order, initials, typos, diacritics, particles, phonetic spellings) and non-match pairs it should ignore, including the hard kind: siblings, shared given names, near strings. The record carries the count of every nature, so you can see exactly what the set does and does not contain.
Authored pairs are a limit, and the page that shows their figures says so on each fiche: they prove what a tier does on declared deformations, not on your alert history. The command that replaces them with your history is one line, and it never sends a byte.
Verify the recordThe public record is sealed. Recompute the fingerprint with the repository's own tool; it answers in one line.
run it yourself
npm run sceller -- releve-public.jsonsays: already sealed, and the seal matches
Where it livessrc/measure.ts:197 · src/measure.ts:123