A source of truth is a governance decision, not a compliment you give your favorite tool.
The phrase gets abused because most systems contain copies of important facts. CRM may show customer name, billing status, renewal date, owner, and support tier. Billing may show some of the same. The warehouse may show all of it. That does not mean each place has equal authority.
A system of record is the place allowed to speak for a specific kind of truth. CRM may own opportunity state. Billing may own invoices. ERP may own legal entities. Product may own usage events. HRIS may own employee status. The warehouse may reconcile and publish, but reconciliation is not the same as ownership.
Operators get hurt when this distinction is left implicit. Someone updates a copied field because it is convenient. A workflow routes work from the wrong version. A dashboard treats a replica as authoritative. Then the meeting becomes a court case about which screen "counts."
The decision has to be made at the fact level, not the system level. One tool rarely owns everything about an object. CRM might own commercial ownership while billing owns payment status and product owns activity. That is normal. The architecture needs to say so.
A practical source-of-truth rule names the object, attribute, authoritative system, change owner, sync path, exception process, and downstream consumers. If that sounds basic, good. Basic is what keeps truth from becoming political.
The question is not where data appears. The question is where the business is allowed to change it.
This is part 1 of 10 in Systems of Record.
