- From: <zhaoxinghua07@126.com>
- Date: Fri, 30 Oct 2026 11:02:11 -0000
- To: public-agentprotocol@w3.org
- Cc: abisheakp197@gmail.com, llewis@sovrlabs.com, alanhkarp@gmail.com, lars@moltrust.ch, tima@aeoess.com, lee@aicent.com
Colleagues,
On 30 October I proposed a `resume_basis` field in this thread (archived as message 0107): a field that states what a resuming agent's identity decision rests on, so that a receiver can distinguish "signature verified" from "delegation still valid at resume time" before deciding.
Worked example of the two outcomes (illustrative, not a lab run). One clarification: message 0107 framed `resume_basis` as a closed enumeration (`evidence | exemption`); the example below carries the delegation state the resuming agent relied on — an extension of that same idea, and whether to keep the enum, the object form, or both is exactly what the agenda slot would settle:
# as shipped today
{ "sub": "agent-77", "resume_token": "...", "sig": "valid" }
receiver: signature verifies -> RESUMED
# T1 failure: an upstream delegation may already be revoked
# with resume_basis
{ "sub": "agent-77", "resume_token": "...", "sig": "valid",
"resume_basis": { "delegation_id": "d-42",
"state_at_resume": "REVOKED" } }
receiver: basis says REVOKED -> decline the resume
# T2: fail closed instead of fail open
What I am asking the AIW#3 agenda for is procedural, not a new claim: a short slot to adopt, amend, or reject `resume_basis` on the record. A proposal that is neither adopted nor rejected by the session tends to die of silence, which is the worst outcome for everyone implementing receivers.
If the team prefers to settle it before the session, a written adopt / amend / reject on this thread before 6 November works just as well.
Xinghua Zhao
Disclosure: I participate under the Individual CLA, not on behalf of any organisation, and I hold no commercial interest in the outcome of this request.
Received on Friday, 30 October 2026 11:02:46 UTC