Clean Architecture
Concentric layers with a strict dependency rule — source code dependencies point only inwards, towards higher-level policy.
Entities at the centre (enterprise-wide business rules), then use cases (application-specific rules), then interface adapters, then frameworks and drivers at the edge. Nothing in an inner circle may name anything in an outer one.
It is the same core idea as hexagonal architecture, expressed with more layers. Both exist to make the business rules independent of the delivery mechanism, the database and the framework — so that those can be replaced, and so the rules can be tested without them.
The practical caution is the same too: the dependency rule requires an interface and often a data transfer object at every crossing, and on a service whose "business rules" are validation plus a database write, that is a lot of files for very little protection. Apply it where the domain has real behaviour.