FA-692 / Replication / Member archive

Delete a write-ahead log segment: Garbage collection deletes a segment still accepting writes · case 02

The wal retention operation is admitted even though garbage collection deletes a segment still accepting writes.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for delete a write-ahead log segment. The record r must satisfy all of: r['slowest_replica'][0] < min(r['slowest_replica'][1]); r['backup_pin'][0] not in r['backup_pin'][1]; r['archive_confirmed'] is True; r['segment_sealed'] is True; r['recovery_floor'][0] < r['recovery_floor'][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
Garbage collection deletes a segment still accepting writes	`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.