FA-60500 / Loyalty points ledgers / Member archive

Pending points hold period: repeat refund guard · case 05

A second refund message for the same order is processed again instead of being ignored.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Events: ["earn",day,order,pts] starts pending; points post (become available) on day >= earn day + hold. ["refund",day,order] cancels a live earn if day < earn day + hold ("cancelled"), otherwise claws it back ("clawed"; available may go negative); unknown or already refunded orders are "ignored". ["redeem",day,pts] spends available (posted - spent) points or returns "insufficient". ["query",day] returns [pending, available]. Return results list.

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
double refund	`["pending", "cancelled", "cancelled", "ignored"]`	`["pending", "cancelled", "ignored", "ignored"]`	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.