FA-94293 / Shift rostering labor rules / Member archive

Back-to-back shifts rejected as overlapping during bidding · case 03

Workers cannot bid for a shift that starts when their held shift ends.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

workers [id, hire day, max shifts]; shifts id -> [start, end]; prefs id -> ordered shift ids. Bidding rounds repeat until nobody picks: in each round workers in seniority order (earlier hire day, then id) take their first preferred shift that is untaken and does not overlap a shift they already hold (touching is fine), one pick per round, until reaching their maximum. Return worker -> picks in order.

Why this case matters

Seniority bidding is a common contractual roster procedure; each rule change reallocates shifts.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: adjacent shift overlap 1	`{"w0": ["s3"], "w1": ["s0"], "w2": ["s1"]}`	`{"w0": ["s3"], "w1": ["s0", "s2"], "w2": ["s1"]}`	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.