FA-640 / Replication / Member archive

Admit a conflict resolution result: Replicas execute different resolver versions · case 05

The conflict resolution operation is admitted even though replicas execute different resolver versions.

Member previewVariant 5 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for admit a conflict resolution result. The record r must satisfy all of: set(r['parent_coverage'][0]) <= set(r['parent_coverage'][1]); all(a >= b for a,b in zip(r['clock_dominance'][0],r['clock_dominance'][1])); len(set(r['resolver_version'])) == 1; tuple(r['new_dot'][0]) not in [tuple(x) for x in r['new_dot'][1]]; r['result_domain'] >= 0. Extra tracing fields are ignored; validation does not mutate the record.

Why this case matters

A deterministic local contract for replication. Each negative fixture violates exactly one invariant. No transport timing, persistence, cryptographic verification, or full protocol implementation is claimed.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
Replicas execute different resolver versions	`true`	`false`	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.