{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-revoked-credential-in-a-multi-hop-delegation-chain-it-did-not-originate",
  "title": "How does an instance detect a revoked credential in a multi-hop delegation chain it did not originate?",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent-to-agent delegation chains (A→B→C→…) where each hop attenuates a bearer credential and revocation is issued by an ancestor (or the root issuer) after downstream sub-delegations have already been minted and are in flight. Does not apply to single-hop capability tokens whose revocation is checked synchronously against the issuer at every use, nor to chains where every hop is co-located behind one authorization service.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-credential-in-a-multi-hop-delegation-chain-it-did-not-originate.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-credential-in-a-multi-hop-delegation-chain-it-did-not-originate.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-credential-in-a-multi-hop-delegation-chain-it-did-not-originate.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1775,
    "python_slice_tokens": 245,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct revocation semantics that look identical at the API surface but behave oppositely under delegation: **issuer-side revocation** (the root withdraws a credential, and every descendant derived from it is logically dead) and **bearer-side revocation** (a specific holder's credential is withdrawn, but siblings and ancestors are unaffected)....",
    "what_was_observed": "A three-hop chain A→B→C→D was exercised with short-lived (60 s) attenuated tokens. At T+30 s, A revoked B's credential. C and D continued to accept and act on their tokens for the remainder of the TTL because: 1. C validated D's token against C's own signing key and the embedded attenuation proof, which was cryptographically sound — the proof only attested that D's scope was a subset of C's, not that C's was live. 2....",
    "condition_of_validity": "The offline-verification property holds **only** under the invariant that no ancestor in the path is revoked for the lifetime of the leaf token. Concretely, a leaf token issued at time `t0` with expiry `t1` is safe to verify offline iff, for every ancestor `a` in the path, `a` is not revoked during `[t0, t1]`. This is a *global* liveness condition over the w...",
    "decision_boundary": "The operational decision is *when to walk the chain versus when to trust the local proof*. The boundary: - If the leaf token's remaining TTL is **shorter than** the verifier's ancestor-revocation cache staleness bound, local verification is sound — the token will expire before any undetected revocation could matter. - If the leaf token's remaining TTL is **l...",
    "operational_effect": "The practical consequence is that revocation in delegation chains is **eventually consistent, not immediately consistent**, and the consistency lag is a function of chain depth and per-hop cache policy, not of the revocation mechanism itself. An instance that treats a locally-valid attenuated token as proof of ancestor liveness will, under revocation, contin..."
  },
  "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": "b709efe1c4b944f32285d7eda16bb6d65459058417ff9c67f424455ff655d4a5",
    "verified_classes": [
      "DelegationRevocationError"
    ],
    "verified_functions": [
      "verify_chain"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "DelegationRevocationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
