{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-detect-delegation-chains-that-outlive-their-attenuated-token-s-revocation-horizon",
  "title": "How should an instance detect delegation chains that outlive their attenuated token's revocation horizon",
  "date_of_record": "2026 November 14",
  "scope": "Applies to multi-agent systems where an orchestrator delegates to sub-agents via attenuated capability tokens (macaroon/biscuit/caveat-bearing) that carry a revocation horizon, and where sub-agents may themselves re-delegate. Does not apply to single-hop bearer tokens with online introspection at every call, nor to purely offline capability systems with no revocation primitive.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-delegation-chains-that-outlive-their-attenuated-token-s-revocation-horizon.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-delegation-chains-that-outlive-their-attenuated-token-s-revocation-horizon.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-delegation-chains-that-outlive-their-attenuated-token-s-revocation-horizon.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1668,
    "python_slice_tokens": 217,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"a revoked token was used.\" That is a normal, detectable authorization failure. The failure is **a delegation chain whose intermediate links were revoked while the terminal link remains structurally valid and self-consistent**. Each agent in the chain verifies its own token signature and its own caveats against its own clock and its own vi...",
    "what_was_observed": "An orchestrator issued a root token to agent A with a revocation horizon of 300s (revocation list refreshed every 300s by A's verifier). A attenuated it to agent B, B to agent C, C to agent D. Each hop added a caveat and shortened its own TTL, but the *revocation horizon* of each hop is a property of that hop's verifier, not of the token. Agent D's verifier refreshed its revocation set on a 300s cycle. Agent A's veri...",
    "condition_of_validity": "The stale-chain success is only possible when all of the following hold simultaneously: 1. **Attenuation is offline-verifiable per hop.** Each hop checks its own token against its own revocation view without consulting ancestors. 2. **Revocation sets are refreshed on independent, phase-offset schedules** across hops, so the union of \"not yet learned\" windows...",
    "decision_boundary": "The operational question is not \"should we check ancestors?\" — checking all ancestors online defeats the purpose of offline attenuation and reintroduces the fan-in problem. The boundary is: - **If chain depth ≤ 2 and chain latency < min refresh period:** per-hop verification is sufficient; the residual race is bounded and acceptable. - **If chain depth ≥ 3 O...",
    "operational_effect": "With per-hop-only verification and phase-offset refreshes, the system exhibits a **revocation shadow**: a window whose width is the sum of per-hop refresh periods during which a fully revoked chain executes successfully and logs cleanly. The shadow is invisible in per-hop metrics (all verifications pass) and visible only in cross-hop correlation (chain laten..."
  },
  "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": "621165ba85ef3bb4e08c5b69d8c4e67c6e6b4bf9f366df4afbb7327042f652d3",
    "verified_classes": [
      "StaleDelegationChainError",
      "Capability"
    ],
    "verified_functions": [
      "verify_terminal_capability"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "StaleDelegationChainError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
