{"id":"conflict-resolution-depth-scales-with-distribution","text":"Conflict detection infrastructure scales with distribution topology: single-node systems detect conflicts at mutation time via optimistic locking, multi-device systems detect at sync time via version vectors, and fully distributed systems maintain ongoing anti-entropy covering both writes and deletes — each matching resolution complexity to the divergence characteristics its topology demands.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["conflict-detection-varies-by-consistency-model","kv-anti-entropy-covers-writes-and-deletes"],"outlist":[],"label":"Topology determines whether conflict detection is point-in-time (optimistic lock), sync-time (version vector), or continuous (anti-entropy)"}],"dependents":["conflict-resolution-is-forward-only-at-all-distribution-levels","consistency-strategy-scales-uniformly-with-distribution"],"metadata":{"last_reviewed":"2026-06-05T18:21:49","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"conflict-resolution-depth-scales-with-distribution","truth_value":"IN","reason":"SL justification valid","antecedents":["conflict-detection-varies-by-consistency-model","kv-anti-entropy-covers-writes-and-deletes"],"label":"Topology determines whether conflict detection is point-in-time (optimistic lock), sync-time (version vector), or continuous (anti-entropy)"},{"node":"conflict-detection-varies-by-consistency-model","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-node-stores-sibling-versions","gdrive-version-vector-conflict","hotel-reservation-optimistic-locking"],"label":"conflict detection strategy correlates with data model — multi-writer replication retains all versions, collaborative editing uses device vectors, single-resource booking uses counters"},{"node":"kv-node-stores-sibling-versions","truth_value":"IN","reason":"premise"},{"node":"gdrive-version-vector-conflict","truth_value":"IN","reason":"premise"},{"node":"hotel-reservation-optimistic-locking","truth_value":"IN","reason":"premise"},{"node":"kv-anti-entropy-covers-writes-and-deletes","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-read-path-is-self-healing","soft-delete-prevents-distributed-resurrection"],"label":"without read repair, write divergence persists; without tombstones, deletes get resurrected — both mechanisms are independently necessary for full convergence"},{"node":"kv-read-path-is-self-healing","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-read-repair-on-get","kv-node-stores-sibling-versions"],"label":"Read repair + sibling detection make the read path an active consistency mechanism, not just a query"},{"node":"kv-read-repair-on-get","truth_value":"IN","reason":"premise"},{"node":"soft-delete-prevents-distributed-resurrection","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-store-deletes-use-tombstones","s3-delete-marker-hides-not-removes"],"label":"Both systems independently arrived at write-over-delete to prevent resurrection from unsynchronized replicas"},{"node":"kv-store-deletes-use-tombstones","truth_value":"IN","reason":"premise"},{"node":"s3-delete-marker-hides-not-removes","truth_value":"IN","reason":"premise"}]}}