FA-60405 / Loyalty points ledgers / Member archive

Expiring point lots: sweep report unit · case 05

The expiry notice says "2 points expired" when two lots holding hundreds of points expired.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Events ["earn",day,pts,ttl] create a lot expiring at day+ttl (usable through that day); ["redeem",day,pts] draws only unexpired lots, soonest expiry first (ties by earn day), rejecting with "insufficient" when unexpired points are short; ["sweep",day] removes lots whose expiry is before day and reports the points removed. Emptied lots are dropped. Return {results, lots:[[expiry, earn_day, pts]]}.

Why this case matters

Member point balances, statements and the program liability depend on this ledger rule.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
sweep reports points	`{"lots": [[103, 3, 60]], "results": [10, 10, 103, 2]}`	`{"lots": [[103, 3, 60]], "results": [10, 10, 103, 205]}`	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.