What Belongs to the Aggregate Root

Question

This is a practical Domain Driven Design question:

Conceptually, I think I get Aggregate roots until I go to define one.

I have an Employee entity, which has sur

Answer 1

I was wondering what the conclusion would be?

'Violations' become a root entity. And 'violations' would be referenced by 'employee' root entity. ie violations repository <-> employee repository

But you are consfused about making violations a root entity becuase it has no behavior.

But is 'behaviour' a criteria to qualify as a root entity? I dont think so.