AICENT.COM
← Back to Blog

Two clocks, one decision — a new credential is not a new determination

2026-11-16 · RTTP · IQA
Reading the Draft · No. 26 · 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 agenda that set the hour: public-agentprotocol, November 2026 · the series piece that walked the time-half before: the time belongs to the determination · the mid-task companion: No. 18, what happens mid-task · Sister pillars: RTTP (rttp://, CRI 27) · IQA (iqa://, CRI 28)

The agenda that asked this week's binding question also gave its meeting an hour on cross-domain delegation, and the hour's premise is where this piece starts — because delegation is where authorization's oldest conflation breeds. A credential presented after the fact gets treated as a fresh decision. Two clocks are silently merged into one: the lifetime of the credential — the leaf's clock — and the age of the determination — the clock of the observation the decision rested on. The claim of this piece, and of the draft sections it reads, is that these are separate axes, and that every failure mode the walls keep rediscovering is one of the four cells their grid produces.

§6.1 · §8.1 · §8.2 · two clocks, four cellsthe leaf’s clock (evidence lease) and the determination’s clock (observation age) are separate axeslease fresh · observation freshthe one cell that permitsreliance under the rules of §6lease expiredevidence_expired — first applicable valueno extension, renewal, reinterpretation (§6.1)fresh credential · stale observationauthority_not_determined — the conflation cellnever read as assent (§8.1)evidence expired · diagnostic read just succeededstill refused · observation_as_of_ms stays nullno backfill: diagnostic reads do not renew evidence (§8.2)a new credential re-arms neither clock · a fresh read is not a renewal · the grid, not the vocabulary, is the mechanism
Figure 1: the two-clock grid. Only one cell permits; the other three are where implementations quietly merge the clocks — and where the refusal vocabulary names the merge instead of granting through it.

The leaf's clock rides in the bytes

The first clock is the credential's, and the draft carries it in-band rather than in anyone's assumptions. Section 6.1, verbatim: “Every attestation answer produced under the iqa scheme carries its freshness window in-band: the answer states the instant until which it may be relied on, in a field of the answer itself (the lease_expiry field of Section 7.2), not in a cache header, a lookup result, or an out-of-band agreement.” The verification rule follows: “A verifier checks the stated expiry against its own clock. The check is local and offline ... An answer whose lease has expired MUST be treated as expired; a verifier MUST NOT extend, renew, or reinterpret an expired lease except by obtaining a new answer.” The leaf's clock therefore reads locally — no network call decides freshness, and no local grace period decides it either. The envelope's lease field is eight octets of Unix seconds, the instant until which the answer counts as fresh, and nothing in the format gives an implementation room to negotiate with it.

The determination's clock has its own member

The second clock is older than any single credential: when was the standing observation made that the decision rests on? The grant reference names it — observation_as_of_ms — and Section 8.2 pins it down with the rule this series keeps returning to, verbatim: “observation_as_of_ms is null whenever the observation the answer relied on is absent or not fresh, even if a later, successful observation is available at answer time. A diagnostic or opportunistic read performed after the relied-on evidence expired does not backfill the member: diagnostic reads do not participate in authorisation and do not renew evidence.” The member states “the age of what the answer actually relied on, not the freshness of the freshest thing the implementation happened to see.” Two fields, two clocks: the lease lives in the envelope's octets; the determination's age lives in the grant reference — structurally separated, so an implementation cannot conflate them without breaking the wire format.

The four cells, and the trap

Two binary clocks give four cells, and the refusal vocabulary lands one answer in each. Lease fresh, observation fresh — the one cell that permits. Lease expired — evidence_expired, the first applicable value, with no extension, renewal, or reinterpretation available. Fresh credential presented now, but the only observation predates the request — authority_not_determined; Section 8.1, verbatim: “because the only observation available predates the request and therefore establishes nothing about the present. An unreachable source is refused under this value, never read as assent.” And the fourth cell is the trap: the evidence expired, but a successful diagnostic read just happened — still refused, and the observation member stays null. A new credential is not a new determination; a fresh read is not a renewal. The grid, not the vocabulary, is the mechanism: the closed set merely gives each cell a name an implementation cannot quietly reinterpret.

What the delegation hour will need

This is the equipment the cross-domain delegation hour will need before its first scenario runs. A delegation chain threads credentials through intermediaries, and every link multiplies the temptation to merge the clocks: an intermediary holds a current credential and quietly treats its own freshness as the subject's; a downstream relying party sees a recently presented token and forgets to ask when the standing observation behind it was made. The draft's answer is structural, not advisory — the two ages travel in different fields, so the conflation has no wire representation. Where the ages cannot be conflated, they cannot be quietly merged; they can only be named. The series has walked the time-half of this once before, following a working-group thread's wording; what this piece adds is the arithmetic — four cells and a no-backfill rule — read from the published text rather than from the thread. Determination is not credential is also the load-bearing distinction of the whole series: the closed set exists so the difference has a name, the null rule exists so the difference has a number.

§8.2 · the no-backfill rule on a timelinewhat the answer relied on is what it reports — not the freshest thing it happened to seet0 grant issuedt1 observation madet2 evidence expirest3 request arrivest4 diagnostic readat t3 the answer is refusedthe relied-on evidence is behind t2 → the applicable value names itobservation_as_of_ms stays nullthe member reports the age of what the answer relied on — null, not t4t4 succeeds anywayand changes nothing — diagnostic reads do not participate in authorisationbackfilling the member is how an answer quietly inflates itself · the null rule is the padlock on the field
Figure 2: the no-backfill rule on a timeline. The request lands after the evidence expired; a later diagnostic read succeeds and still changes nothing — the answer reports the age of what it relied on, which is null, not the freshness of the read it happened to see.

One line: the credential's clock answers whether the bytes are still fresh; the observation's clock answers whether the determination still binds; a new credential re-arms neither — and where the two clocks disagree, the refusal vocabulary names the disagreement instead of granting through it: rttp resolves where & when; iqa states whether — and where the two agree, action begins.

SEALED rttp://ab1c94fa.blog.aicent · iqa://ab1c94fa1c9a32d002c636cf3b395d27.forge.iqa · seal record