{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-federated-agent-trust-anchor-silently-accept-tokens-minted-under-a-superseded-signing-key-during-cross-org-authorization",
  "title": "Why does an instance of a federated agent trust anchor silently accept tokens minted under a superseded signing key during cross-org authorization",
  "date_of_record": "2026 November 18",
  "scope": "Applies to cross-organization agent federation where authorization tokens are verified against a trust anchor document (JWKS-like key set) that is fetched, cached, and rotated out-of-band from the token issuer. Does not apply to single-org deployments with a single static signing key, nor to tokens verified with a pinned public key compiled into the verifier.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-agent-trust-anchor-silently-accept-tokens-minted-under-a-superseded-signing-key-during-cross-org-authorization.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-agent-trust-anchor-silently-accept-tokens-minted-under-a-superseded-signing-key-during-cross-org-authorization.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-agent-trust-anchor-silently-accept-tokens-minted-under-a-superseded-signing-key-during-cross-org-authorization.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2149,
    "python_slice_tokens": 429,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two different questions a verifier can ask about a token, and they are not the same question: 1. *Is this token cryptographically valid under some key I currently trust?* 2. *Was this token validly issued at the moment it was minted, under the key material the issuer was authorized to use at that moment?* Most federation implementations answer only...",
    "what_was_observed": "During a cross-org agent federation incident (red-team exercise, two cooperating orgs, agent A at Org-1 acting on behalf of a user, calling agent B at Org-2), the following sequence was reproduced: - Org-1 rotated its agent-signing key from `K_2024` to `K_2025` at 09:00 UTC. The anchor document published to Org-2 retained `K_2024` with `\"use\":\"sig\"` and no expiry field, under a documented 24-hour grace policy for in-...",
    "condition_of_validity": "The silent-acceptance failure occurs if and only if all of the following hold: 1. The trust anchor retains a superseded key for verification (grace window > 0). 2. The anchor document does not carry a per-key `signing_not_after` (or equivalent issuance-authorization bound) distinct from the key's presence in the set. 3. The verifier does not compare the toke...",
    "decision_boundary": "The correct verifier decision is a conjunction, not a disjunction: The boundary between \"grace window is a safety feature\" and \"grace window is an attack surface\" is precisely the `signing_not_after` bound. Without it, a non-zero grace window is an unbounded issuance-authorization extension for any actor holding the old key. With it, the grace window is boun...",
    "operational_effect": "When the bound is absent, the observable effect is a *latency between compromise and detection* that equals the grace window, not the token TTL. During that latency, every token minted by the stale key is indistinguishable from a legitimate in-flight token. Audit logs show valid signatures, correct `kid`, correct `iss`, plausible `iat`. The only forensic sig..."
  },
  "matched_failure_symptoms": [
    "UNNECESSARY_OR_STALE_EXTERNAL_FETCH"
  ],
  "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": "0010b3a59eaf7aab966393098b85f1d244a231274a072a05ca94bc551ad95d02",
    "verified_classes": [
      "StaleIssuanceAuthorityError",
      "TrustedKey",
      "Token"
    ],
    "verified_functions": [
      "verify_federated_token"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "StaleIssuanceAuthorityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
