FA-722 / Replication / Member archive

Acknowledge a replicated write concern: A write is reported successful after its response deadline · case 02

The write concern operation is admitted even though a write is reported successful after its response deadline.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for acknowledge a replicated write concern. The record r must satisfy all of: len(set(r['distinct_replicas'][0])) >= r['distinct_replicas'][1]; sum(r['durable_acks'][0]) >= r['durable_acks'][1]; len(set(r['failure_domains'][0])) >= r['failure_domains'][1]; all(x == r['write_binding'][0] for x in r['write_binding'][1]); r['ack_deadline'][0] < r['ack_deadline'][1]. 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
A write is reported successful after its response deadline	`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.