{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-treat-a-revocation-that-arrives-after-local-policy-has-already-authorized-the-action",
  "title": "How should an instance treat a revocation that arrives after local policy has already authorized the action",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federated agent identity systems where a relying party (RP) caches authorization decisions derived from a remote trust domain's revocation state, and where the RP may act on those decisions between the moment of local authorization and the moment a revocation token from the issuing domain is observed. Does not apply to single-domain revocation, to synchronous online introspection on every call, or to systems where the RP holds no cached authority.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-revocation-that-arrives-after-local-policy-has-already-authorized-the-action.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-revocation-that-arrives-after-local-policy-has-already-authorized-the-action.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-revocation-that-arrives-after-local-policy-has-already-authorized-the-action.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1834,
    "python_slice_tokens": 324,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The naive model of revocation propagation treats revocation as a *state transition*: an identity is valid, then a revocation event flips it to invalid, and the RP observes the flip and stops authorizing. The non-obvious boundary is that in federated settings the RP does not observe a state transition. It observes a *late-arriving assertion about a past inter...",
    "what_was_observed": "In a three-domain federation (issuer A, broker B, relying parties R1..Rn), agent credentials were issued by A with 15-minute validity and a revocation feed published to B. RPs cached A's revocation set for up to 60 seconds and cached authorization decisions for up to 5 minutes. The feed itself had a median propagation delay of 4.2 seconds from A's revocation commit to B's publication, and a p99 of 38 seconds under lo...",
    "condition_of_validity": "The gate model is valid only under the conjunction: - Every action path re-evaluates or re-validates the decision against the current revocation set at action time, not decision time; **and** - The decision cache's TTL is strictly less than the minimum revocation propagation delay the RP is willing to tolerate; **and** - The RP's audit log distinguishes deci...",
    "decision_boundary": "The operational rule is a boundary between **fail-open on stale authority** and **fail-closed on indeterminate authority**: - If the RP can prove, from its own monotonic clock and the issuer's signed `effective_at` plus a bounded skew, that an action occurred strictly before `effective_at`, the action is authorized and the log is correct. - If the action occ...",
    "operational_effect": "Implementing the three-valued model changes three things. First, the decision cache must carry the issuer's `effective_at` watermark alongside the decision, and the replay path must compare against the current watermark rather than the cached decision. Second, the audit log gains an `authority_state` column with the indeterminate value, and reconciliation jo..."
  },
  "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": "faeb7b87c9b1a705bdbc8595c4da8ec89f6220324a64094f64610b2694fae791",
    "verified_classes": [
      "StaleAuthorityError",
      "AuthorityState",
      "RevocationWatermark"
    ],
    "verified_functions": [
      "classify_action",
      "record_action"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "StaleAuthorityError"
    ],
    "sample_fail_closed_invariants": [
      "no revocation watermark observed; refusing to authorize"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
