From c2675c934bb6c36900fe1533cc05be639d70ec1f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20CORTIER?= Date: Tue, 27 Oct 2026 02:41:42 +0900 Subject: [PATCH] docs(agent): let authorities coalesce last-seen writes A busy agent channel made an authority write `last_seen_at` for every message. An authority may now write later agent messages at most once every 5 seconds per stream, so `last_seen_at` trails the latest message by at most 5 seconds and never moves back. Changelog: ignore Issue: DGW-478 Co-Authored-By: Claude Opus 5.5 --- docs/agent-identity/INTENT.agent-identity.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/agent-identity/INTENT.agent-identity.md b/docs/agent-identity/INTENT.agent-identity.md index 18dfe8b0a..8e2763815 100644 --- a/docs/agent-identity/INTENT.agent-identity.md +++ b/docs/agent-identity/INTENT.agent-identity.md @@ -134,7 +134,8 @@ Not intended: ### Configuration and metadata - `last_seen_at` moves only on actions that prove current possession of the device key; an enrollment replay and a stream closure prove none. - Creating the identity initializes it; every accepted renew, confirm (including an already-current retry) and check-in, every authenticated `Hello`, and every later agent message on an authenticated stream sets it to the authority's current time. + Creating the identity initializes it; every accepted renew, confirm (including an already-current retry) and check-in, and every authenticated `Hello`, sets it to the authority's current time. + Later agent messages on an authenticated stream also set it, but an authority may write them at most once every 5 seconds per stream, so that a busy channel does not write for every message; `last_seen_at` then trails the latest message by at most 5 seconds and never moves back. - Check-in is only a fallback for configuration and renewal requests while no channel is working. Features that need server push require the agent channel. - An enrollment token gives an identity no config by default.