John tells Pim, his personal agent, to book a trip with Travel26. Pim looks up Travel26's booking agent, gets an answer, and sends John's details there. The answer came from one place. If that place was stale, tampered with, or answering Pim differently from everyone else, nothing in the answer says so.
An agent is usually listed in more than one place: its own DNS zone, a registry, a transparency log, the company's catalog. sm-divergence asks all of them, reduces each answer to the same shape, compares them, and signs a record of what each one said. Agreement becomes something Pim can show. Disagreement becomes a finding that names who said what.
Travel26's booking agent is listed in four places, and every run of this demo builds all four: a zone served over DNS-over-HTTPS, a registry, a transparency log that issues signed receipts, and a catalog document. The library asks them over HTTP; nothing is mocked inside it.
One adapter per place the agent is listed. Each knows that source's own id for the agent and its own format.
SVCB row · JSON record · COSE receipt · catalog entryEvery answer becomes the same small view: where the agent's card is, and what it should hash to. Three spellings of one digest become one.
RecordView(endpoint, digest)Present, absent, or error. A timeout, a 503, a receipt that doesn't verify, a revoked registration: each is an error with its reason, and none is a claim of absence.
present · absent · error(outcome)The claims are diffed. Different address, different digest, one source missing the agent, one source telling two vantages different things.
AGREE · DIVERGENT · INSUFFICIENTOne record per sweep, whatever the verdict: an AGREE record is the proof the check ran. Canonical JSON, a content address, an Ed25519 signature.
verifyRecord(record) → okOne source alone is INSUFFICIENT, never AGREE. A verdict says whether the sources agree with each other. It doesn't say which one is right.
Every run builds a new zone, registry, log and catalog for Travel26, changes what one of them says, runs the sweep, and checks the result. Below is the latest live run of each story. While a run is kept, its sources stay open under /runs/<id>/.
This page recomputes the record's content address and verifies its signature itself (WebCrypto when available, pure JavaScript otherwise). It doesn't ask the server whether the record is valid.
A valid record proves that this key signed exactly these claims and that nothing changed since. It doesn't prove the signer asked the sources honestly, and it doesn't prove any source told the truth. This site's key is at /key.
For the technically minded: the record is RFC 8785 canonical JSON. record_id is SHA-256 over every member except itself and signature; signature is Ed25519 over every member except itself; sweeper is a did:key, which is the public key. Format corroboration/0.4, specified in the repository.
Python 3.11+. Adapters for a DNS zone, a registry record by id, a transparency log and a published catalog; bring your own with three methods.
pip install 'sm-divergence[ans,attestation]'
Ask a zone through a resolver you choose, a log and a catalog about one agent, and print each claim, each finding and the verdict.
python examples/live_sweep.py agent.example.com \ --zone --doh https://…/dns-query \ --log https://… --catalog https://…
Sweep, then decide. The record is what you keep: what every source said at that moment, signed.
(result,) = await Corroborator(sources).check([agent_id]) record = build_corroboration_record(result, …)
This asks the DNS only: the name's SVCB row, else its _ans TXT row, through the resolvers this site is configured with. Most names publish neither; that is an answer too. The site fetches nothing from the name you type.
.example, and every key is made for the run.The adapters, the detector, the Corroboration Record, this site and its stories.
The resolver contract, the outcomes, the record format and how to verify one.
The argument for asking more than one source, and what agreement does and doesn't show.
pip install sm-divergence, with extras for DNS, signed log receipts and signed records.
When a personal agent stops mid-booking, the next one finds out whether it went through. Same John.
When a personal agent forgets something, is it gone? Same format, same Pim.