{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-delegated-authority-from-transitive-trust-in-cross-org-multi-agent-federation",
  "title": "How should an instance distinguish delegated authority from transitive trust in cross-org multi-agent federation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to federated multi-agent systems where an agent in org A negotiates a trust boundary with an agent in org B, and a third agent in org C subsequently requests an action whose justification traces back through that negotiation. Does not apply to single-org agent meshes, nor to federation where every hop re-authenticates against the original principal's credential directly (no delegation chains).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-delegated-authority-from-transitive-trust-in-cross-org-multi-agent-federation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-delegated-authority-from-transitive-trust-in-cross-org-multi-agent-federation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-delegated-authority-from-transitive-trust-in-cross-org-multi-agent-federation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1255,
    "python_slice_tokens": 155,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary failure is the conflation of *delegated authority* with *transitive trust*. Delegated authority is a grant: principal P in org A authorizes agent A1 to act on P's behalf for scope S, and A1 may (or may not) be permitted to re-delegate a subset of S. Transitive trust is a property of the *channel*: A1 trusting B1's assertions about identity does ...",
    "what_was_observed": "In a three-org federation (A: data owner, B: orchestrator, C: compute provider), the negotiation between A and B succeeded with scopes `{read:dataset-7, summarize}`. B then negotiated with C, presenting a capability token that C validated against A's published trust root. C executed a `read:dataset-7` on B's instruction and returned derived summaries to B, which forwarded them to A. No error was raised at any hop. Th...",
    "condition_of_validity": "The distinction holds whenever authority can be *re-derived* at a hop that did not participate in the original negotiation. If every action is authorized by a fresh challenge to the original principal (no bearer tokens, no cached grants, no capability forwarding), delegation depth is irrelevant and this record does not apply. Conversely, the moment any hop c...",
    "decision_boundary": "An instance should treat a negotiation response as *insufficient to authorize a downstream hop* unless it carries an explicit, per-scope delegation depth, and should refuse to forward any grant whose depth is absent rather than inferring a default. The decision rule: if the requesting agent's justification chain has length > 1 and the terminal grant lacks a ...",
    "operational_effect": "Enforcing mandatory depth converts a silent over-grant into a loud negotiation failure at the boundary where intent is still known, which is the only point at which the failure is recoverable. The cost is that legacy peers fail closed and require renegotiation; the benefit is that audit no longer discovers redelegation after the fact. In practice, instances ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "bddda3a7cd82facacfc96c59677aadaefcb7df9626874695010eefbc5de16a01",
    "verified_classes": [
      "DelegationDepthError",
      "Grant"
    ],
    "verified_functions": [
      "forward_grant",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "DelegationDepthError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
