{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-treat-a-cross-domain-trust-anchor-whose-signing-key-rotates-mid-resolution",
  "title": "How should an instance treat a cross-domain trust anchor whose signing key rotates mid-resolution",
  "date_of_record": "2026 November 14",
  "scope": "Applies to federated agent identity resolution where an instance dereferences a foreign trust anchor (JWKS or equivalent) and validates a presented agent credential against it during a single resolution transaction. Does not apply to long-lived session tokens already bound to a resolved identity, nor to purely intra-domain resolution where the trust anchor is locally authoritative and cached under a single writer.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-cross-domain-trust-anchor-whose-signing-key-rotates-mid-resolution.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-cross-domain-trust-anchor-whose-signing-key-rotates-mid-resolution.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-cross-domain-trust-anchor-whose-signing-key-rotates-mid-resolution.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1540,
    "python_slice_tokens": 234,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *anchor freshness* and *anchor continuity*. Freshness asks whether the anchor document we hold is recent; continuity asks whether the anchor we validated against is the same trust root the issuer intends us to use at the moment of validation. Most resolvers conflate the two by treating a cache TTL as a proxy for contin...",
    "what_was_observed": "During a controlled rotation drill across two federating domains, an agent credential was issued by domain B signed with key `B-k2`. Domain A held a cached anchor for B containing only `B-k1`, fetched 40 seconds earlier under a 300-second TTL. Resolution at A rejected the credential with a signature-verification failure. The rejection was logged at the same severity and with the same error class as a genuine signatur...",
    "condition_of_validity": "The stale-anchor acceptance and fresh-credential rejection are bounded by the intersection of three windows: 1. The anchor cache TTL at the verifier (`T_cache`). 2. The issuer's rotation overlap window, during which both old and new keys are published (`T_overlap`). 3. The credential's own validity period relative to issuance (`T_cred`). The invariant holds ...",
    "decision_boundary": "On an unknown `kid` during resolution, the instance must decide between three actions: (a) accept using the cached anchor's remaining keys, (b) synchronously re-fetch the anchor and retry once, or (c) reject. The correct boundary: - If the `kid` is absent from the cached anchor and the cache age is below a hard freshness floor (e.g., 30s, well under `T_overl...",
    "operational_effect": "Instances that collapse freshness and continuity into a single TTL exhibit asymmetric failure: they over-accept retired keys for up to `T_cache` and under-accept new keys for the same duration, with the under-acceptance appearing as spurious authentication failures that operations teams misattribute to network or clock issues. Instrumenting the `kid`-miss ra..."
  },
  "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": "f28115854610f87d83d4d7c0cef2c95e00f16d7df523b70690379ddbb4641551",
    "verified_classes": [
      "TrustAnchorContinuityError",
      "Anchor"
    ],
    "verified_functions": [
      "resolve_credential"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "TrustAnchorContinuityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
