A2A Delegation

Carry authority through every agent handoff.

Bind delegated work to its original purpose, intended recipient and final action before the receiving executor admits it.

Architecture illustration. Coverage follows the configured integration and execution boundary.

Where the action needs a decision

A receiving agent may be authenticated without being authorised to carry out every request from another agent. Context can be lost or expanded as work passes between agents and tools.

01

Bind the delegation

Associate the initiating actor, purpose, intended receiver and permitted action with the delegation context.

02

Check at the receiver

At a supported receiving boundary, verify expiry, replay state, delegation and destination before allowing the side effect.

03

Retain the chain

Preserve the action decision and source-labelled outcome evidence so a reviewer can follow the handoff to the executor.

Build a testable deployment.

The Action Passport model binds exact-action authority to a short-lived, single-use decision. Keep the receiver’s own identity and destination permissions authoritative, and reject a changed action rather than reusing approval for a different request.

See the decision before the action.

Try a local scenario, then bring your workflow to a deployment review. Start with one agent and one tool, and see exactly where the action can be stopped.