A service boundary accepts valid traffic but mishandles duplicate, stale, or unauthorized records. The affected area is notification API.
Repair the notification API module boundary implementation so it ranks change-prone modules, preserves ownership boundaries, and identifies where characterization tests are required before extraction.
Evidence
- Affected surface: Express / notification API.
- Observed failure family: choose a safe refactoring boundary.
- Scope policy: contractVersion must equal 2.