{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-a-cached-aaif-delegation-grant-as-revoked-before-the-revocation-event-is-durably-propagated",
  "title": "Under what conditions must an instance treat a cached AAIF delegation grant as revoked before the revocation event is durably propagated",
  "date_of_record": "2026 November 16",
  "scope": "Applies to AAIF (Agent Authorization and Identity Federation) delegation chains where an agent instance holds a locally cached capability grant and relies on a revocation propagation channel that is asynchronous relative to the authorization decision path. Does not apply to synchronous, transaction-coupled revocation (e.g., central PDP consulted on every request with read-your-writes consistency), nor to chains terminated by short-lived bearer tokens whose TTL is shorter than the maximum propagation lag.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-cached-aaif-delegation-grant-as-revoked-before-the-revocation-event-is-durably-propagated.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-cached-aaif-delegation-grant-as-revoked-before-the-revocation-event-is-durably-propagated.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-cached-aaif-delegation-grant-as-revoked-before-the-revocation-event-is-durably-propagated.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1771,
    "python_slice_tokens": 207,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *revocation as a propagated event* and *revocation as an entailed invariant*. AAIF delegation chains are DAGs of signed grants: principal P delegates capability C to agent A₁ with attenuations, A₁ re-delegates a subset to A₂, and so on. Each edge carries an issuer signature, an attenuation predicate, and a validity window....",
    "what_was_observed": "In a multi-hop AAIF deployment (three delegation hops, ~40k agent instances, revocation feed with median propagation of 900 ms and p99 of 11 s), the following was observed during a red-team exercise: - A grant G₃ = (A₂ → A₃, cap: `read:dataset/7`, exp: T+3600s) was cached by instance I₃ at t₀. - At t₁, the root principal revoked the edge A₀ → A₁. The tombstone was published to the feed under key `edge:A₀→A₁`. - I₃ su...",
    "condition_of_validity": "A cached AAIF grant may be treated as authorized **only** when all of the following hold at the moment of use, not at the moment of caching: 1. **Chain integrity:** every edge in the path from root principal to the acting instance verifies under its issuer's key. 2. **Epoch monotonicity:** for every edge e in the path, `e.revocation_epoch >= chain_status.epo...",
    "decision_boundary": "The operational rule: **key revocation checks on the chain, not on the grant.** Concretely: - Subscribe to (or poll) the chain-status document, which carries the epoch floor for each root principal. This is a small, coarsely-updated artifact; polling it at `max_propagation_lag / 2` is cheap. - On every authorization decision, re-evaluate conditions 1–4 above...",
    "operational_effect": "Instances that adopted chain-keyed revocation checking eliminated the 47-minute window in the red-team replay; the maximum unauthorized-action window collapsed to the chain-status freshness bound (configured at 2 s, observed p99 2.3 s). The cost was a 3–5% increase in authorization-path latency from the epoch comparison and a small increase in chain-status f..."
  },
  "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": "29949fbf68483fb6ca486c0ae3ae3f3a0c669645592a8f826ff3236636e514c0",
    "verified_classes": [
      "DelegationRevokedError",
      "Edge",
      "ChainStatus"
    ],
    "verified_functions": [
      "authorize"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "DelegationRevokedError"
    ],
    "sample_fail_closed_invariants": [
      "empty delegation chain"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
