Current
The Quilt That Checks Itself
Corroborated Discovery for the Internet of AI Agents — the core method and the Corroboration Record. v1.1 (30 Oct 2026) adds resolution sources and the lease sequence, supersession, the digest, and DAWN alignment. Read on this site; a Google Docs mirror is linked from the paper page.
→ PAPER · v2.0The Registry Points, the Quilt Proves
A quilt-of-registries model for verifiable agent discovery under registry-assisted resolution. The index moves out of the resolution path into configuration and audit; every panel — ANS, DNS-AID, ARD catalogs, AgentFacts cards, DIDs, workloads — is placed in the profile's terms. Read on this site; a Google Docs mirror is linked from the paper page.
→ INTERNET-DRAFT · -02 · publisheddraft-chandra-agent-registry-corroboration-02
Multi-Source Corroboration for AI Agent Discovery — the current published revision, submitted 30 October 2026. Aligns corroboration with registry-assisted resolution of known subjects and the DAWN charter: supersession, the digest field, a known-subject resolver, and a normative statement of the relationship (Section 12).
Revision history
All revisions, status, and the diff between them.
↗
Each revision is tagged to the code that implements it, so the normative text and the
implementation move together: draft-02 ↔ sm-divergence 0.12.0 + the sm-resolver 0.7.0
kernel;
draft-01
↔ 0.9.0 + 0.3.0; and
draft-00
↔ 0.8.0 + 0.2.0. The text committed at each tag is byte-identical to the revision the IETF serves.
What changes in -02
-02 aligns corroboration with registry-assisted resolution of known subjects,
the DAWN-aligned profile under which a registry resolves a known subject to a terminal target in
one hop, as a renewable lease with a sequence. Three consequences, each implemented
before the text was written:
Supersession (Section 6.4). A claim below the current sequence in its authority
scope is stale_binding — attributed to the lagging source and withheld from the field
comparison. Lag is attributed, never accused. Equal sequence, different target still diverges.
Digest (Section 11). The discovery view gains targetDigest; same
address, different digest is host-level substitution, a kind the endpoint comparison could not
express. The relationship (Section 12). Resolution is one source's answer,
corroboration the comparison; no forwarding; bounded fan-out and exact lookup; authority evidence
is provenance, never verdict; the direct DNS path is a source; Answer Scope sits beside the
profile's target scope.
Also: expired and revoked outcomes, binding on claim entries
(record version corroboration/0.4), eight new conformance cases, and two new security
considerations (fan-out and enumeration; authority laundering). The DAWN charter, terminology and
requirements drafts are cited as the frame, and Raskar, Sharaf and Chari are credited in the
Acknowledgements.
How the two compose →
Archive
Earlier versions are kept exactly as published. They describe the model as it stood before the October 2026 alignment with registry-assisted resolution; the current papers above say what changed and why.
The Quilt That Checks Itself (v1.0)
The original paper (July–August 2026): the threat taxonomy, the resolve · view · diff primitive, the signed self-description, and the Corroboration Record. Superseded by v1.1 above.
↗ PAPER · v1.0 · archivedThe Index Points, the Registry Proves (v1.0)
The original quilt-of-registries paper: a pointer-only index in the resolution path, domainless trust, verifiable index entries, cross-registry corroboration. Its two-hop model is what the resolution profile retires; superseded by The Registry Points, the Quilt Proves above.
↗ INTERNET-DRAFT · -01 · supersededdraft-chandra-agent-registry-corroboration-01
Submitted 27 August 2026. Adds the Answer Scope and declared divergence. Superseded by -02.
draft-chandra-agent-registry-corroboration-00
The first revision, submitted 4 July 2026.
↗ SITE · v1 · archivedthequilt.ai v1
The site as it stood from July to October 2026, frozen with an archive banner.
→What changed in -01
-01 adds the Answer Scope: a way for a source to declare, in advance, which
fields it varies and along which context. Not every difference between two registries is a
lie, and a procedure that reports every difference as one fires during normal operation.
The rest of the revision follows from it. A vantage becomes a controlled term with an
externally defined value space, so two sweepers mean the same thing by the same label.
Cross-source comparison is scoped to a cohort. A finding carries whether it was declared and
which revision of the declaration was matched. The record version becomes
corroboration/0.2, and a verifier is now required to check it.