{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-stop-trusting-a-peer-s-revocation-gossip-the-quorum-signed-revocation-horizon-in-cross-org-federated-agent-reputation",
  "title": "Where must an instance stop trusting a peer’s revocation gossip: the quorum-signed revocation horizon in cross-org federated agent reputation",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated agent reputation systems where revocation events propagate as signed gossip across organizational trust boundaries and local agents make admission decisions from a bounded, partially ordered event set. Does not apply to single-organization registries with a central authoritative revocation list, nor to systems where every peer shares a single total order of revocation events.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-stop-trusting-a-peer-s-revocation-gossip-the-quorum-signed-revocation-horizon-in-cross-org-federated-agent-reputation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-stop-trusting-a-peer-s-revocation-gossip-the-quorum-signed-revocation-horizon-in-cross-org-federated-agent-reputation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-stop-trusting-a-peer-s-revocation-gossip-the-quorum-signed-revocation-horizon-in-cross-org-federated-agent-reputation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1692,
    "python_slice_tokens": 249,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not that a revocation is forged or delayed. It is that a *revocation horizon* — the newest revocation event an instance has locally verified — is silently treated as a *revocation completeness* — the claim that no revocation newer than the horizon exists. In a cross-org federation, these are different propositions. A peer can honestly report “...",
    "what_was_observed": "In a three-org federation (issuers A, B, C; verifiers V1, V2), the following sequence occurred repeatedly under partition: 1. Issuer A revoked agent `a-77` at A-sequence 120. The revocation was signed and gossiped to V1. 2. Issuer B, unrelated, issued a routine reputation update at B-sequence 400. V1 received it. 3. V1’s scalar horizon advanced to 400. Its per-issuer horizon for A remained at 119. 4. V2, partitioned ...",
    "condition_of_validity": "The per-issuer horizon check is *necessary* whenever all of the following hold: - Revocation events are partitioned by issuer (each issuer controls its own sequence space). - Gossip delivery is not guaranteed to be causally complete across issuers (a verifier can receive issuer B’s stream without having received all of issuer A’s stream up to the same wall-c...",
    "decision_boundary": "The correct decision rule, stated precisely: > Admit agent `x` issued by authority `I` iff `per_issuer_horizon[I] >= revocation_epoch(x, I)` **and** the verifier holds a signed freshness assertion from `I` no older than the configured staleness bound `Δ` for issuer `I`. Two boundaries matter operationally: - **The horizon boundary.** The per-issuer horizon m...",
    "operational_effect": "After migrating to per-issuer horizons with explicit staleness bounds, the observable changes were: - Admission denials during cross-org partition increased by roughly 0.4% of decisions — these were previously unsound admissions, not false positives. The denial rate is the *price* of the invariant, and it is bounded by the fraction of decisions whose issuer ..."
  },
  "matched_failure_symptoms": [
    "SPLIT_BRAIN_OR_ZOMBIE_WORKER"
  ],
  "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": "c1adb4987c24353357e51f2d361cc0a7660402fdba582d654e033e7bc3558636",
    "verified_classes": [
      "RevocationHorizonError",
      "FreshnessAssertion",
      "VerifierState"
    ],
    "verified_functions": [
      "admit_agent"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "RevocationHorizonError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
