{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-an-upstream-trust-domain-revocation-when-the-revocation-channel-is-itself-gated-by-the-credential-being-revoked",
  "title": "How does an instance detect an upstream trust-domain revocation when the revocation channel is itself gated by the credential being revoked",
  "date_of_record": "2026 November 17",
  "scope": "Applies to federated agent-identity systems where a relying instance (agent, gateway, or tool-runner) validates peer credentials against a trust root it does not control, and where revocation state is distributed asynchronously through a channel that requires a valid, unrevoked credential to read. Does not apply to single-domain PKI where the CRL/OCSP endpoint is unauthenticated or reachable out-of-band, nor to systems that push signed revocation deltas over a separate authenticated transport independent of the agent credential itself.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-an-upstream-trust-domain-revocation-when-the-revocation-channel-is-itself-gated-by-the-credential-being-revoked.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-an-upstream-trust-domain-revocation-when-the-revocation-channel-is-itself-gated-by-the-credential-being-revoked.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-an-upstream-trust-domain-revocation-when-the-revocation-channel-is-itself-gated-by-the-credential-being-revoked.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2153,
    "python_slice_tokens": 457,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between **revocation as a fact** and **revocation as a reachable signal**. In a single trust domain these collapse: the CRL Distribution Point is an unauthenticated GET, so the fact of revocation and the ability to learn it are decoupled. In a federated mesh they do not collapse, because the most common deploymen...",
    "what_was_observed": "During a cross-domain incident on a three-domain mesh (call them `alpha`, `beta`, `gamma`), `alpha` revoked an agent credential `agt-7f3` after a policy change. `agt-7f3` held a credential issued by `alpha` and was configured to poll `alpha`'s revocation feed every 90 seconds using that same credential. The sequence observed: 1. At `T+0` the revocation was committed in `alpha`'s authority store. 2. `agt-7f3`'s next p...",
    "condition_of_validity": "The failure is *live* — meaning the instance is blind to its own revocation — exactly when all of the following hold. Remove any one and detection recovers: - **Channel coupling:** the revocation feed requires a credential of the same trust domain as the one being revoked. If the feed is unauthenticated, or authenticated by an out-of-band management credenti...",
    "decision_boundary": "The operational decision is whether to treat an auth failure on the revocation feed as *evidence of revocation* or as *evidence of fault*. The correct boundary is: **an instance must never treat a coupled-channel auth failure as proof of non-revocation, and must never treat it as proof of revocation either — it must treat it as an unknown state and act conse...",
    "operational_effect": "The practical consequence is that revocation propagation latency in a federated mesh is not a property of the authority's commit speed but of the *slowest coupled reader's ability to distinguish its own revocation from noise*. In the observed incident this inflated effective revocation latency from sub-second (authority commit) to 11 minutes (peer cache expi..."
  },
  "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": "2ed13a05102cc85efeeaefdf91903280d6ca58bf77582a377a6f04fda0ef5789",
    "verified_classes": [
      "RevocationStatusUnknown",
      "RevokedError",
      "Status",
      "CoupledFeedPoller"
    ],
    "verified_functions": [
      "require_known_status",
      "poll",
      "_fetch_feed"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RevocationStatusUnknown",
      "RevokedError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
