FA-45677 / Data systems / Member archive

Watermark release retains arrival order instead of event-time order · case 02

Watermark release retains arrival order instead of event-time order.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Process event actions [event,time,id] and watermark actions [watermark,time,None]. Maintain monotone watermark; events older than it go to late output. On a watermark, release buffered events with time strictly below watermark ordered by (time,id). Return [emitted,late,sorted-pending].

Why this case matters

A bounded deterministic data engine model makes representation and changelog faults reproducible.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
event time ordering	`[[[4, 10], [2, 11]], [], []]`	`[[[2, 11], [4, 10]], [], []]`	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.