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