{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-still-hold-authority-after-capability-revocation-across-a-federated-trust-boundary",
  "title": "Why does an instance still hold authority after capability revocation across a federated trust boundary?",
  "date_of_record": "2026 November 15",
  "scope": "Applies to multi-domain agent systems where an authority domain issues short-lived capability tokens (macaroons, biscuit tokens, signed JWT capability sets) that are presented to resource domains, and where revocation of an agent identity must take effect before the token's natural expiry. Does not apply to single-domain systems with a shared revocation list, nor to systems where every request is re-validated against the issuing domain synchronously.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-still-hold-authority-after-capability-revocation-across-a-federated-trust-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-still-hold-authority-after-capability-revocation-across-a-federated-trust-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-still-hold-authority-after-capability-revocation-across-a-federated-trust-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1641,
    "python_slice_tokens": 313,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *token validity* and *agent authority*. A short-lived capability token encodes a claim: \"the bearer, at issuance time, was granted capability C until wall-clock time T.\" Revocation is a claim about the *subject* (the agent identity), not about the *token*. These two facts live in different domains, propagate on differe...",
    "what_was_observed": "An agent identity `agent://ops/reconciler-7` held a delegated capability set issued by trust domain `alpha` and presented it to resource domain `beta`. `beta` validated the token chain, verified the signature against `alpha`'s published JWKS, and cached an authorization decision under key `sha256(token) → {subject, caps, exp}` with a local cache TTL of 300s. The token TTL was 120s. At T+0 the operator revoked `reconc...",
    "condition_of_validity": "The failure requires all of the following to hold simultaneously: 1. The resource domain caches authorization decisions keyed on token identity or token hash rather than subject identity. 2. The agent can obtain and hold more than one valid token concurrently (pre-fetch, batch issuance, or overlapping refresh windows). 3. Revocation is expressed at the subje...",
    "decision_boundary": "The operational decision is whether to treat the resource domain's cache as an authority-bearing artifact or as a pure performance optimization. If it is authority-bearing — i.e., a cache hit is allowed to authorize a request without re-establishing the subject's current standing — then the cache must be invalidated by revocation events, which requires a rev...",
    "operational_effect": "The practical effect is that revocation latency is governed by the *maximum* of (propagation delay, token TTL, cache TTL), not by the token TTL alone, and the cache TTL is usually the largest term and the least monitored. Systems that advertise \"120-second revocation bound\" based on token TTL are typically operating at 5–10 minute effective bounds. The corre..."
  },
  "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": "50d64d7fe3c782d855ef2ca04bbd7d967b0773db48219947588704e6035e5829",
    "verified_classes": [
      "RevocationPropagationError",
      "CapabilityToken",
      "DecisionCacheEntry",
      "FederatedAuthorizer"
    ],
    "verified_functions": [
      "token_hash",
      "__init__",
      "_revocation_known_recently",
      "authorize",
      "_reconfirm_standing"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RevocationPropagationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
