FA-052 / Distributed coordination / Member archive

A revoked writer overwrites its successor's state · case 02

An old lease holder writes after a higher fencing epoch has already committed.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Process [epoch,value] writes in arrival order. Accept epochs >= the stored epoch and return [largest accepted epoch,last accepted value]. Tokens are nonnegative and uniquely allocated per lease.

Why this case matters

Models storage-side fencing after delayed writes outlive a coordinator lease; lease expiry alone cannot stop a paused former holder from sending a request.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
late revoked writer	`[19, "stale"]`	`[20, "current"]`	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.