well, your architecture (and I dont care what an achitectural pattern is) isnt an valid architecture: The bare minimum for an architecture is that it must be independent from the UI. it does not know anything about the ui. the UI is a client. or as Robert C. Martin (aka Uncle Bob) puts it: "The UI must be an I/O device". But if you would remove the UI code from your app, nothing with any structure would remain.

Also I dont get why everybody — not only you — invests so heavily in accidental complexities (= non-domain-relevant codes; what the customer is not interested in) like presenters & coordinaters and alike.

if you are interested (and not only mad with me), I invite you to read about Khipu, a Clean-Architecture descent that does contain no non-domain code at all. it is free of any accidental complexity.

https://betterprogramming.pub/meet-khipu-a-boilercode-free-implementation-of-clean-architecture-in-swift-f76ccab82ff3?sk=a8938450032cb5aa67a4e7938c0b774a

https://decodemeester.medium.com/khipu-rapid-and-sustainable-software-creation-in-swift-using-engineering-and-science-principles-312a933cce57?sk=8359f48cc06571e53de156db8cbc005c

And I also invite you to watch my presentation on "Declarative axiomatic and provable correct systems in Swift" this November, 8th, as it will also be about Khipu with the audience being able to try it out themselves.

https://declarative.amsterdam/program