docs(spec): clarify in-task authorization scope semantics - #2081
Open
muscariello wants to merge 1 commit into
Open
docs(spec): clarify in-task authorization scope semantics#2081muscariello wants to merge 1 commit into
muscariello wants to merge 1 commit into
Conversation
Add §7.6.4 to explicitly state that TASK_STATE_AUTH_REQUIRED is a coordination signal, not an authorization grant. The A2A protocol does not define the scope, representation, validity, or revocation semantics of the authorization decision or credential obtained in response to this state. Agents MUST NOT treat the state transition itself as authorization for any particular operation; implementations are responsible for defining how the authorized operation is identified and verified before execution. Signed-off-by: Luca Muscariello <muscariello@ieee.org>
mikeas1
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
This improves spec clarity around what is in scope in the A2A core protocol for authorization semantics and reduces implementer ambiguity.
Changes
Fixes #2080