conflict-resolution-architecture-is-split

Status: IN

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.

Justifications

The enum explicitly tracks that CRDTs are a third strategy but delegates to a separate module, creating an architectural seam where composition should exist

Depends on (SL): crdts-are-self-resolving, strategy-enum-covers-two-of-three

Depended on by

JSON