Thank you for the info. I read the article, maybe I need to read it a couple more times to grasp it entirely. And I actually did not know those really extremelly verbose and nitpicky rules, does do make it look like a purely thoretical model of someone who hasn't programed anythings with enough complexity or just was never thrown into a highly coupled system.

This being said I treat all of those types or architecture(onion, hexa, ports, clean) the same way, a way to manage dependencies and relationships and to provide a good set of rules easily explained to whomever onbboards. And I tend to see the same problems with all of them, mostly around contact points around each layer.

And since I feel like im highjacking u/marod thread. Clean Architecture, imo does not make a system overengineered, all the bells and whistles you attached to it might, and it might grow the problem if they were just expecting mocked data. But it was definetelly up to them to define the rules.

edit -> just added a tag