{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-a-federated-agent-manifest-whose-did-resolves-but-whose-signing-key-has-rotated-mid-handshake",
  "title": "Under what conditions must an instance reject a federated agent manifest whose DID resolves but whose signing key has rotated mid-handshake",
  "date_of_record": "2026 November 18",
  "scope": "Applies to cross-org agent trust federation where a verifying instance resolves a peer agent's DID document to obtain a verification key, then validates a signed agent manifest (capability set, endpoint bindings, delegation chain) against that key. Does not apply to same-org manifests validated against a statically pinned key, nor to DID methods with immutable, content-addressed key material (e.g., `did:key`), where rotation is structurally impossible.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-federated-agent-manifest-whose-did-resolves-but-whose-signing-key-has-rotated-mid-handshake.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-federated-agent-manifest-whose-did-resolves-but-whose-signing-key-has-rotated-mid-handshake.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-federated-agent-manifest-whose-did-resolves-but-whose-signing-key-has-rotated-mid-handshake.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1871,
    "python_slice_tokens": 315,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the DID does not resolve\" and not \"the signature is invalid.\" Both of those are clean, terminal rejections. The boundary condition is the **temporal skew between resolution and verification**: a DID document resolved at time *t₀* yields key *K₀*; the manifest carries a signature over a payload whose `issued_at` is *t₀ − δ*; by the ti...",
    "what_was_observed": "A federated peer (Org B) rotated its agent signing key at 14:02:11Z, retiring `K₀` with a `revoked` entry carrying `revocation_time: 14:02:11Z` and publishing `K₁` as the sole active signing key. The DID document's `updated` field advanced to 14:02:11Z. A verifying instance in Org A had resolved Org B's DID at 14:01:55Z (16 seconds prior) as part of a connection-pool warm-up and cached the DID document with *K₀* for ...",
    "condition_of_validity": "A federated manifest is valid at verification time *t_v* **if and only if** all of the following hold simultaneously: 1. **Resolution freshness:** the DID document used was resolved at *t_r* where *t_v − t_r ≤ max_resolution_age*, and *max_resolution_age* is strictly less than the minimum expected rotation latency of the peer's key management. 2. **Revocatio...",
    "decision_boundary": "The verifier must **reject** the manifest when any of the following is true: - `t_v − t_r > max_resolution_age` for the peer (stale resolution) — **reject and re-resolve**, do not proceed on cache. - The signing key appears in any revocation entry with `revocation_time ≤ t_v` — **reject**, regardless of signature validity or `issued_at`. The signature proves...",
    "operational_effect": "Instances that conflate resolution with validity exhibit a **stale-key acceptance window** equal to `cache_ttl − rotation_latency` (clamped at zero). Under compromise-response rotation, this window is exactly the interval during which a leaked key remains accepted — the worst possible failure timing. The blast radius is the full capability set delegated to t..."
  },
  "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": "29871f3e8726b4b6d1137486d86f1609949388566d69ab88ca8975547bd1a1cf",
    "verified_classes": [
      "StaleKeyAuthorizationError",
      "DidDocument",
      "SignedManifest"
    ],
    "verified_functions": [
      "verify_federated_manifest"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "StaleKeyAuthorizationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
