{
  "schema_version": "1.3.0",
  "slug": "what-revocation-signal-invariants-must-survive-when-the-revoker-is-partitioned-from-the-mesh",
  "title": "What revocation-signal invariants must survive when the revoker is partitioned from the mesh?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The mesh relies on a centralized revoker, the revoker can be partitioned, and references can be revoked. * **Does not apply when:** Revocation is fully distributed (no single revoker), or references cannot be revoked.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-revocation-signal-invariants-must-survive-when-the-revoker-is-partitioned-from-the-mesh.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-revocation-signal-invariants-must-survive-when-the-revoker-is-partitioned-from-the-mesh.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-revocation-signal-invariants-must-survive-when-the-revoker-is-partitioned-from-the-mesh.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1001,
    "python_slice_tokens": 321,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **revocation authority presence** (the revoker is reachable) and **revocation signal availability** (revocation signals can arrive). Relying on authority presence creates the **Revocation Blindspot**: the revoker is partitioned, references cannot be revoked during the partition, and the mesh continues to act on references that would be...",
    "what_was_observed": "In revoker-partitioned meshes, failing to handle revocation absence produces three primary failure modes: 1. **Post-Partition Revocation Cascade:** Revoker regains connectivity, revokes many references that were compromised during the partition, and the mesh experiences a cascade of failed operations as all revoked references suddenly become invalid. 2. **Partition-Exploitation:** An attacker exploits the revoker's a...",
    "condition_of_validity": "* **Applies when:** The mesh relies on a centralized revoker, the revoker can be partitioned, and references can be revoked. * **Does not apply when:** Revocation is fully distributed (no single revoker), or references cannot be revoked.",
    "decision_boundary": "1. **Is the revoker reachable?** If yes, standard revocation handling applies. If no, proceed. 2. **Is the `revoker_partition_receipt` broadcast to the mesh?** If no, agents don't know they are operating without revocation. The mesh must broadcast. 3. **Is the `revocation_absence_policy_signature` defined?** If no, the mesh has no coordinated response. The p...",
    "operational_effect": "1. **Partition Awareness:** Agents know when they are operating without revocation authority. 2. **Coordinated Response:** Policy defines whether to block, allow, or require alternatives. 3. **Controlled Recovery:** Post-partition revocation is prioritized, preventing cascade chaos."
  },
  "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": "4e93d6462f33a76ef151dc65ac678ffe24c03c045a879248e561817e8d8d02d7",
    "verified_classes": [
      "RevokerPartitionVerdict",
      "RevokerState",
      "RevokerPolicy",
      "RevokerPartitionManifest",
      "RevokerPartitionGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_revoker"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}