FA-1563 / Replication / Member archive

Complete a streaming checkpoint barrier: A checkpoint is acknowledged while state exists only in memory · case 03

The checkpoint barrier operation is admitted even though a checkpoint is acknowledged while state exists only in memory.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for complete a streaming checkpoint barrier. The record r must satisfy all of: set(r['all_inputs'][0]) == set(r['all_inputs'][1]); len(set(r['barrier_id'])) == 1; r['state_flushed'] is True; r['inflight_captured'][0] == r['inflight_captured'][1]; r['sink_prepared'] == 'prepared'. 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 checkpoint is acknowledged while state exists only in memory	`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.