{"id":"anti-entropy-detects-but-cannot-fully-resolve-divergence","text":"Anti-entropy can precisely locate divergent key ranges via Merkle tree diffs but cannot fully reconcile them: tombstone semantics differ at every layer (empty-bytes sentinel in LSM, preserved-by-default in merge, replication-convergence-dependent in distributed), preventing consistent cross-replica resolution of deleted keys.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["merkle-diff-enables-targeted-key-range-repair","tombstone-lifecycle-fragmented-across-modules"],"outlist":[],"label":"Detection (Merkle diffs) is precise but resolution is blocked by inconsistent tombstone handling across modules"}],"dependents":["distributed-divergence-accumulates-without-bound"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"insufficient"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"anti-entropy-detects-but-cannot-fully-resolve-divergence","truth_value":"IN","reason":"SL justification valid","antecedents":["merkle-diff-enables-targeted-key-range-repair","tombstone-lifecycle-fragmented-across-modules"],"label":"Detection (Merkle diffs) is precise but resolution is blocked by inconsistent tombstone handling across modules"},{"node":"merkle-diff-enables-targeted-key-range-repair","truth_value":"IN","reason":"SL justification valid","antecedents":["merkle-diff-returns-leaf-indices","key-range-merkle-sorts-by-key","merkle-diff-order-is-ascending"],"label":"Sorted key input + sorted index output = direct mapping from diff results to key ranges needing repair"},{"node":"merkle-diff-returns-leaf-indices","truth_value":"IN","reason":"premise"},{"node":"key-range-merkle-sorts-by-key","truth_value":"IN","reason":"premise"},{"node":"merkle-diff-order-is-ascending","truth_value":"IN","reason":"premise"},{"node":"tombstone-lifecycle-fragmented-across-modules","truth_value":"IN","reason":"SL justification valid","antecedents":["lsm-tombstone-is-empty-bytes","merge-preserves-tombstones-by-default","distributed-tombstone-removal-needs-replication-convergence"],"label":"Three layers of the tombstone lifecycle (creation, local cleanup, distributed cleanup) are independently implemented with no shared abstraction or safety contract"},{"node":"lsm-tombstone-is-empty-bytes","truth_value":"IN","reason":"premise"},{"node":"merge-preserves-tombstones-by-default","truth_value":"IN","reason":"premise"},{"node":"distributed-tombstone-removal-needs-replication-convergence","truth_value":"IN","reason":"premise"}]}}