canonical-data-model

Design canonical data models and golden records for entity reconciliation.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill canonical-data-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canonical-data-model
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/canonical-data-model
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill canonical-data-model

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves the semantic chaos that occurs when multiple systems describe the same real-world entities differently, preventing the creation of fragmented, unreliable data silos.

Core Features & Use Cases

  • Identity Resolution: Implements deterministic and probabilistic matching to identify when disparate records refer to the same entity.
  • Survivorship Logic: Defines authoritative rules to assemble a single, trusted Golden Record from conflicting source data.
  • Boundary Governance: Establishes the Canonical Data Model as an integration contract, protecting internal domain models from external schema changes.

Quick Start

Apply the canonical-data-model skill to design the golden record assembly rules for the Person entity using the provided reference documentation.

Frequently Asked Questions about canonical-data-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a canonical data model for system integration?

A canonical data model acts as an anti-corruption layer across bounded contexts. It establishes an integration contract that reconciles differing source representations of real-world entities, preventing semantic chaos and protecting internal domain models from external schema changes.

What is the best way to define survivorship rules for a golden record?

The best way to define golden record survivorship rules is to establish authoritative logic that assembles a single, trusted record from conflicting source data, resolving semantic differences across multiple systems describing the same real-world entity.

How does identity resolution work for master data management?

Identity resolution for master data management works by applying deterministic and probabilistic matching techniques to identify when disparate records from multiple systems refer to the same real-world entity, enabling the creation of unified golden records.

When do I need an anti-corruption layer for bounded contexts?

You need an anti-corruption layer across bounded contexts when multiple systems describe the same real-world entities differently, causing semantic chaos. The canonical data model resolves this by acting as a stable integration contract between domains.

How to handle multi-domain governance in master data architecture?

To handle multi-domain governance in master data architecture, you design a canonical data model that enforces deterministic identity resolution and survivorship rules, ensuring trusted golden records across diverse system integrations.