Single Source of Truth

An SSOT is the definitive, approved version of a specific data entity or fact. It is designated as the sole official source, superseding all other copies or derivations. This eliminates conflicting versions and establishes clear data provenance.

• Golden Record Creation: For master data (e.g., Customer, Product), the SSOT is often a golden record synthesized from multiple source systems.
• Governance Mandate: Its authority is enforced by formal data governance policies, not just technical implementation.
• System of Record: It acts as the ultimate system of record for its defined domain, serving as the reference point for all downstream consumers.

The SSOT must be reliably accessible to authorized systems and users through well-defined interfaces. It is not a hidden or isolated repository but a central hub for data consumption.

• Standardized APIs: Access is typically provided via RESTful APIs, GraphQL endpoints, or standardized query languages like SPARQL for semantic graphs.
• Unique Identifiers: Every entity within the SSOT is assigned a persistent, unique identifier (URI, UUID) that allows it to be precisely referenced and linked.
• Virtual or Materialized: The SSOT can be a physically integrated data store or a virtualized layer (logical data fabric) that provides a unified view without moving data.

Data within the SSOT maintains internal consistency and is the basis for synchronizing dependent systems. Changes are propagated to subscribing applications to prevent drift.

• Transaction Integrity: Updates adhere to ACID (Atomicity, Consistency, Isolation, Durability) or eventual consistency guarantees appropriate to the architecture.
• Change Data Capture (CDC): Mechanisms like CDC log changes and publish events to notify downstream systems of updates.
• Versioning & Temporality: Critical SSOTs support temporal data models or versioning to track how facts change over time, forming a temporal knowledge graph.

An SSOT provides a unified, contextualized view by integrating data from disparate source systems. It resolves semantic conflicts and aligns entities using shared models.

• Semantic Layer: It often functions as the core semantic layer, using an ontology to define business concepts and their relationships.
• Entity Resolution: Implements entity resolution algorithms to deduplicate and link records referring to the same real-world object.
• Cross-Domain Links: It establishes explicit relationships between entities across different domains (e.g., linking a Customer to their purchased Products and Support Tickets).

The integrity of the SSOT is maintained through active data governance and quality controls. It is not a static repository but a managed asset with clear stewardship.

• Data Quality Rules: Automated checks enforce rules for validity, accuracy, completeness, and timeliness at the point of ingestion.
• Provenance Tracking: Full data lineage is maintained, documenting the origin of each fact and the transformations applied.
• Access Control: Role-based access control (RBAC) or attribute-based policies govern who can read or update specific data elements.

The SSOT is the primary source for downstream analytics, applications, and AI systems. It feeds data products, reports, and machine learning models, ensuring they operate from a common factual base.

• Feeds Data Products: Serves as the source for domain-oriented data products in a data mesh architecture.
• Grounds AI & RAG: Provides deterministic factual grounding for Retrieval-Augmented Generation (RAG) and knowledge graph-based RAG architectures, eliminating hallucinations.
• Enables Federated Queries: Acts as a central node in federated query systems, providing authoritative answers within a broader data fabric.

An architectural framework that uses a knowledge graph as a unifying semantic layer to provide integrated, contextualized, and governed access to enterprise data across disparate sources. It is the primary implementation pattern for a true SSOT.

• Core Mechanism: Applies ontologies and semantic models to create a common business vocabulary.
• Key Benefit: Enables data to be queried for meaning and relationships, not just retrieved by location.
• Contrast with SSOT: While an SSOT is the principle, a semantic data fabric is the architecture that enforces it.

A comprehensive discipline and set of technologies for defining, managing, and governing an organization's critical shared data entities (e.g., Customer, Product, Supplier) to provide a consistent point of reference.

• Primary Focus: The governance, quality, and lifecycle of core business entities.
• Relationship to SSOT: MDM programs are often responsible for creating and maintaining the golden records that serve as the SSOT for master data domains.
• Key Process: Involves identity resolution, record consolidation, and stewardship workflows.

The single, authoritative, and consolidated version of truth for a specific core business entity, created by merging, cleansing, and validating data from multiple source systems.

• SSOT Instantiation: A golden record is the physical or logical manifestation of the SSOT principle for a given entity (e.g., the definitive 'Customer X' record).
• Creation Process: Built using algorithms for entity resolution, survivorship rules, and data quality checks.
• Usage: Served to downstream systems via APIs or a shared data hub to prevent replication of logic and inconsistency.

A decentralized sociotechnical architecture that organizes data by business domain, treating data as a product owned by domain-oriented teams.

• Contrast with Centralized SSOT: Data Mesh advocates for domain-oriented decentralization of data ownership and architecture.
• Alignment with SSOT: Each domain is responsible for providing its own domain data products as the SSOT for its area. Inter-domain consistency is achieved through federated governance and explicit product contracts, not a single physical database.
• Key Principle: Shifts from a central monolithic data platform to a distributed ecosystem of interoperable data products.

The set of policies, standards, and processes for managing the lifecycle of semantic artifacts—such as ontologies, taxonomies, and mappings—to ensure consistency, quality, and alignment with business goals.

• Enables SSOT: Without governance, the shared vocabularies and models that define meaning in an SSOT become fragmented.
• Key Activities: Includes ontology versioning, change management, stakeholder collaboration, and compliance monitoring.
• Outcome: Creates a governed, trusted semantic layer that makes the SSOT interpretable and reliable across the enterprise.

A data integration technique that provides a unified, abstracted view of data from multiple disparate sources in real-time, without requiring physical data movement or replication.

• SSOT Delivery Mechanism: Can be used to present a virtualized single source of truth, where the authoritative data remains in source systems but is accessed through a single logical interface.
• Key Technology: Relies on query federation and sophisticated query optimization to retrieve and join data on-demand.
• Use Case: Ideal for providing real-time access to an SSOT where data latency or regulatory constraints prevent physical consolidation.