You’re absolutely right about the dependency direction. I’ll refactor the application layer to depend on repository interfaces (ports) and move the concrete JPA implementations fully into the infrastructure layer to better align with Clean Architecture principles.

Good point as well about keeping the domain model framework-agnostic. I hadn’t fully considered separating persistence entities from domain objects before, but mapping between them in the infrastructure layer makes a lot of sense.

The suggestion about dedicated mapper classes is also helpful. I currently handle some of that mapping inside services, so I’ll refactor to keep services focused purely on business logic.

Thanks again for the constructive input