When using Domain Events in distributed systems, publishing all events on a single bus exposes internal Bounded Context structure as a public API and risks leaking sensitive data. The solution is to separate internal and external messaging channels, keeping all events private by default and explicitly marking a small subset as public via annotations, marker interfaces, or a method. This preserves encapsulation and decouples internal implementation from the external API contract.
