System of record

A system of record is a designated place whose entries govern a particular domain or business process. Its authority is scoped: one system may govern contracts while another governs payments, and neither necessarily settles every related question. The designation is a governance decision about which record to rely on and how changes are controlled. It does not make every contained value true merely because the value is stored there.

A useful designation identifies the covered objects, responsible stewards, update process, evidence standard, and how conflicts with other sources are handled. Consumers need to know whether they are viewing the authoritative record or a delayed copy. Corrections should preserve enough history to explain past decisions, and access policies should match the sensitivity of the information. External registries can be authoritative for some fields while internal signed documents govern others.

For an organization defending every value, the system of record gives a clear answer to where a decision basis should be found and challenged. It needs provenance, time, and auditability to support that role. A single source of truth is often a desired consistency property across consumers; a system of record is the governed authority for a stated scope. Neither term excuses ignoring contradictory evidence or silently replacing a disputed value.

A system of record must be able to show the history of its values, who changed them and why, as set out in audit trail. It must have a defined route for corrections, so that a wrong value is fixed at the source and not patched downstream. It must publish changes to consumers and provide a way to ask what it said at an earlier time, as in as-of queries. It must define its scope and be clear about what it does not know: a system of record for registered offices is silent on trading addresses, and consumers who read silence as absence repeat the error described under the closed-world assumption.

Several systems of record may legitimately exist for different classes of fact. The question that matters is whether, for any given fact, exactly one of them is authoritative and everyone knows which. The article on auditing the multiple-sources-of-truth assumption offers a procedure for testing this. The article on minimum data provenance requirements lists what a value needs in order to be defended from the record.

For each important fact class, ask which system is the record and where the decision is written. Pick a fact and trace a correction from the record to its consumers. Ask what the record says about its own scope and currency. Ask whether any consumer edits its copy. Reproduce a past value from the record's history.