Master Entity Registry¶
Software / tool — instantiates Entity Individuation Criteria Design
The system of record that stores accepted entities, their identifiers, aliases, lineage, and cross-system links under the governing individuation criteria.
Criteria that live only in a document govern nothing until something holds the entities they produce. Master Entity Registry is that operational store: the running system that persists the accepted inventory of individuals, mints and binds their identifiers, keeps their aliases and merge/split lineage, and maintains the crosswalk that maps a registry entity to how other systems refer to the same thing. Its defining feature is that it is a consequence store, not a rule store — it does not decide same-as or author unity; it records the decisions those mechanisms make and serves them as durable, resolvable reference. It is the place you go to ask "which individuals exist, under what identifiers, and how does system X's key for this entity map to ours?" The registry is where the archetype's criteria become queryable, standing infrastructure.
Example¶
A banking group runs a legal-entity registry across its subsidiaries, funds, and trading desks. Each legal entity accepted under the governing criteria gets a registry record: an internal key, its Legal Entity Identifier (LEI), its former names as aliases, and lineage links recording that this entity is the post-merger successor of two entities that combined last year. When the credit-risk system, the regulatory-reporting system, and the trade-booking system each refer to that entity by a different code, the registry's crosswalk holds the correspondences, so a query in one system can resolve to the canonical individual.
A trader searches for a counterparty under its old name; the registry resolves the alias to the surviving entity and returns the current identifier plus the merger lineage, so exposure is aggregated against one counterparty rather than split across a stale name and a current one. The registry did not decide that the two pre-merger firms became one — the succession rule did — but it is what makes that decision usable at query time, consistently, across every consuming system.
How it works¶
- Persist accepted individuals. Store each entity the criteria have accepted as a countable record with status (active, merged, retired), so the live inventory is always answerable.
- Bind and resolve identifiers. Mint canonical keys, attach external identifiers and aliases, and resolve any of them to the surviving entity — identifiers point to entities, never substitute for them.
- Keep lineage. Record merge, split, and succession links so a historical reference still resolves and a bad merge can be traced and unwound.
- Maintain the crosswalk. Map registry entities to how partner systems individuate and key the same thing, flagging where a partner's grain differs.
Tuning parameters¶
- Match automation — how much resolution the registry performs itself versus deferring to the resolution policy. More automation is faster but risks embedding a match score as a de facto criterion.
- Lineage retention — how deep the merge/split history is kept. Deeper history enables reversal and audit but grows the store and slows queries.
- Crosswalk coupling — how tightly partner-system keys are bound in. Tight coupling gives seamless resolution but propagates a partner's re-individuation as churn.
- Write authority — who may create or merge records directly versus only through governed pipelines. Looser write access is convenient but invites ungoverned entities.
When it helps, and when it misleads¶
Its strength is durability and resolvability: it turns criteria into infrastructure that answers "which individuals exist and how do they map across systems" at scale, with lineage that makes reference survive renames, merges, and successions.
Its failure mode is the archetype's cardinal sin — treating the registry key as the entity criterion. A registry that mints identifiers faster than the criteria justify manufactures false precision: a stable, authoritative-looking key bound to a contested or unsettled entity. Master data management calls the canonical record a "golden record," but a golden record is only as trustworthy as the same-as rule that built it, and a shiny identifier can lend unearned confidence to a merge that should never have happened.[n1] The guarding discipline is to keep the registry strictly downstream of the criteria — it stores and resolves decisions made elsewhere, preserves reversible lineage so wrong merges can be undone, and never lets the presence of a clean identifier stand in for a warranted identity.
How it implements the components¶
countable_inventory_register— it is the live, queryable store of accepted individuals with their status; the persistent register the archetype calls for.identifier_binding_layer— it mints canonical keys and binds external identifiers and aliases to entities, resolving any to the survivor.cross_context_identity_crosswalk— it maintains the mappings from its entities to how partner systems key and individuate the same things.
It does not author the identity_criterion it stores decisions under — that same-as warrant is set by the Entity Resolution Policy; the registry persists and resolves those rulings, it does not make them.
Related¶
- Instantiates: Entity Individuation Criteria Design — the operational store that makes the accepted inventory durable and resolvable.
- Consumes: Entity Resolution Policy — supplies the same-as rulings the registry records and binds.
- Sibling mechanisms: Entity Resolution Policy · Individuation Criteria Charter · Count Impact Assessment · Split/Merge Decision Tree · Versioned Identity Rulebook · Entity Definition Workshop · Identity and Unity Test Checklist · Edge-Case Adjudication Panel
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Master Entity Registry operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it the system of record that stores accepted entities, their identifiers, aliases, lineage, and cross-system links under the governing individuation criteria.
Independent corroboration: The frozen evidence defines Master Entity Registry as 'The system of record that stores accepted entities, their identifiers, aliases, lineage, and cross-system links under the governing individuation criteria', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The registry's accepted entities, identifiers, aliases, and cross-references continue the library and archival tradition of authority control. Computer science contributes database identity, linkage, and system-of-record implementation.
Related originating lineages:
- Computer Science & Software Engineering — Database systems operationalized entity registries, identifiers, lineage, and cross-system links.
Review resolution: The Library of Congress MARC Authority standard explicitly represents authorized names, references, and the sources consulted to establish them. That is a closer provenance match to a governed entity-and-alias registry than database implementation alone. The alternates are retained only as formative or independently established origins, not because the mechanism can be applied there. origin_mode=cross_disciplinary_synthesis states the provenance relationship; domain_reach=multi_domain separately records breadth because independent established uses occur in several fields. confidence=high reflects the strength and specificity of the evidence; encyclopedia_synthesis=false because the entry generalizes an established mechanism without inventing a new composite.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.loc.gov/marc/authority/ — The Library of Congress authority standard documents authorized headings, cross-references, and source provenance.
- https://www.loc.gov/standards/mads/userguide/authority.html — The Library of Congress MADS guide describes authority records and their controlled identifiers and variants.
Notes¶
[n1] In master data management, the golden record is the single, reconciled, authoritative version of an entity's data assembled from many sources. Its danger here is reputational: the record looks canonical by construction, which tempts consumers to trust the identity behind it more than the underlying same-as evidence warrants. ↩