Direct answer
Cross Agent Delegation, in this implementation guide, is limited to the following inspected scope. Delegation, impersonation, subject and actor token roles, validation inputs, and an actor chain representation. The answer carries the source boundaries forward and does not infer authority from a neighboring topic.
Implementation guide
Translate the source-backed rule into inspectable inputs, state transitions, outputs, and refusal conditions.
Local code can demonstrate behavior, but it cannot supply independent assurance or prove the surrounding deployment is configured correctly.
Applied scope: Delegation, impersonation, subject and actor token roles, validation inputs, and an actor chain representation.
Definition and operating context
The canonical concept owner is maha-strategies. This route may apply authority; it cannot redefine or inherit the authority of its canonical owner.
This property may publish bounded explanations, operational guides, commercial entry points. It must not publish research-source duplication or unreleased evidence claims.
Evidence and exact locators
OAuth 2.0 Token Exchange — §1.1; §2.1 subject_token and actor_token; §4.1 act claim. Establishes: Delegation, impersonation, subject and actor token roles, validation inputs, and an actor chain representation.
What the evidence does not establish
Token exchange does not prove authorization policy quality, downstream enforcement, revocation propagation, agent identity, or a Maha deployment.
This route must not claim research-source duplication.
This route must not claim unreleased evidence claims.
Related definitions and applications
same-topic-application: https://www.mahastrategies.com/clearing/agent-governance/cross-agent-delegation/definition
graphEdges: https://www.mahastrategies.com/clearing/agent-governance/identity-bound-agents/definition
same-topic-application: https://www.mahastrategies.com/clearing/agent-governance/cross-agent-delegation/threats
same-topic-application: https://www.mahastrategies.com/clearing/agent-governance/cross-agent-delegation/controls
property-home: https://www.mahastrategies.com/
same-topic-application: https://www.mahastrategies.com/clearing/agent-governance/cross-agent-delegation/architecture
Questions this page can answer
What does Cross Agent Delegation mean in this bounded context?
Cross Agent Delegation, in this implementation guide, is limited to the following inspected scope. Delegation, impersonation, subject and actor token roles, validation inputs, and an actor chain representation. The answer carries the source boundaries forward and does not infer authority from a neighboring topic.
Which inspected sources support this implementation answer?
OAuth 2.0 Token Exchange (RFC 8693, January 2020), at §1.1; §2.1 subject_token and actor_token; §4.1 act claim, supports delegation, impersonation, subject and actor token roles, validation inputs, and an actor chain representation.
What does the evidence not establish?
Token exchange does not prove authorization policy quality, downstream enforcement, revocation propagation, agent identity, or a Maha deployment. Property boundary: This route may apply authority; it cannot redefine or inherit the authority of its canonical owner.
Which definition or canonical owner must be read first?
This page is the local maha-strategies definition for its topic. Related applications may depend on it but may not silently redefine it.
What source, policy, implementation, or release change would require revision?
Re-evaluate this page when a cited source, locator, governing instrument, local implementation, or canonical definition changes. Publication also requires a matching exact-revision review and active canonical release.