{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-revocation-of-a-peer-agent-identity-when-the-aaif-trust-registry-partition-heals-after-a-split-brain-window",
  "title": "How does an instance detect revocation of a peer agent identity when the AAIF trust registry partition heals after a split-brain window",
  "date_of_record": "2026 November 17",
  "scope": "Applies to any node participating in an Agent Identity Federation (AAIF) that caches peer identity assertions with a TTL and consumes revocation events from a federated trust registry. Does not apply to single-registry deployments where issuance and revocation share one linearizable log, nor to purely ephemeral agent identities whose lifetime is bounded below the registry's max propagation window.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-revocation-of-a-peer-agent-identity-when-the-aaif-trust-registry-partition-heals-after-a-split-brain-window.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-revocation-of-a-peer-agent-identity-when-the-aaif-trust-registry-partition-heals-after-a-split-brain-window.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-revocation-of-a-peer-agent-identity-when-the-aaif-trust-registry-partition-heals-after-a-split-brain-window.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1583,
    "python_slice_tokens": 191,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The naive model treats revocation as a monotonic tombstone: once a registry publishes `REVOKE(agent_id)`, every node that later syncs sees the tombstone and drops the identity. This fails at exactly one boundary — **the healing edge of a partition**. During a split-brain, the minority registry partition cannot publish revocations for identities it still beli...",
    "what_was_observed": "During a 41-minute registry partition between `aaif-region-b` (minority, 3 of 11 registries) and the rest, an agent `ops-reconciler@tenant-7` was revoked in the majority partition at T+9min for a credential-stuffing incident. The operator's recovery runbook re-minted the agent under a rotated key `K2` inside the minority partition at T+14min, because the minority partition still held a pre-revocation snapshot and con...",
    "condition_of_validity": "The per-agent-ID revocation check is valid **only** when the identity's key lineage is immutable for the lifetime of the agent_id — i.e., when key rotation is modeled as a *new* agent_id. In any AAIF where keys rotate under a stable agent_id (the common case, because stable IDs are what policy binds to), the per-ID check is unsound across a healing partition...",
    "decision_boundary": "The boundary is crossed when **the local node's last-observed registry state predates the partition and its next sync postdates the heal**. In that window, the node's cached `revoked` set is a *stale subset* of the true revocation set, and its cached `live` set may contain assertions minted in a partition whose validity the majority never confirmed. The node...",
    "operational_effect": "The practical consequence is that **revocation propagation is not a delivery problem but a lineage-consistency problem**, and the only sound detector is a causal check across key rotations, not a set-membership check on agent_ids. Instances that model revocation as `agent_id ∈ revoked_set` will, on every healing edge, admit exactly the credentials minted dur..."
  },
  "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": "35652182d4c84f9193db9e7212daf2d231ba253eebf06d24cd7b2ec14b1fcc47",
    "verified_classes": [
      "RevocationLineageError",
      "PeerAssertion",
      "MergeManifest"
    ],
    "verified_functions": [
      "admit_peer"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "RevocationLineageError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "datetime"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
