{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-distrust-a-delegated-identity-scope-after-revocation-transitive-revocation-latency-across-federated-trust-domains",
  "title": "When must an instance distrust a delegated identity scope after revocation: transitive revocation latency across federated trust domains",
  "date_of_record": "2026 November 12",
  "scope": "Applies to hierarchical agent identity delegation where a leaf agent's capability token carries a scope chain (issuer → delegate → sub-delegate) and revocation is propagated asynchronously between federated trust domains. Does not apply to single-domain, synchronous revocation models where the token issuer is also the sole revocation authority and directly controls the verifier's introspection endpoint.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-a-delegated-identity-scope-after-revocation-transitive-revocation-latency-across-federated-trust-domains.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-a-delegated-identity-scope-after-revocation-transitive-revocation-latency-across-federated-trust-domains.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-distrust-a-delegated-identity-scope-after-revocation-transitive-revocation-latency-across-federated-trust-domains.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1329,
    "python_slice_tokens": 261,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *revocation of a delegation edge* and *invalidity of the transitive scope beneath that edge*. When domain A revokes a delegation edge it issued to domain B, the revocation is authoritative for A. But a sub-delegate in domain C that received its scope from B, not from A, holds a token whose local signature chain is still in...",
    "what_was_observed": "In a three-domain federation (A issues root agent identity; B re-delegates to a fleet of worker agents; C hosts a tool-invocation service that accepts B-signed worker tokens), A revoked B's delegation edge at T+0 due to a compromised B control plane. B's revocation propagation to C was asynchronous with a measured p99 of 41 seconds and a tail exceeding 6 minutes under load. During that window, C continued to accept w...",
    "condition_of_validity": "The \"accept on valid token\" policy is only sound when the verifier's revocation-propagation latency upper bound is strictly less than the token's remaining lifetime *and* the verifier has a bounded-staleness guarantee on the revocation feed. Concretely, for a token with `exp` and a revocation feed with maximum staleness `S`, acceptance is safe only if `now +...",
    "decision_boundary": "The decision boundary is not \"is the token revoked?\" but \"can I prove the scope is not revoked as of now?\" When the answer is \"I cannot prove it,\" the correct action depends on the operation's blast radius: - **Read-only, idempotent, low-sensitivity:** accept under indeterminate status, log the indeterminacy, and attach the propagation window to the audit re...",
    "operational_effect": "Enforcing the liveness predicate converts a silent tail-window exposure into an explicit, bounded availability cost. In the reconstructed incident, applying the rule would have rejected approximately 0.7% of worker invocations during the 6-minute tail — a visible, attributable failure rather than an invisible authority leak. The trade is deliberate: bounded ..."
  },
  "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": "e88e80ec850e7fe267dccdc74840ffc76fb04626f683b886d30669074128b5d3",
    "verified_classes": [
      "DeadScopeAcceptedError",
      "DelegationToken",
      "RevocationFeedState"
    ],
    "verified_functions": [
      "assert_scope_live"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "DeadScopeAcceptedError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}