FA-10497 / Caching / Member archive

A refresh failure destroys a still-usable stale cache entry · case 02

A refresh failure destroys a still-usable stale cache entry.

Member previewVariant 2 · 3 implementations · 4 checks per implementation

Case contract

For this stale-allowed cache policy, error preserves the prior value; success replaces it with body, including zero or None. Expiration eligibility is handled before this operation.

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	`null`	`"stale"`	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.