{"id":"conflict-resolution-architecture-is-split","text":"Conflict resolution is implemented in two disconnected modules: CRDTs encode resolution in their merge semantics (self-resolving), while the strategy enum covers only LWW and custom-merge — leaving no unified API and no bridge between the two approaches.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["crdts-are-self-resolving","strategy-enum-covers-two-of-three"],"outlist":[],"label":"The enum explicitly tracks that CRDTs are a third strategy but delegates to a separate module, creating an architectural seam where composition should exist"}],"dependents":["distributed-writes-have-compounding-correctness-gaps","two-incompatible-conflict-resolution-paradigms"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"conflict-resolution-architecture-is-split","truth_value":"IN","reason":"SL justification valid","antecedents":["crdts-are-self-resolving","strategy-enum-covers-two-of-three"],"label":"The enum explicitly tracks that CRDTs are a third strategy but delegates to a separate module, creating an architectural seam where composition should exist"},{"node":"crdts-are-self-resolving","truth_value":"IN","reason":"premise"},{"node":"strategy-enum-covers-two-of-three","truth_value":"IN","reason":"premise"}]}}