FA-074 / Distributed coordination / Member archive

Failover routes a session behind its observed version · case 04

The fastest replica returns data older than a version this session has already seen.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Replicas are [ID,applied version,latency]. Return [ID,version] for the minimum (latency,ID) among versions >= session floor, or None if no replica qualifies. Version order is globally comparable in this model.

Why this case matters

Models session-consistent replica routing after a client moves between read endpoints, including the distinction between a required consistency floor and unnecessarily seeking the newest state.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
stale fast replica	`["a", 13]`	`["b", 14]`	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.