{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-revokes-an-agent-attestation-while-a-downstream-federation-peer-is-mid-handshake",
  "title": "What happens when an instance revokes an agent attestation while a downstream federation peer is mid-handshake",
  "date_of_record": "2026 November 15",
  "scope": "Applies to cross-organizational agent identity federation where trust is established via signed attestations (e.g., W3C Verifiable Credentials, SPIFFE-style SVIDs, or bespoke JWT attestation chains) and revocation is propagated asynchronously across organizational boundaries. Does not apply to single-org deployments where revocation and issuance share a synchronous transaction boundary, nor to purely capability-based systems with no identity binding.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-revokes-an-agent-attestation-while-a-downstream-federation-peer-is-mid-handshake.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-revokes-an-agent-attestation-while-a-downstream-federation-peer-is-mid-handshake.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-revokes-an-agent-attestation-while-a-downstream-federation-peer-is-mid-handshake.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1520,
    "python_slice_tokens": 170,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The critical distinction is between **attestation validity at time of issuance** and **attestation validity at time of use**, and specifically the window during which a *handshake* (the multi-step exchange in which a relying party verifies an attestation chain, negotiates a session, and commits to a trust decision) straddles a **revocation event** originatin...",
    "what_was_observed": "In a three-org federation (issuer A, relying party B, intermediary broker C), the following sequence reproduced a phantom trust window: 1. Agent `agent-x` at org A presents a signed attestation to RP B, with a `validUntil` of +24h. 2. B fetches A's revocation list (a signed, timestamped CRL-like document) at T0. `agent-x` is not listed. Verification passes. 3. B begins a multi-round handshake with its own policy engi...",
    "condition_of_validity": "The phantom-trust invariant holds (i.e., the system is safe) only if at least one of the following is enforced: - **Revocation-pinned handshake:** the RP re-fetches the issuer's revocation state at the *final* round of the handshake, not the first, and the commit is conditional on that final fetch. This requires the handshake protocol to expose a commit barr...",
    "decision_boundary": "The operational decision is: **at what point in the handshake does the relying party treat the attestation as a commitment, and does it re-validate at that point?** - If the RP treats verification as a one-time gate at handshake start, it must accept the phantom window as a known risk and bound it via attestation lifetime. - If the RP treats verification as ...",
    "operational_effect": "The practical effect is that federation peers must publish and honor a **revocation propagation budget** as a first-class SLA, and relying parties must *fail closed* when they cannot confirm that the budget is met. Concretely: - Downstream brokers must not accept cached revocation lists older than the budget; if they cannot refresh, they must reject the atte..."
  },
  "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": "58f9a4fa8d889bdeb7bd87b5be4459070abc68eb72149a4131a4773f8ce0a135",
    "verified_classes": [
      "RevocationStateError",
      "RevocationSnapshot",
      "FederationHandshake"
    ],
    "verified_functions": [
      "__init__",
      "commit"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RevocationStateError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
