AICENT.COM
← Back to Blog

The action never changes the address

2026-11-18 · RTTP · IQA
Reading the Draft · No. 29 · Sources cited in this piece · the text read sentence by sentence: draft-li-rttp-iqa-addressing-02 (full text) · series page and revision history: datatracker · the family as it entered the mainline: the route-shard family page (sealed record) · the merge record: lab PR #224 · Sister pillars: RTTP (rttp://, CRI 27) · IQA (iqa://, CRI 28)

Every addressing system faces the same temptation: let the request shape the address. It feels natural — of course asking for different things should route to different places — and it quietly destroys the thing an address is for. The route-shard family exists to keep that temptation out of the rttp scheme. It is our case set for the ROUTE_SHARD derivation of section 4.4, it entered the conformance lab's mainline as PR #224 this week, merged at 04:56:09Z on 2026-11-17 — five minutes after its sibling family — and its quiet center is a single sentence: the derivation takes the authority alone, and the action never changes the address.

§4.4 · the derivation takes the authority aloneno DNS · no registry · no network access · no lookup servicerttp://f3b2a1c4.pillar.example/vesselscheme "rttp:" · "//" · action "vessel" — all excluded from the inputf3b2a1c4.pillar.exampleSHA-256(ASCII(·))[0:16]557c8154d3780cb78cc5fa1bd72b331cthe output address is pinned by the draft itself (§7.2.1) for the §4.1 example authority —derivation cases RS-D01–D03 recompute it and a name-intent and a digits-and-hyphens authoritysame authority + different action = same address (RS-B01/B02)deterministic · pure computation · one-way · action-independent
Figure 1: the derivation pipeline. The input is the full authority — intent.pillar.root, lowercase US-ASCII — and nothing else; the example output is the address the draft itself publishes, which the family recomputes rather than assumes.

The derivation takes the authority alone

Section 4.4 defines the whole routing address in two lines: canonical_authority = intent "." pillar "." root, lowercase US-ASCII, and ROUTE_SHARD = SHA-256(ASCII(canonical_authority))[0:16]. Then the boundary sentence that the family is built around: “The authority only: the scheme name, "//" and any action are excluded.” The draft lists four properties of what comes out — the address is deterministic, pure computation (“no DNS, no registry, no network access, no lookup service”), one-way, and action-independent. The family's three derivation cases do not trust the draft's own arithmetic on faith: RS-D01 recomputes the address for the section 4.1 example authority and matches it against the value section 7.2.1 pins in the text — 557c8154d3780cb78cc5fa1bd72b331c — while RS-D02 and RS-D03 derive two more authorities deterministically.

Why the action never participates

The draft answers the question in one sentence that carries the entire doctrine of the two questions: “an address is where, not what — and not when” — where is the address, when is the pulse's own time fields, and what is the action, which is a claim riding the pulse rather than a property baked into the subject's coordinates. The consequence is stated as a counterfactual, verbatim: “Were the action to participate in derivation, two actions on one subject would become two addresses, splitting one subject into several.” Two property cases pin it from the outside: different actions on one authority must yield the same address, and a checker that let the action participate is scored nonconformant. The canonical-form boundary joins the same defense — “Uppercase is invalid input, not a formatting difference: a parser MUST NOT normalise it, because two distinct strings would then map onto one address.” Every excluded input is excluded for the same reason: a derivation that forgives differences collapses subjects that the scheme promised to keep distinct.

§9.1 · the honest truncation account · two gates, not oneentry fingerprint, not a proof of identity — the AID carries identitygate 1 · substitution · ~2^128find a second authority yieldingthe same address in usegate 2 · birthday · ~2^64 + adoptionrequires a second, independent partyto adopt the colliding labeldisplay-form red line · 8 hex digits = 32-bit space = birthday ~2^16display conveniences over the full hash forms — MUST NOT be the sole identifier of a subject (RS-B13)16/16 cases agree · 9/9 mutants killed · merged as lab PR #224 (2026-11-17T04:56:09Z)
Figure 2: the honest truncation account. The 128-bit address defends substitution in use at roughly 2^128; the birthday bound at 2^64 is not enough to reach on its own — it needs a second independent party to adopt the colliding label. And the 8-hex display form, a 32-bit space, is forbidden as a sole identifier — the family holds that line with a dedicated case.

The red line at the end of the address

Section 9.1 states the address's modesty in its opening bullet: “The derived address is an entry fingerprint, not a proof of identity. Identity is carried by the subject's AID, and any attestation of it is carried separately.” Then comes the truncation account that most designs leave out, and this draft puts on the record with both halves: substitution of the authority in use costs approximately 2^128 operations, but “a birthday collision exists at approximately 2^64, and reaching it additionally requires a second, independent party to adopt the colliding label — two gates, not one.” Two gates, not one — the honest account is not the smaller number. The family carries this into behavior rather than prose: RS-B11 is a distinctness spot check, and RS-B13 pins the red line that “the 8-hex-digit display forms of both schemes ... MUST NOT be used as the sole identifier of a subject” — routing by the display form alone is scored nonconformant. A 32-bit space whose collisions are expected after roughly 2^16 adoptions is a convenience, and the moment a convenience is load-bearing it becomes an attack surface with a birthday party.

One line: the derivation takes the authority alone because an address is where, not what and not when; the action stays on the pulse, the uppercase stays invalid, and the display form stays a convenience — two gates stand between a subject and a collision, and the suite's job is to make sure neither gate is ever wired out: rttp resolves where & when; iqa states whether — and where the two agree, action begins.

SEALED rttp://be51443e.blog.aicent · iqa://be51443e9159255d840fba934fa32425.forge.iqa · seal record