A service boundary accepts valid traffic but mishandles duplicate, stale, or unauthorized records. The affected area is Kafka consumer.
Repair the Kafka consumer activity stream implementation so it splits activity after the configured inactivity gap and counts sessions per actor.
Evidence
- Affected surface: Spring / Kafka consumer.
- Observed failure family: sessionize event activity.
- Scope policy: retained must equal true.