{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-cross-org-agent-federation-fail-to-bootstrap-trust-when-both-parties-hold-valid-verifiable-credentials",
  "title": "Why does an instance of cross-org agent federation fail to bootstrap trust when both parties hold valid verifiable credentials",
  "date_of_record": "2026 November 11",
  "scope": "Applies to federated agent-to-agent trust establishment where each organization issues W3C Verifiable Credentials (VCs) under its own DID, and policy is exchanged as signed JSON (e.g., a policy VC or signed policy document). Does not apply to single-issuer PKI with a shared trust root, nor to symmetric pre-shared-key federation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-cross-org-agent-federation-fail-to-bootstrap-trust-when-both-parties-hold-valid-verifiable-credentials.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-cross-org-agent-federation-fail-to-bootstrap-trust-when-both-parties-hold-valid-verifiable-credentials.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-cross-org-agent-federation-fail-to-bootstrap-trust-when-both-parties-hold-valid-verifiable-credentials.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1312,
    "python_slice_tokens": 175,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A **credential that verifies** is not the same as a **credential that authorizes this peer to speak for its org in this context**. Verification answers \"did the holder's key sign this, and is the issuer's DID document resolvable?\" Bootstrapping answers \"am I willing to treat this issuer as an authority for *this* class of claims, *right now*, for *this* coun...",
    "what_was_observed": "Two orgs, A and B, each run an agent gateway that (1) presents a VC binding its agent DID to its org DID, (2) presents a signed policy document declaring which counterparty org DIDs it will accept, and (3) requires the peer to do the same. In the failing case: - A resolves B's DID document, validates B's VC signature, and confirms the policy signature. Result: `verified: true`. - B does the same for A. Result: `verif...",
    "condition_of_validity": "The deadlock is guaranteed (not merely possible) whenever **both** of the following hold: 1. **Mutual admission is required before either side grants.** Each gateway's policy check for \"grant peer authority\" requires the peer's org DID to already be in a local allow-list that is populated only by an explicit operator action or by a prior successful federatio...",
    "decision_boundary": "Distinguish two states that telemetry conflates: - **`verified`** — signatures check out, issuers resolve, policy documents are well-formed and signed. This is a *cryptographic* predicate. It is cheap, local, and symmetric. - **`admitted`** — the local authority set contains the peer's org DID for the relevant claim class. This is a *policy* predicate. It is...",
    "operational_effect": "Systems that miss this boundary exhibit: green crypto-layer health checks with zero successful federations; identical generic errors on both sides that point operators at the wrong layer; retry storms that never converge because no amount of re-verification changes an allow-list; and, after a human adds one side's DID manually, a sudden \"spontaneous\" recover..."
  },
  "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": "1a43572eab2b04f1a117bd88a6dc530c9bc9aa42358d58aa0f99bbdbed16148d",
    "verified_classes": [
      "FederationBootstrapError"
    ],
    "verified_functions": [
      "establish_federation"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "FederationBootstrapError"
    ],
    "sample_fail_closed_invariants": [
      "peer VC failed signature/issuer verification",
      "peer policy failed signature verification"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}