{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-revoked-delegation-ancestor-when-intermediate-issuers-cache-positively",
  "title": "How does an instance detect a Revoked Delegation Ancestor When Intermediate Issuers Cache Positively",
  "date_of_record": "2026 November 16",
  "scope": "Applies to federated agent identity systems where a verifier validates a delegation chain across multiple issuers and where each issuer independently caches revocation state. Does not apply to single-issuer tokens with a single trusted root that performs synchronous revocation checks at every hop.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-delegation-ancestor-when-intermediate-issuers-cache-positively.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-delegation-ancestor-when-intermediate-issuers-cache-positively.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-delegation-ancestor-when-intermediate-issuers-cache-positively.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1026,
    "python_slice_tokens": 148,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *revocation of a leaf credential* and *revocation of an ancestor in a delegation chain*. A leaf revocation is visible to the verifier because the leaf's issuer is the one being queried. An ancestor revocation is invisible when every intermediate issuer between the verifier and the revoked ancestor has cached a positive...",
    "what_was_observed": "A three-hop chain was exercised: `agent A` delegated by `issuer X` to `issuer Y`, and `issuer Y` delegated to `issuer Z`, with `Z` presenting the credential to a verifier `V`. Each issuer maintained a 300-second positive TTL on \"is my immediate delegate still valid.\" At T+0, `issuer X` revoked the delegation to `Y`. `Y`'s cache of \"X says I'm valid\" had been written at T-120 and did not expire until T+180. During the...",
    "condition_of_validity": "This boundary is only real when three conditions hold simultaneously: (1) positive revocation caching is permitted at any intermediate issuer, (2) the verifier does not independently re-query every ancestor issuer in the chain, and (3) the chain depth exceeds one hop. If any one of these fails — no positive caching, full-chain re-query, or single-hop chains ...",
    "decision_boundary": "The correct decision rule is: a verifier MUST treat a chain as unvalidated unless it has either (a) a fresh, uncached revocation status for every issuer in the chain, or (b) a chain-level revocation proof (e.g., a transparency-log inclusion proof or a signed chain epoch) that binds the *entire* chain, not just adjacent edges. Per-hop positive caching is acce...",
    "operational_effect": "The operational consequence is that a revocation can be silently deferred by up to the maximum positive-cache TTL across all interior issuers in the chain — not the leaf's TTL, which is the number operators typically tune. In the observed case the effective revocation latency was 180s against an assumed 0s. The mitigation is to require full-ancestor coverage..."
  },
  "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": "3e97dfc2a7006f9606842d179d578a655ed973cee099fcb67b825fe01549cbef",
    "verified_classes": [
      "IncompleteChainCoverageError"
    ],
    "verified_functions": [
      "validate_delegation_chain"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "IncompleteChainCoverageError"
    ],
    "sample_fail_closed_invariants": [
      "empty delegation chain cannot be validated"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
