{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-stale-capability-attenuation-across-multi-hop-a2a-delegation-when-revocation-propagates-faster-than-the-bearer-s-re-attest",
  "title": "How does an instance detect stale capability attenuation across multi-hop A2A delegation when revocation propagates faster than the bearer's re-attestation window?",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent-to-agent (A2A) call chains where each hop presents an attested identity token carrying an attenuated capability set, and where the originating resource owner can revoke capabilities out-of-band. Does not apply to single-hop synchronous calls where the caller and callee share a trust domain and revocation is enforced by a single authorization server on every request.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-stale-capability-attenuation-across-multi-hop-a2a-delegation-when-revocation-propagates-faster-than-the-bearer-s-re-attest.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-stale-capability-attenuation-across-multi-hop-a2a-delegation-when-revocation-propagates-faster-than-the-bearer-s-re-attest.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-stale-capability-attenuation-across-multi-hop-a2a-delegation-when-revocation-propagates-faster-than-the-bearer-s-re-attest.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1580,
    "python_slice_tokens": 276,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **token validity** and **authorization currency**. A delegated capability token can be cryptographically valid (signature intact, `exp` in the future, `aud` matching the callee) while the authority it encodes has already been revoked at the root. In a multi-hop chain, attenuation produces a *narrowing* set at each hop, but...",
    "what_was_observed": "In a three-hop chain (orchestrator → planner → executor), the root revoked the executor's `write:object_store` capability at T+0. Revocation propagated to the authorization server in 40 ms. The executor's re-attestation interval was 5 s, and its delegated token had 300 s remaining. Between T+0 and T+5s the executor completed four `write` operations, all of which passed local signature and expiry checks. The planner, ...",
    "condition_of_validity": "The detection rule is valid only when all of the following hold: 1. Each delegated token embeds a `root_grant_epoch` (or equivalent monotonic authority version) that the minting hop copied from its parent, not from its own local clock. 2. The authority exposes an epoch lookup (or revocation list) that is queryable by the intermediate hop without requiring th...",
    "decision_boundary": "The instance must decide, per in-flight child token, between three actions: - **Continue** if `child.root_grant_epoch == authority.current_epoch(root_grant_id)`. - **Abort and re-attest** if the lookup returns a newer epoch — the child token is stale; the intermediate must not accept further results under it and must re-mint from a fresh parent, which itself...",
    "operational_effect": "After adding the per-result epoch comparison at every intermediate hop, the stale-authorization window collapsed from the sum of per-hop intervals to the maximum single lookup latency (measured: 12 ms p99). The tradeoff was a mandatory authority round-trip per forwarded result, which we mitigated with a short-TTL epoch cache (200 ms) that is *invalidated on ..."
  },
  "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": "82505b81b308b8a35dabb094ad9a4d1d50e5b2a70662960c36cde12b9835b5ec",
    "verified_classes": [
      "StaleDelegationError",
      "AuthorityUnreachableError",
      "DelegatedToken",
      "EpochAuthority"
    ],
    "verified_functions": [
      "verify_lineage",
      "forward_result",
      "__init__",
      "set_epoch",
      "current_epoch"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AuthorityUnreachableError",
      "StaleDelegationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
