A production rollout exposes a contract mismatch between the UI boundary and the owning service. The affected area is distributed cache.
Repair the distributed cache cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.
Evidence
- Affected surface: Cloud-native full-stack / distributed cache.
- Observed failure family: plan cache invalidation.
- Scope policy: retained must equal true.