{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-federated-capability-registry-diverge-from-its-peers-after-a-partition-heals-and-how-do-you-detect-it-before-routing-agents",
  "title": "Why does an instance of a federated capability registry diverge from its peers after a partition heals, and how do you detect it before routing agents to a stale capability?",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-organization agent registries that exchange capability manifests via gossip or anti-entropy (e.g., CRDT-backed registries, delta-sync federation). Does not apply to single-organization registries with a single authoritative writer, nor to stateless discovery via a shared global index.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-capability-registry-diverge-from-its-peers-after-a-partition-heals-and-how-do-you-detect-it-before-routing-agents.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-capability-registry-diverge-from-its-peers-after-a-partition-heals-and-how-do-you-detect-it-before-routing-agents.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federated-capability-registry-diverge-from-its-peers-after-a-partition-heals-and-how-do-you-detect-it-before-routing-agents.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1831,
    "python_slice_tokens": 552,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"stale replica.\" Staleness is expected and bounded by sync interval. The failure is **capability resurrection**: a capability that was *revoked* or *deprecated* at its authoritative origin reappears on a peer after a partition heals, because the peer's local state was reconstructed from a merge that favored a higher logical clock attached ...",
    "what_was_observed": "Across a three-org federation (A publishes capability `summarize.v3`, B and C consume), a 40-minute partition between B and C healed. During the partition: - A revoked `summarize.v3` (deprecation notice, epoch `A:7`, counter `12`). - C received the revocation and applied it (local counter for that key became `12`). - B did not receive it; B's copy remained at counter `11`, but B independently re-announced a *cached* ...",
    "condition_of_validity": "This boundary applies when all of the following hold: 1. Revocations and deprecations are represented as ordinary manifest mutations (not as tombstones with separate, non-overridable semantics). 2. Merge ordering uses wall-clock or any physical time source that is not bounded by a known skew across federation members. 3. A peer may re-announce a manifest it ...",
    "decision_boundary": "The decision boundary is **whether a re-announcement may outrank a revocation.** Two policies are defensible: - **Remove-wins (safe):** a tombstone for a key permanently dominates any manifest for that key until the key is explicitly re-created by the *original authority* with a strictly greater authority epoch. Re-announcements from non-authorities are disc...",
    "operational_effect": "The operational effect is a **silent routing regression**: the registry reports full convergence (`divergence=0` across all peers), health checks pass, and the stale capability is served for the entire window between heal and the next authoritative re-announcement — which, if the origin does not re-announce on a schedule, may be indefinite. Detection require..."
  },
  "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": "e2ef9747378234600a25e96451901537d551a1a3c15e4d418d5f52f2885f95fc",
    "verified_classes": [
      "CapabilityResurrectionError",
      "Manifest",
      "Registry"
    ],
    "verified_functions": [
      "route_agent",
      "merge",
      "authority_lag"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "CapabilityResurrectionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
