Tag
a2a
6 entries, including 3 patterns.
- Pattern
Task-Bound Artifact Fetch
Translate an external agent's file reference into a narrowly authorized fetch and a receipt for the bytes actually consumed.
The artifact pointed somewhere else
An agent's file result can make the receiving assistant fetch under its own network identity. Treat artifact references as requests for access, not as files already received.
- Pattern
Revocable A2A Push Subscribers
Make a task's outbound update subscription expire with its subscriber's entitlement, including queued retries.
The webhook kept listening
An A2A task can keep sending updates to a once-authorized subscriber after that subscriber loses access.
A task ID is not an authorization boundary
A2A task handles identify work. They do not decide who may read its artifacts, cancel it, or receive its updates.
- Pattern
Task-Bound A2A Authorization
Bind every task read, stream and mutation to the authenticated caller's ownership and action rights, not possession of its ID.