Topic
Everything we've written on this topic, newest first.
12 October 2026 · 5 min read
The relying party is whichever bank, hospital or office is about to act on an agent's request. It should make six checks in order, covering a signed and unrevoked identity, an accountable owner, scope for this exact action, a narrowing delegation chain, data-protection status and written evidence. If a check fails, it says no.
3 October 2026 · 5 min read
Running an agent on a phone settles where the data is processed. It doesn't settle who the agent is when it calls a bank or a hospital, who handed it authority, or when that authority ends. A general design for the edge gives each agent its own key and a short-lived, user-approved delegation.
19 September 2026 · 5 min read
The industry is standardising how agents talk to each other and to tools. It is not standardising where an agent runtime keeps conversation data or how long it stays. That is each vendor's choice. Before adopting a runtime, ask four plain questions about location, retention, erasure and who carries the legal risk.
19 September 2026 · 5 min read
In a Harness report released in September 2026, 76% of respondents believed they could disable a misbehaving agent within 15 minutes, but only 33% had an instant kill switch. We think the gap starts earlier than the switch. An agent that shares a key with nine others has no name to revoke.
18 September 2026 · 6 min read
A read-only label says what an agent may do. It doesn't say which agent acted, who answers for it, or how to stop that one without stopping the rest. The DseWiki case, as researchers and reporters describe it, shows the gap. Scope belongs on a credential. Identity is a name you can revoke.
