{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-revoked-capability-peer-when-the-revocation-plane-and-the-data-plane-disagree-on-causal-order",
  "title": "How does an instance detect a revoked capability peer when the revocation plane and the data plane disagree on causal order",
  "date_of_record": "2026 November 15",
  "scope": "Applies to multi-agent systems where capability attestations (signed grants that peer A may invoke operation X on peer B) are issued by an attestation authority and revoked through a separate propagation channel, and where peers cache attestations locally for latency reasons. Does not apply to single-process agent runtimes, to systems where every invocation synchronously re-validates against the authority, or to monotonic read-only capability leases that are never revoked mid-flight.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-capability-peer-when-the-revocation-plane-and-the-data-plane-disagree-on-causal-order.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-capability-peer-when-the-revocation-plane-and-the-data-plane-disagree-on-causal-order.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-revoked-capability-peer-when-the-revocation-plane-and-the-data-plane-disagree-on-causal-order.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1949,
    "python_slice_tokens": 197,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The common mental model is that revocation is a *state*: an attestation is either valid or revoked, and a peer that checks the authority learns the truth. The operative distinction is that revocation is an *event* propagating over a channel whose delivery order is not causally tied to the data plane. An invocation that arrives at peer B at wall-clock time `t...",
    "what_was_observed": "In a deployment of 40 collaborating agents sharing a capability authority, agent `A-17` had its `write:ledger` grant revoked at authority epoch 8814 after a policy change. The revocation was published to a gossip channel with a target fan-out of 3 hops and a nominal propagation bound of 400 ms. Agent `A-17` continued issuing `write:ledger` invocations for 1.9 seconds. Peer `B-04` accepted 6 of them, each carrying a v...",
    "condition_of_validity": "The detection rule is sound only under the following conditions, all of which must hold: 1. **Epoch monotonicity at the authority.** Every revocation and every grant issuance advances a single authority epoch, and the epoch is globally ordered (a single sequencer or a consensus log). If revocations and grants are sequenced by different authorities, epochs ar...",
    "decision_boundary": "The boundary is between *rejecting an invocation that would have succeeded* and *accepting an invocation that violates a revocation*. The rule above is deliberately biased toward rejection: any attestation whose epoch is behind the receiver's witness is refused, even if the revocation in question was for a different peer or a different capability. This is co...",
    "operational_effect": "After adopting the epoch-witness rule, the observed deployment's revocation-violation window dropped from 1.9 s to the receiver's gossip lag (median 180 ms, p99 610 ms), with the residual window attributable to receivers that had not yet observed any epoch past the revocation. The false-rejection rate settled at 0.7% of invocations during revocation bursts a..."
  },
  "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": "c8bb6546fb07a5fe6528dc898c7876e7a13020bad093ad99f3a2c22221b7069f",
    "verified_classes": [
      "RevocationCausalityError",
      "Attestation",
      "EpochWitness"
    ],
    "verified_functions": [
      "admit_invocation",
      "__init__",
      "observe",
      "_persist"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "RevocationCausalityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
