{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-cross-org-agent-federation-deadlock-when-trust-score-routing-and-policy-negotiated-capability-exchange-are-applied-to-a-mutual",
  "title": "Why does an instance of cross-org agent federation deadlock when trust-score routing and policy-negotiated capability exchange are applied to a mutually-recursive delegation cycle",
  "date_of_record": "2026 November 15",
  "scope": "This record applies to federated agent meshes where (a) routing decisions are gated by a scalar trust score computed per-origin, and (b) capability grants are negotiated pairwise via a policy handshake that itself requires a capability (the \"policy-evaluation\" capability) to be present on the responding peer. It does not apply to single-org meshes, nor to federations using pre-shared static capability manifests, nor to routing schemes that ignore trust scores.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-cross-org-agent-federation-deadlock-when-trust-score-routing-and-policy-negotiated-capability-exchange-are-applied-to-a-mutual.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-cross-org-agent-federation-deadlock-when-trust-score-routing-and-policy-negotiated-capability-exchange-are-applied-to-a-mutual.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-cross-org-agent-federation-deadlock-when-trust-score-routing-and-policy-negotiated-capability-exchange-are-applied-to-a-mutual.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2355,
    "python_slice_tokens": 538,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction is between **capability negotiation as a prerequisite for routing** and **capability negotiation as a consequence of routing**. In a federation with policy-negotiated capability exchange, a request to org B for capability `X` triggers a negotiation round: A presents its policy, B evaluates it, B returns a grant or counter-offer, and A accepts...",
    "what_was_observed": "Observed on a mesh of 11 orgs, 4 of which were newly onboarded. New peers exhibited a stable pattern: every outbound delegation to a new peer was admitted at the transport layer, rejected at the trust-router admission gate with reason `TRUST_BELOW_ROUTE_THRESHOLD`, and the negotiation request was never emitted. The trust score for new peers sat at its initialization value (`0.0` in this deployment; some deployments u...",
    "condition_of_validity": "The deadlock manifests if and only if all four of the following hold simultaneously: - **C1 (cold-start gate).** The trust router enforces a threshold `θ > init_score` on *all* outbound traffic, including negotiation traffic. If negotiation traffic is exempted (a \"bootstrap class\" of requests), no cycle exists. - **C2 (history-derived trust).** The trust sco...",
    "decision_boundary": "The correct engineering response is to **break the cycle at exactly one point, chosen deliberately, and to make the break explicit in the admission policy rather than emergent in the code.** Three viable break points, in order of preference: 1. **Exempt negotiation traffic from the trust gate (break C1).** Negotiation requests are admitted under a distinct \"...",
    "operational_effect": "When the cycle is present and unbroken: - New peers reach steady-state trust of exactly `init_score` and never move. Dashboards show flat lines, not errors. - Chained delegations fail at the first hop whose counterparty lacks a trust history, with error attributed to the wrong hop. - Manual trust seeding becomes an undocumented operational dependency, and it..."
  },
  "matched_failure_symptoms": [
    "SQLITE_BUSY_OR_DEADLOCK"
  ],
  "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": "151cbf39d5df427708f0fb4a8f3abbe55fa8892aa6e742b7fae148e947c209be",
    "verified_classes": [
      "FederationCycleError",
      "FederationPolicy"
    ],
    "verified_functions": [
      "_reachable",
      "validate_federation_policy",
      "admit_request"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "FederationCycleError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
