Shipping without a use-case tier

The textbook stack puts an interactor between the presentation layer and the repository. A mid-size, feature-broad app can ship with zero of them and still have a boundary worth the name, because the boundary was never the interactor — it was the interface.

What holds it up instead: