Is the architecture built correctly (Aggregate - Repository - Service - Controller)?

Question

Problem-Based Design

Need advice on application architecture.
There is a website, for example, a real estate aggregator. To store information about objects
, I use RealtyObject Aggregate, consisting of RealtyObject Entity + RealtyImages Entity plus some other entities. In these entities, only getters and setters, nothing else.
Everything related to reading operations, saving entity properties - lies in the RealtyObject Repository and RealtyImages Repository.
Actions with the aggregated RealtyObject Aggregate object (all business logic) are accordingly placed in the RealtyObject Service, which will already be interacted with from the controller.
I would like to know if I correctly grasped the concept of building such systems?