FA-10445 / Caching / Member archive

A failed flush marks its cache entry clean · case 05

A failed flush marks its cache entry clean.

Member previewVariant 5 · 3 implementations · 4 checks per implementation

Case contract

Entry is [key,value,dirty]. Successful flush clears dirty; failed flush preserves prior dirty state and never changes key/value.

Why this case matters

A deterministic cache state transformation. Inputs are copied or treated as immutable; no remote storage, real clock, or concurrent interleaving is simulated.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 1	`["a", 3, false]`	`["a", 3, true]`	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.