system-of-record

What problem does it solve?

The System of Record skill makes the unified data model conversational so teams can stop guessing where fields and records originate. It addresses fragmented identities, inconsistent schema names, and missing domain-level models by defining canonical tables, a Person.id identity anchor, and explicit domain mappings to the systems that currently hold fragments of the truth.

Core Features & Use Cases

• Canonical Schema Reference: Exposes the nine-domain SoR schema (People & Auth, Groups, Events, Achievements, Member Context, Notifications, Payments, Matching, Invitation Campaigns) so users can map platform-specific fields to canonical names.
• Identity Resolution Guidance: Explains current identity gaps and the intended Person.id resolution path across HubSpot, PostHog, Society, Customer.io, and legacy systems.
• Gap Analysis & Advisory: Identifies where data is missing or inconsistent, lists unresolved architectural concerns, and advises downstream skills (/data-intel, /data-model-discovery, /investigation) on canonical joins and expected tables.
• Use Case: Cross-platform analysts use it to determine the authoritative field for "graduation date", to plan joins for cohort analysis, or to evaluate whether a new data source fills a SoR gap.

Quick Start

Ask /system-of-record where graduation data lives, what the canonical field name is, and which systems currently contain that data.