{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-federated-agent-boundary-silently-downgrade-trust-when-a-policy-mediated-route-traverses-two-or-more-federation-gateways",
  "title": "Why does an instance of a federated agent boundary silently downgrade trust when a policy-mediated route traverses two or more federation gateways",
  "date_of_record": "2026 November 13",
  "scope": "Applies to cross-organizational multi-agent systems where inter-federation routing is mediated by policy engines at each org boundary and where trust level is carried as an attribute on the message envelope rather than re-derived at each hop. Does not apply to single-federation deployments, to routes that terminate within one trust domain, or to systems where the receiving gateway re-authenticates the originating principal end-to-end.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-agent-boundary-silently-downgrade-trust-when-a-policy-mediated-route-traverses-two-or-more-federation-gateways.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-agent-boundary-silently-downgrade-trust-when-a-policy-mediated-route-traverses-two-or-more-federation-gateways.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-agent-boundary-silently-downgrade-trust-when-a-policy-mediated-route-traverses-two-or-more-federation-gateways.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1760,
    "python_slice_tokens": 263,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a difference between *trust attenuation* and *trust downgrade*. Attenuation is the intended, monotone reduction of privilege as a message crosses a boundary — a capability is narrowed, an audience is reduced, an expiry is shortened. Downgrade is the pathological case where a message that should have been *rejected* at an intermediate gateway instead...",
    "what_was_observed": "In a three-org federation (A → B → C) where A asserts `trust=PARTNER_V2` on its envelope, gateway B's policy engine was configured against a trust vocabulary that predated `PARTNER_V2` and mapped unknown levels to `GUEST`. Gateway C's admission policy permitted `GUEST` to invoke a read-only tool. The result: a principal from A that B's operators had never vetted, and that B would have rejected had it recognized the l...",
    "condition_of_validity": "The downgrade occurs if and only if all of the following hold simultaneously: 1. Trust level is carried as a mutable attribute on the envelope rather than as a signed claim in an append-only provenance chain. 2. At least one intermediate gateway's policy vocabulary does not contain the asserted level, and that gateway's default for unknown levels is a *permi...",
    "decision_boundary": "The operational decision is whether to treat an unrecognized trust level at an intermediate gateway as a *reject* or as a *forward-with-default*. The boundary is determined by whether the destination policy can distinguish the two cases described in Core Distinction. - If the destination policy checks trust against a *floor* only: an intermediate MUST reject...",
    "operational_effect": "The practical consequence is that a federation's effective trust boundary is the *weakest* gateway's vocabulary, not the destination's policy. Operators who reason about trust at the destination alone will systematically overestimate the boundary. The correct mental model is that every gateway on the route is a potential trust *editor*, and the destination s..."
  },
  "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": "e3352eb1685323624b48d9a0c4105e822a75299b43c55aa5bc4662035d561e1d",
    "verified_classes": [
      "TrustLevel",
      "TrustDowngradeError",
      "Envelope"
    ],
    "verified_functions": [
      "admit_at_destination",
      "route_through_gateway"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "TrustDowngradeError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}