I'm wondering how a rule tailored for a specific UI is handled in a context of DDD and hexagonal/onion architecture?
For example, if you have a screen for an inventory app where you can create product which are displayed as a list. The specifications tell you that newly created item should appear at the top of the list but the user can reorganise item order just for visualisation purpose.
I'm a bit reluctant to store some kind of order property in my product entity because if UX change the domain is impacted.
So I wonder what are my other options to handle theses use cases?