{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-spiffe-trust-domain-drift-in-agent-to-agent-mutual-tls-before-handshake-failure",
  "title": "What structural signals indicate SPIFFE trust-domain drift in agent-to-agent mutual TLS before handshake failure",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent meshes where each participating organization runs its own SPIRE server and agents authenticate peers via X.509-SVIDs over mTLS, with peer trust established through federated bundles. Does not apply to single-trust-domain deployments, to JWT-SVID-only flows, or to meshes that terminate mTLS at a shared gateway with a single issuing authority.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-spiffe-trust-domain-drift-in-agent-to-agent-mutual-tls-before-handshake-failure.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-spiffe-trust-domain-drift-in-agent-to-agent-mutual-tls-before-handshake-failure.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-spiffe-trust-domain-drift-in-agent-to-agent-mutual-tls-before-handshake-failure.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1560,
    "python_slice_tokens": 225,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure that matters is not \"mTLS handshake fails.\" That is loud, logged, and retried. The failure that matters is **trust-domain drift**: a peer's SVID chain still validates against a bundle the local SPIRE agent holds, but the bundle is stale relative to the peer's actual issuing authority, or the peer's SPIFFE ID has been reissued under a rotated CA t...",
    "what_was_observed": "Across a three-org agent mesh (orgs A, B, C; each with an independent SPIRE server, bundle federation via the SPIFFE bundle endpoint), the following sequence recurred: 1. Org B rotated its upstream CA and reissued all SVIDs with a 1-hour TTL. The new CA was published to its bundle endpoint. 2. Org A's SPIRE agent polls federated bundles on a 5-minute interval but applies them lazily — the new bundle is written to dis...",
    "condition_of_validity": "The distinction holds — i.e., \"chain verifies\" does not imply \"identity is current\" — under these conditions: - The peer rotates SVIDs with overlap (old and new CA both in bundle during transition). Without overlap the failure is loud and this analysis is moot. - Authorization decisions key on the SPIFFE ID *string* rather than on registration-entry identity...",
    "decision_boundary": "The operative rule: **treat a verifying chain as necessary but not sufficient; gate admission on bundle-currency, not chain-validity alone.** Concretely, before admitting a peer SVID: - Compare the peer leaf's `NotBefore` against the local loaded-bundle fetch timestamp. If `NotBefore > bundle_loaded_at`, the verifier is behind the peer's issuance epoch — ref...",
    "operational_effect": "Meshes that adopt bundle-currency gating observe: authorization decisions fail closed during rotation overlap rather than admitting superseded identities; the \"silent re-parenting\" class of confused-deputy incidents disappears because a reissued entry cannot inherit the old entry's admission; and rotation cadence becomes an explicit SLO coupling between orgs..."
  },
  "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": "53d975f34f25f8d98b42980ac91b716405da591cd1b2ef393d4a3b09252f01c3",
    "verified_classes": [
      "TrustDomainDriftError",
      "LoadedBundle",
      "PeerSVID"
    ],
    "verified_functions": [
      "assert_bundle_currency",
      "admit_peer",
      "__init__",
      "__init__"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TrustDomainDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
