A service boundary accepts valid traffic but mishandles duplicate, stale, or unauthorized records. The affected area is Kafka consumer.
Repair the Kafka consumer cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.
Evidence
- Affected surface: Spring / Kafka consumer.
- Observed failure family: plan cache invalidation.
- Scope policy: retained must equal true.