{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-a-federated-revocation-as-authoritative-before-it-has-received-the-revocation-itself",
  "title": "Under what conditions must an instance treat a federated revocation as authoritative before it has received the revocation itself",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agents and gateways that accept credentials minted by a foreign trust domain and cache authorization decisions derived from them. Does not apply to same-domain revocation, which is synchronous and covered by the local control plane.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-federated-revocation-as-authoritative-before-it-has-received-the-revocation-itself.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-federated-revocation-as-authoritative-before-it-has-received-the-revocation-itself.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-federated-revocation-as-authoritative-before-it-has-received-the-revocation-itself.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1590,
    "python_slice_tokens": 291,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The intuitive model is that revocation is an event: domain A revokes agent X, publishes the revocation, and every relying party in domain B that sees the revocation stops honoring X. The failure mode lives in the gap between *revocation issuance* and *revocation observation* — the propagation window. The non-obvious boundary is this: an instance that has not...",
    "what_was_observed": "In a three-domain federation (A issues, B and C rely), A revoked a compromised agent identity at epoch 4410. B's revocation feed was healthy and applied the revocation within 90 seconds. C's feed was partitioned from A's revocation topic for 41 minutes due to a cross-org network policy change. During that window, C continued to admit the agent. The interesting observation is what happened at the *relying-party cache ...",
    "condition_of_validity": "The rule \"unobserved revocation may be treated as non-revocation\" is valid only when all three hold: 1. The relying party's decision cache TTL is strictly less than the issuer's revocation-propagation SLO. If B caches decisions for 15 minutes and A promises revocation propagation in 5 minutes, B's cache can outlive the revocation and the rule is violated by ...",
    "decision_boundary": "At the boundary, the relying party must choose between **fail-open** (admit on unobserved revocation) and **fail-closed** (deny on unobserved revocation). The correct choice is determined by the credential's liveness binding, not by risk appetite: - Credential carries a fresh issuer-signed heartbeat (epoch within skew): **deny** on heartbeat absence. Absence...",
    "operational_effect": "Implementing the discriminator changes the failure profile from *silent over-admission during partition* to *bounded re-validation latency during partition*. In the incident above, adding a signed epoch watermark to the revocation feed and keying decision caches by `(issuer, jti)` would have reduced C's exposure from 41 minutes to the watermark staleness thr..."
  },
  "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": "3d7ccfaa2224ca1a5cc859a6e9ba2cbea9762d3737d10cdbb8c135411d7b8759",
    "verified_classes": [
      "UnprovableLivenessError",
      "Credential",
      "FeedState"
    ],
    "verified_functions": [
      "evaluate_foreign_credential",
      "admit_or_raise"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnprovableLivenessError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
