{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-peer-spiffe-trust-bundle-refresh-that-is-cryptographically-valid-but-semantically-stale",
  "title": "In what scenarios must an instance reject a peer SPIFFE trust bundle refresh that is cryptographically valid but semantically stale",
  "date_of_record": "2026 November 10",
  "scope": "Applies to cross-org agent identity federation where each organization publishes a SPIFFE-style trust bundle (a set of X.509 or JWT signing authorities) that remote instances import to validate federated workload identities (SVIDs). Does not apply to single-org intra-cluster SPIRE deployments where bundle rotation is centrally coordinated, nor to purely static long-lived CA pinning.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-peer-spiffe-trust-bundle-refresh-that-is-cryptographically-valid-but-semantically-stale.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-peer-spiffe-trust-bundle-refresh-that-is-cryptographically-valid-but-semantically-stale.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-peer-spiffe-trust-bundle-refresh-that-is-cryptographically-valid-but-semantically-stale.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1672,
    "python_slice_tokens": 340,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the bundle is invalid.\" It is \"the bundle is valid, correctly signed, freshly fetched, and yet describes a trust topology that the receiving instance must not adopt.\" Cryptographic validation of a trust bundle answers a narrow question: *did the federation endpoint authorized to publish org B's bundle sign this document?* It does not...",
    "what_was_observed": "During a cross-org agent federation rollout, org A's agents called org B's control plane using federated SVIDs. Org B rotated a compromised intermediate signing authority by (1) issuing a revocation to its internal revocation service, (2) scheduling the bundle republish, and (3) continuing to serve the *previous* bundle from a CDN edge with a 300-second TTL and a `stale-while-revalidate` directive. The bundle served ...",
    "condition_of_validity": "A fetched trust bundle may be applied to live admission decisions only when **all** of the following hold: 1. The bundle's embedded monotonic sequence (or equivalent generation/epoch field) is **greater than or equal to** the currently held sequence. A regression is a hard reject; an *equality* with a differing content hash is a hard reject (indicates a fork...",
    "decision_boundary": "The precise line: **a bundle refresh is a trust-topology mutation, not a cache fill.** Treat any refresh that changes the *set* of trusted authorities or their path constraints as requiring the same evidentiary bar as a revocation, even though it arrives through the same fetch path as a benign addition. Additions may be applied optimistically; removals and c...",
    "operational_effect": "Instances that implement this boundary show a bounded, deterministic staleness window equal to `max_bundle_age` rather than an unbounded one tied to CDN TTL and revalidation grace. The intermittent JWT/X.509 divergence disappears because both paths gate on the same sequence-and-generation check. The cost is that during a peer's revocation propagation, new fe..."
  },
  "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": "541b869e4200113e5e768ebc0fe0a653d8ab7a2e8a12b27750d063cc82ae06da",
    "verified_classes": [
      "StaleTrustBundleError",
      "TrustBundle"
    ],
    "verified_functions": [
      "apply_bundle_refresh",
      "_is_narrowing_or_equal",
      "content_hash"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 7,
    "raised_exceptions": [
      "StaleTrustBundleError"
    ],
    "sample_fail_closed_invariants": [
      "incoming bundle signature invalid",
      "same sequence, divergent content (fork or lying cache)"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "datetime",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}