Why does Modulith flag cyclic dependencies for normal Spring event flows?

[shishir-polygon]

Hi builders,

I’m trying to understand the philosophy behind cyclic dependency detection in Modulith.

In a typical Spring application, I have two modules (slices) that communicate via events:

Module A publishes an event.
Module B listens to that event and, based on business logic, may publish another event back to Module A or call a service in Module A.

In plain Spring, this works perfectly at runtime. However, when I run ModulithVerifier, it flags a cycle:
Slice A -> Slice B -> Slice A

My question is:

Is the detection of cycles intended to prevent runtime issues, or is it purely an architectural/design enforcement?
Is it expected that normal two-way event flows between slices always trigger a violation?
Are there recommended patterns to handle legitimate two-way event-driven communication without creating a cycle violation?

It would be great to understand the design thinking behind this and any recommended approaches.
Thanks in advance!