Why do retain cycles become invisible in large modular architectures?

Cycles become indirect across modules via delegates, closures, and service layers.

In modular apps, ownership is distributed across services, coordinators, and callbacks. This creates graph-based retention cycles that are not obvious locally but exist globally across modules.