Regarding the point that the REST Adapter has a unidirectional source code dependency on the Application, while the Application does not have any source code dependencies on the outer layers, I'm puzzled about how to handle the following scenarios:

1.Complex conditional queries and pagination information: How can these query conditions and pagination details be passed from the REST Adapter to the persistence layer?

2.A single large form submission from the user: This form may involve multiple business entities, requiring it to be split into different business entities for processing and persistence according to business rules. Does this large form correspond to the WebModel in the example (for instance, a parameter in the Controller marked with the @RequestBody annotation)? Does the Application layer need to establish a "pseudo" domain object identical to this WebModel to receive and handle this request?

Thus, the time complexity for both operations is: O(n log n)"

It should be O(log(n)),
according to my text books and
https://stackoverflow.com/questions/28819327/time-complexity-of-inserting-in-to-a-heap

I tried that, but it was complaining about the bootstrap module calling the constructurs and the tests accessing basically any other code. So I eventually decided to write this custom ArchUnit test.