October summary — the addressing line, on the record

Colleagues ,
— ahead of the 4 November biweekly, a compact October summary from the addressing line. Everything below is on the public record today, each item with its address; nothing here is a projection, and only the November commitment looks forward.
The combined specification advanced to revision -01 on 27 October (34 pages, back in the Independent Submission Editor's queue): the derived-address core untouched, the security considerations rewritten around the truncation honesty account, and the TLS reference corrected to RFC 9846 — https://datatracker.ietf.org/doc/draft-li-rttp-iqa-addressing/
Both Provisional registrations hold: rttp, CRI Scheme Number 27, and iqa, CRI Scheme Number 28. This month the registry rows began citing the draft and linking the scheme specification pages at rttp.com/URI/ and iqa.org/URI/, verified live in the registry — https://www.iana.org/assignments/uri-schemes/prov/rttp · https://www.iana.org/assignments/uri-schemes/prov/iqa
Two sealed, byte-replayable run records over the lease-revocation-axes family entered the LFDT Agent-Authority-Conformance lab's mainline this month, PRs #187 and #194, both merged: revision 2 recorded Mode B author-produced runs over the frozen vectors; revision 3 added the refusal vocabulary with grant references, all five refusal values exercised across 176 composite calls, grant_ref coverage 176/176. Each artifact is organ-sealed with dual scheme addresses derived from its own digest — run reports: https://iqa.org/conformance/lra-runner/ · https://iqa.org/conformance/lra-runner-rev3/
The family also holds two independent treatments side by side, each labeled by its authorship as the lab's rules ask: the lab maintainer's reproduction review of 23 October, which surfaced two reporting defects, both fixed in the corrected revision; and an independent reproduction recorded on 29 October by Larry Lewis, chair of the W3C Agent Trust Protocol Community Group, pinned to the runner repository's head at the time (commit 8a58c88c). Two records, two authorship labels, one frozen byte stream each — the shape we argued for in post 0109.
On the deployment side, the release-attestations bundle now carries 63 sealed records, byte-identical on both sites — https://iqa.org/attestations/ · https://rttp.com/attestations/ — and every scheme address printed on our sites now resolves: fourteen sites were re-cast this month so that rttp:// addresses resolve via rttp.com/open/ and iqa:// addresses via iqa.org/open/, and our status brief received its first seal under the same discipline — https://iqa.org/brief/
The GitHub organization was recast to match the record: seventeen pillar and utility repositories are marked as frozen design archives, the founding manifesto is preserved as a historical document, and the five live repositories carry READMEs aligned with -01 — https://github.com/Aicent-Stack
The bilingual practice series continued through October; two pieces carry the semantics the conformance records test — what happens mid-task when the lease is the halt, and why there is no stop button on the wire — https://blog.aicent.com/
Two commitments for November. The first waits on nothing but our own upload: revision -02, the revision that records what this month's public exchange with reviewers produced, goes to the datatracker this November. The second is already on the record in post 0031: the AAE candidate vectors now in the lab's candidate pipeline will be run under the same treatment this family received, digest-gated inputs, per-mode and per-axis scoring, sealed-record format available as in 0031, on our schedule; no dates promised — https://lists.w3.org/Archives/Public/public-agentprotocol/2026Oct/0031.html
Every claim above resolves to bytes a third party can check. That is the whole method.
Best regards,
Lee
lee@aicent.com
Author, draft-li-rttp-iqa-addressing-01 (ISE review)
Resonant Time Transfer Protocol (RTTP, CRI 27) · Identity Quality Assurance (IQA, CRI 28)
Sites: https://rttp.com · https://iqa.org
Blog: https://blog.aicent.com

Received on Saturday, 31 October 2026 07:41:25 UTC