01 / The operating case
What changes in a real workflow?
A procurement agent in tenant A delegates a vendor update to an agent in tenant B.
- 01Origin grant
- 02Parent agent
- 03Narrow child grant
- 04Action boundary
02 / Decision contract
What the executor must check
Authenticate each tenant and agent, bind resource ownership, data-sharing purpose, operation and receiving audience in a bounded grant.
03 / Failure and evidence
What goes wrong, and what can be proven?
Tenant B accepts A’s task text and uses its own broad vendor privileges without cross-tenant consent.
Both tenant IDs, grant, consent or contract reference, decision and vendor change.
04 / Canonical scope
Why this reference stands alone
Cross-runtime delegation can be same tenant; this page owns organizational boundary and data scope.
Technical artifact
Tenant boundary requires two-sided context
tenant A task: update vendor V4 tenant B agent: vendor-service/B A grant audience: B, vendor V4, address only B resource policy: A may request address update change bank account → DENY
Run the denial test
Change the recipient tenant or target field after the handoff. The receiving system must enforce its own resource policy and the sender’s narrower grant.
Primary references