{"version":"2.1.251","anchor":"permission-forwarding-between-agents-records-why-it-failed","canonical_anchor":"permission-forwarding-between-agents-records-why-it-failed","heading":"Permission forwarding between agents records why it failed","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/permission-forwarding-between-agents-records-why-it-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Permission forwarding between agents records why it failed\n\nCross-agent permission relays log mismatched or unbound verdicts with their own labels.\n\n**What**\n\nWhen one agent relays a tool permission decision to another, the outcome is now recorded in more detail than success or mailbox failure: a denial or approval that does not match what was asked for, and a verdict that was never bound to a request, each get their own label.\n\n**Evidence**\n\n`verdict_unbound`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}