A company is not a person, a service is not a credential, and an affiliation is not an identity. These distinctions sound obvious until a public website has been revised for years and the same facts are copied into dozens of pages. At that point, a person’s biography can accidentally become the organization’s biography, an old affiliation can appear current, and a service can remain attached to a location where it is no longer offered.
Entity-based organization creates a cleaner model. The professional has a record. The organization has a record. The location has a record. The service has a record. Relationships connect them: a professional may work for an organization, a location may belong to a company, a service may be offered at a location, and an article may be authored by a professional. If one relationship changes, the underlying identities do not need to be rewritten.
Schema.org’s vocabulary illustrates the same idea through Person, Organization, affiliation, memberOf, credentials, and related properties. W3C provenance likewise models entities, agents, and activities separately. Dominator does not need to reproduce those standards internally in every detail to benefit from the principle: model the thing and the relationship as different facts.
This separation is especially valuable for history. A professional may have authored an article while employed by one organization and later move elsewhere. The article’s historical attribution remains true even though current affiliation changed. A flat page that treats authorship and employment as the same relationship can easily become misleading after the move.
Entity separation therefore makes maintenance safer. Instead of searching every page for a name, title, or address, the authority system can understand what changed and which public representations depend on that fact. It is an architectural choice that reduces future ambiguity.