Re: Four open questions on the Agentic Web report (2026-09-24): preimage defense, address assurance, trust leases, statement granularity

Lee, Alan, Larry, Tymofii, all,

Following the refusal-reason discussion: the five-value set answers "why was the next call refused." Lee's closing question — when the interpreter and the clock disagree, which does the relying party audit against — points at a separate layer the closed set doesn't cover: what happens after a call has been authorized and the chain is already running.

The five values tell you why a boundary was closed. They don't tell you how to suspend an agent that's mid-task when the clock has turned. A lease that expires at 14:00 blocks the 14:01 call, but the chain that started at 13:50 and is still executing at 14:05 needs something the refusal set doesn't model: a runtime halt, not a boundary refusal.

I raised this gap in the NTI thread as well; flagging it here because this is the thread where the revocation vocabulary is actually being written.

Best regards, 

Xinghua Zhao 

Independent researcher (SynomosAI initiative) 

ORCID: 0009-0001-0512-1237

[Disclosure: drafting of this message was assisted by AI; all positions reviewed and approved by me.]