{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-trusted-agent-fail-to-bootstrap-trust-across-organizational-boundaries-when-its-attestation-chain-is-cryptographically-valid",
  "title": "Why does an instance of a trusted agent fail to bootstrap trust across organizational boundaries when its attestation chain is cryptographically valid but its issuer's trust root is not anchored in the verifier's policy graph",
  "date_of_record": "2026 November 16",
  "scope": "Applies to cross-org agent-to-agent authentication where identity is established via signed attestations (e.g., SPIFFE/JWT-SVID-style bundles, W3C Verifiable Credentials, or custom delegation chains) and the verifier evaluates those attestations against a *local* trust policy graph. Does not apply to same-org deployments where issuer and verifier share a single trust anchor, nor to cases where the attestation itself is cryptographically broken (signature failure, expiry, malformed claims) — those are simpler, well-understood rejection modes.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-trusted-agent-fail-to-bootstrap-trust-across-organizational-boundaries-when-its-attestation-chain-is-cryptographically-valid.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-trusted-agent-fail-to-bootstrap-trust-across-organizational-boundaries-when-its-attestation-chain-is-cryptographically-valid.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-trusted-agent-fail-to-bootstrap-trust-across-organizational-boundaries-when-its-attestation-chain-is-cryptographically-valid.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1953,
    "python_slice_tokens": 522,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A cryptographically valid attestation chain proves *who signed what, in what order*. It does not prove that the verifier has any reason to care about the signer. These are two separate predicates: 1. **Chain integrity** — every signature in the delegation path verifies against its parent, the leaf subject matches the claimed agent identity, and no claim has ...",
    "what_was_observed": "During a multi-org agent federation rollout, Org B's verifier rejected Org A's agent attestations with a generic `attestation_untrusted` error despite: - The JWT-SVID chain verifying cleanly against Org A's published JWKS. - The leaf SVID carrying the correct SPIFFE ID (`spiffe://org-a.example/agent/worker-7`). - Org A's JWKS being fetchable and well-formed. - Both orgs having *verbally* agreed to federate the previo...",
    "condition_of_validity": "The bootstrap succeeds only when all of the following hold simultaneously: 1. The verifier's policy graph contains a trust anchor whose issuer identity matches the root of the presented chain (byte-equal after canonicalization — beware trailing slashes, case, and port normalization in SPIFFE IDs). 2. The anchor's scope predicate (path glob, audience restrict...",
    "decision_boundary": "The operational decision is: **on rejection, do you retry, escalate to a human, or fail closed permanently?** - If the failure is *anchor-absent* or *anchor-scope-mismatch*, retrying is futile — the policy graph is static within its refresh cycle. Escalate to the federation operator with the specific missing anchor identifier. Do not loop. - If the failure i...",
    "operational_effect": "The practical consequence is that cross-org trust bootstrapping is a **two-party, out-of-band provisioning problem masquerading as a runtime authentication problem.** No amount of cryptographic correctness on the presenting side closes the gap; only the verifier's policy graph changing does. This means: - Federation onboarding must include a *policy-graph co..."
  },
  "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": "849508f5ec3fea4d0b3b45b13b49370fe994f1cc16a23de51674d65587de6363",
    "verified_classes": [
      "TrustBootstrapError",
      "TrustAnchor",
      "PresentedChain",
      "Reason"
    ],
    "verified_functions": [
      "_canonicalize",
      "_glob_matches",
      "bootstrap_trust",
      "__init__"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "TrustBootstrapError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
