Where to find further discussion why "directed acyclic graph" for dependencies is a good approach

[ghferrari]

Spring Modulith includes some useful features which impose relatively easy-to-meet constraints on your code (e.g. external API vs hidden internals). However, it also imposes a "no cyclic dependencies" constraint which places a strong (indeed, absolute) and not-so-easy to meet constraint on the structure of your app and how your modules interact. This certainly seems to be a core intention of the Spring Modulith project: cf. @odrotbohm's comment that "a directed acyclic graph between modules is key to an evolvable architecture".

I'd like to understand this approach better, so I wonder if anyone has any pointers to discussions about why directed acyclic graphs are good for dependencies, what the tradeoffs might be, and how to resolve common difficulties in achieving it. Also happy to hear people's thoughts and experiences. (To be clear, I'm not here to contest this approach but to learn more about the motivation for it.)