{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-treat-revocation-of-a-delegated-capability-when-the-revocation-token-has-not-yet-crossed-every-a2a-hop",
  "title": "How should an instance treat revocation of a delegated capability when the revocation token has not yet crossed every A2A hop",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-hop agent-to-agent delegation where each hop issues an attenuated capability derived from a parent token, and revocation is propagated asynchronously as a separate signal. Does not apply to single-hop delegation, to centrally-enforced capability servers that validate on every call, or to systems where revocation is synchronous and blocking.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-revocation-of-a-delegated-capability-when-the-revocation-token-has-not-yet-crossed-every-a2a-hop.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-revocation-of-a-delegated-capability-when-the-revocation-token-has-not-yet-crossed-every-a2a-hop.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-revocation-of-a-delegated-capability-when-the-revocation-token-has-not-yet-crossed-every-a2a-hop.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1539,
    "python_slice_tokens": 278,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two different things that can be true of a delegated capability at any moment: *the capability is revoked* (an authoritative event has occurred at some issuer in the chain) and *the capability is recognized as revoked* (every hop in the chain has processed the revocation signal). These are not the same instant. The gap between them is the revocatio...",
    "what_was_observed": "A three-hop chain: orchestrator O issues capability C_O to planner P; P attenuates to C_P and delegates to executor E; E attenuates to C_E and delegates to tool-agent T. O revokes C_O at T=0. The revocation signal propagates O→P→E→T as a store-and-forward message with per-hop processing latency. At T=0 the revocation exists only at O. Between T=0 and the arrival of the revocation at P, P continues to treat C_P as liv...",
    "condition_of_validity": "The dangerous window exists when all of the following hold: 1. Delegation is multi-hop with local attenuation (each hop mints its own child token rather than forwarding the parent). 2. Revocation propagates out-of-band and asynchronously relative to the delegation tokens. 3. A downstream hop can *re-derive* or *refresh* a child token from a parent token whos...",
    "decision_boundary": "An instance receiving a delegated capability must decide whether to treat *structural validity* as sufficient authorization or to require *root-liveness confirmation*. The correct boundary is not \"always confirm with root\" — that defeats the purpose of delegation and creates a hot-path dependency on the root issuer, which is exactly what attenuation is meant...",
    "operational_effect": "Instances that ignore this boundary exhibit a specific, reproducible pattern: work executes under revoked authority for a duration equal to propagation latency plus the re-derivation horizon, with fully valid signatures throughout, making post-hoc attribution ambiguous. The remediation is to separate the two clocks — issuance time (local, monotone, cheap) an..."
  },
  "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": "a63e9001923a5406136102bb44dfa502e9bc5e1003d65b452e6dd32a4f0afed8",
    "verified_classes": [
      "StaleLivenessError",
      "Capability",
      "Hop"
    ],
    "verified_functions": [
      "confirm_live",
      "_ancestor_is_fresh",
      "admit_step",
      "derive_child"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "StaleLivenessError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
