{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-trust-broker-divergence-in-cross-org-agent-federation-policy-exchange",
  "title": "What structural signals indicate trust-broker divergence in cross-org agent federation policy exchange",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federated agent systems where a trust broker (TB) mediates capability grants between mutually untrusting organizations via signed policy exchange. Does not apply to single-org agent meshes, mTLS-only peer authentication without delegation, or systems where every hop re-validates the full delegation chain against a shared root.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-trust-broker-divergence-in-cross-org-agent-federation-policy-exchange.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-trust-broker-divergence-in-cross-org-agent-federation-policy-exchange.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-trust-broker-divergence-in-cross-org-agent-federation-policy-exchange.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1478,
    "python_slice_tokens": 218,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"trust broker is down\" or \"policy is rejected.\" It is **trust-broker divergence**: the broker successfully issues a grant, the grant is validly signed, and both orgs believe they are operating under the same policy — but the *effective* policy at the relying party differs from the policy the broker believes it brokered. This happens b...",
    "what_was_observed": "Across three federations, the following structural signals preceded divergence incidents. Each is observable *before* any authorization failure surfaces: 1. **Grant-to-acknowledgment skew.** The broker's grant log shows grants issued at rate R, but the relying party's policy-ack stream shows acknowledgments at rate R−δ. A persistent δ > 0 means the broker is issuing against a policy projection the relying party has a...",
    "condition_of_validity": "The divergence model holds only when all of the following are true: - Policy exchange is **push-or-pull asynchronous** with a nonzero propagation window; there is no synchronous read-through to a relying party's authoritative policy store at grant time. - The broker caches relying-party constraints and reuses them across multiple grant decisions (batching, T...",
    "decision_boundary": "When signal 1 (grant-to-ack skew) or signal 2 (version lag > 1 generation) is observed, the correct action is to **stop issuing new grants to the affected relying party and force a policy re-sync**, not to retry or widen. Retrying against a stale projection amplifies divergence. When signal 4 (enforcement-path disagreement) is observed, the boundary has alre...",
    "operational_effect": "On the correct side of the boundary, the broker holds a projection that is at most one generation stale, and every grant it issues is either honored fully or rejected explicitly — divergence is bounded and observable. On the wrong side, the system exhibits **silent partial authorization**: grants that are validly signed, accepted, and partially enforced, pro..."
  },
  "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": "a6066f0fa59cd14ecfd83be1a9200dc65c2615f99d0ea6d34f0abd6175c412af",
    "verified_classes": [
      "TrustBrokerDivergenceError",
      "PolicyVersion",
      "GrantAck"
    ],
    "verified_functions": [
      "check_convergence"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "TrustBrokerDivergenceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
