persistence VS jmolecules

Have you never used the Servlet API? JPA? Those validation annotations from the javax.validation package? JAX-RS to define REST Endpoints? CDI for dependency injection?

You can open issues related to the API here: https://github.com/eclipse-ee4j/jpa-api/issues

Spring Modulith is the successor of Oliver Drotbohm's Moduliths project (with a trailing S). It uses both ArchUnit and jMolecules. At the time of this writing, it's experimental.

You could move towards modeling your code around DDD building blocks (like aggregates etc.) and declare those concepts in code explicitly using jMolecules types. There is a dedicated jMolecules Integrations ByteBuddy Plugin, that would then add the necessary boilerplate code and default mappings required by the expressed concept. This makes the code shown here a fully working JPA model. You can argue that the lack of JPA oddities is odd itself in the first place but I like the idea of expressing the architectural concept explicitly and the technology integration completely flowing from that.