What is a canonical identity record, and why should one primary record define an entity?

In plain language

Imagine that different notebooks give different dates of birth for the same person. If everyone treats their own notebook as correct, the confusion grows. The primary record is the trusted reference against which other copies are checked.

Why this matters

Scattered identity records create false merges, outdated names, conflicting ownership and broken links between language editions. One primary record also makes change tracking easier.

Do not confuse

• A canonical identity record is not the entity itself.
• A canonical URL is a preference signal among web copies; it is not a complete identity-management system.
• The primary record does not replace independent outside evidence.

What should you do?

1. Give every entity a stable, unique identifier.
2. Keep canonical, alternative, former and language-specific names separate.
3. Record entity type, relationships, status and validity dates.
4. Create field-level links to sources and evidence.
5. Connect other pages and datasets to the primary record.

How do you audit it?

• Are there competing primary records for the same entity?
• Was the stable identity preserved across versions?
• Do changes in names and relationships have a history?
• Do external identifiers point to the correct entity?
• Does the primary record present its own statement as independent evidence?