[[Entity|Entities]] represent mutable domain concepts with consistent identity while protecting invariants and enforcing business rules. [[Repository|Repositories]] abstract the persistence logic of [[Aggregate|Aggregates]], and making Entities dependent on or referencing Repositories violates the [[Separation of Concerns (SoC)]] principle. Dependence on Repositories introduces technical details into the [[Domain Model]], reducing its clarity and focus. Entities should be reusable, and coupling them with Repositories compromises that reusability. Entities are easier to test by keeping Repositories separate, as their behavior remains isolated from persistence. This aligns with the [[Ports and Adapters|Hexagonal architecture]], which advocates for a [[Domain Model]] free from direct or indirect interactions with external systems ([[References#^512c44|Khorikov, 2020]]).