Nicely written article. It is a quite intersting approach, I like it's simplicity and integration into swiftui. though it is strongly coupled to the UI — which actually would mean it isnt really an architecture, which has as one requirement, that the UI has to be loosely coupled (Robert C. Martin: "the UI has to be an I/O device").

I like your accronym — though I am inclined to challenge you for it, as I believe that my Khipu architecture is simpler and more intuitive than your design. simpler, as it has no accidental complexity what-so-ever and more intuitive as it allows for code that resembles spoken English quite a lot.

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

older, but more advanced topics like testing: https://decodemeester.medium.com/khipu-rapid-and-sustainable-software-creation-in-swift-using-engineering-and-science-principles-312a933cce57?sk=8359f48cc06571e53de156db8cbc005c

you will find dozen of codes — some derived from commercially available apps — on my gitlab account: https://gitlab.com/vikingosegundo.

you see, I really appreciate your feedback as it isnt easy to find people who try out new things.

I hope to trick you into an intersting discussion with my "challenge".