FA-74988 / CRDT convergence / Member archive

Delta causal context join: coverage ignores the dot cloud · case 03

A dot removed after out-of-order delivery comes back on join.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

A state is {"dots": [[element, replica, n]], "vv": {replica: n}, "cloud": [[replica, n]]}. A context covers (r, n) when n <= vv[r] or [r, n] is in the cloud. Join keeps dots present in both states plus dots of one state not covered by the other's context; contexts join by vector maximum and cloud union, then the cloud is compacted: an entry equal to vv[r]+1 advances vv[r], entries at or below vv[r] are pruned. Return elements, dots, vector and cloud, all sorted.

Why this case matters

Delta-state add-wins sets rely on causal contexts to tell removals from unseen additions.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
dot covered only by the peer cloud is dropped	`{"cloud": [], "dots": [["x", "a", 3], ["y", "b", 1]], "elements": ["x", "y"], "vv": [["a", 3], ["b", 1]]}`	`{"cloud": [], "dots": [["y", "b", 1]], "elements": ["y"], "vv": [["a", 3], ["b", 1]]}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.