Skip to content

Source Of Truth Assignment

Assign authoritative status to one representation or system so conflicting versions can be resolved consistently.

The Diagnostic Story

Symptom: Different teams make different decisions because they are consulting different records, and no governed rule determines which one controls. A stale copy overrides the current record because it is more visible or more convenient, and corrections made in local systems never reach the source that downstream systems trust. Arguments focus on whose spreadsheet, memory, or document is real rather than on a shared authority rule. Nobody can reconstruct after the fact which version was treated as official or why.

Pivot: Designate a scoped authoritative source, define what it governs, assign update and stewardship rights, specify conflict and exception rules, and govern how dependent representations synchronize, defer, challenge, or retire — rather than letting precedence be decided informally on each conflict.

Resolution: Decision inconsistency drops because actors know which source governs and how to challenge it, and accountability for maintaining that state is explicit. Stale copies, local spreadsheets, and old branches stop overriding current governing state because the authority relation is defined rather than contested. Audits can reconstruct why a value was treated as official because the stewardship trail exists.

Reach for this when you hear…

[data engineering] “There are three tables that claim to be the user table and they disagree on half the rows — we need to pick one as the source of truth and treat the others as derived.”

[regulatory compliance] “The audit will ask which system was authoritative for these figures — if we can't answer that question before the audit, we have a governance problem.”

[product management] “The roadmap in Confluence, the one in the slide deck, and the one in the product manager's head are all different — until we designate which one is real, every planning meeting starts from scratch.”

Mechanisms / Implementations

  • Access and Update Rights Matrix: A grid mapping actors and systems against fields and states to who may view, edit, approve, override, and publish, converting 'this is authoritative' into an enforceable set of who is allowed to change it.
  • Authoritative Policy Repository: Holds the current policy statements in one governed location so that outdated copies, summaries, and local interpretations must be resolved against it.
  • Canonical Registry: Maintains the one official list of entities and their canonical identifiers that every system looks up, with a mapping from aliases and legacy codes back to the canonical entry.
  • Change Log and Audit Trail: Preserves an append-only record of every change to authoritative state — who, when, why, under what right, and what it propagated to — so the source's history is accountable and reconstructable.
  • Conflict Resolution Workflow: Routes a detected disagreement between representations through review, reconciliation, escalation, or authoritative override, applying a standing precedence rule so the same conflict resolves the same way every time.
  • Deprecation and Forwarding Notice: Marks an obsolete representation as no longer authoritative and attaches a forwarding pointer to the current source, so anyone still holding the old copy is redirected rather than misled.
  • Golden Record Consolidation: Merges many duplicate and conflicting records of the same entity into one consolidated 'golden' record, picking the surviving value field by field with survivorship rules.
  • Master Data Management: A standing enterprise program that assigns data stewards, carves which system is authoritative for each data domain across business units, and sets the synchronization and duplicate-resolution policy the point mechanisms execute.
  • Official Record Policy: Declares which document, filing, or register is the official record for legal, compliance, and historical purposes, ranking it above informational copies and defining the exceptions under which another may temporarily stand in.
  • Source-Control Main Branch: Treats one branch — main or trunk, reached through a reviewed merge — as the authoritative state of code, config, or content, so every working copy is provisional until it lands there and merge rights gate what may.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 14 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

System-of-Record Assignment · domain variant · recognized

Designate one operational system as authoritative for a defined entity, field, state, or transaction class.

Golden Record Assignment · implementation variant · recognized

Create or designate a consolidated record that resolves duplicates and conflicting attributes into a governing representation.

Authoritative Policy Repository · governance variant · recognized

Designate one governed repository as the current authority for policies, procedures, standards, or rule interpretations.

Official Record Assignment · domain variant · recognized

Identify which document, filing, register, or archive entry has official standing when informal, draft, duplicate, or historical records conflict.

Branch Authority Assignment · temporal variant · recognized

Designate a branch, trunk, release, or reviewed merge path as authoritative among many evolving versions.

Decision Authority Source Assignment · governance variant · candidate

Identify which actor, role, committee, rule, or decision record governs when competing interpretations or approvals exist.