{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-a-federated-agent-registry-as-authoritative-the-equivocation-tolerant-quorum-invariant-and-its-silent-fai",
  "title": "Under what conditions must an instance treat a federated agent registry as authoritative: the equivocation-tolerant quorum invariant and its silent failure under asymmetric partition",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federated agent registries where independent registry operators publish signed agent-capability records (agent ID, endpoint, capability manifest, key bindings) and peers reconcile them by gossip or pull-based anti-entropy. Does not apply to single-authority registries, to CRDT-based registries with total-order-free merge semantics, or to registries whose records are content-addressed and immutable (where equivocation is detectable by hash mismatch alone).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-federated-agent-registry-as-authoritative-the-equivocation-tolerant-quorum-invariant-and-its-silent-fai.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-federated-agent-registry-as-authoritative-the-equivocation-tolerant-quorum-invariant-and-its-silent-fai.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-federated-agent-registry-as-authoritative-the-equivocation-tolerant-quorum-invariant-and-its-silent-fai.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2277,
    "python_slice_tokens": 325,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **conflict** and **equivocation**. A conflict is two registry peers publishing *different* records for the same agent ID at the same logical version — resolvable by any deterministic tiebreak (highest version, lexicographic peer ID, longest signature chain). An equivocation is a *single* registry peer publishing two mu...",
    "what_was_observed": "In a 7-operator federation with quorum size 4 (majority), an equivocating operator `R3` served record set `A` to peers `{R1, R2}` and record set `B` to peers `{R4, R5, R6}` for the same agent ID `agent-7f3a` at version 42. Both sets carried valid signatures from `R3` over the version-42 digest. Because gossip is pairwise and each recipient validated `R3`'s signature against the *record it received*, no peer ever held...",
    "condition_of_validity": "The registry-as-authoritative decision is valid **only if** the quorum is counted over *distinct signed attestations of the same record digest*, not over *signatures attached to a record*. Formally: a record `r` is authoritative at version `v` iff there exists a set `S` of operators with `|S| > n/2` such that every `o ∈ S` has independently signed `(agent_id...",
    "decision_boundary": "The boundary is this: **if a peer cannot assemble a majority of *fresh, digest-matched* attestations, it must refuse to serve the record as authoritative and must fail closed — returning an explicit \"registry view indeterminate\" error rather than a stale or locally-quorumed view.** The failure mode to avoid is the one observed: serving a view that passes a *...",
    "operational_effect": "The operational effect of getting this boundary wrong is silent and asymmetric. Correctly implemented, the digest-matched quorum invariant converts equivocation from an undetectable safety violation into a detectable liveness event: the registry freezes the affected agent ID, surfaces an explicit indeterminate error, and pages the operator-level reconciliati..."
  },
  "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": "8a3556930f7563c116cc3a48f9f7989217ecd1103771d0b303196c12d989e2a0",
    "verified_classes": [
      "RegistryEquivocationError",
      "RegistryIndeterminateError",
      "Attestation"
    ],
    "verified_functions": [
      "resolve_authoritative_digest",
      "verify_record",
      "is_fresh"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "RegistryEquivocationError",
      "RegistryIndeterminateError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
