data-source-ssot

name	data-source-ssot
description	Catch the "same data lives in two differently-keyed tables, two features read different ones, they silently disagree" failure class. Use whenever two models hold overlapping fields, a reader picks a pricing/config/settings store, or two surfaces (e.g. Margot vs the estimator, dashboard vs API) should show the SAME number but might not.
automation	manual
intents	schema, prisma, tenancy, source-of-truth, pricing, config, drift, resolver, organizationId, userId

Data-Source SSOT (single source of truth)

The class: the same logical data is stored in two tables keyed differently, one code path reads one and another reads the other, so they drift and two features answer the same question with different numbers — with no error anywhere.

Golden rule: For any logical fact, exactly one store is authoritative and exactly one resolver reads it. If two readers can disagree, you have two sources of truth — a bug waiting for a customer to notice.

The case that proved it (RA-7026)

• Contractor pricing lived in OrganizationPricingConfig[organizationId] (written by the setup wizard, read by Margot) AND CompanyPricingConfig[userId] (read by every estimator: rate-engine, /api/calculate, nir-cost-estimation). Field-identical tables, different tenancy keys, linked only by a one-time backfill.