design principle
Single Source of Truth
Single Source of Truth
Also known as · SSOT · source ownership · one authoritative source
Definition
A principle that gives one authoritative source the meaning and write authority for a fact while treating other representations as derived state. It clarifies ownership and synchronization boundaries; it does not mean copies never exist.
Searchable examples
- notes/
- courses/
- apps/console/sql/
Short example
notes/ owns note bodies, while the Admin DB and Fly export are derived publication states.
source → authenticated admin upsert → DB read / Fly snapshot
Compare with
Terms that compare with this term
- Database migrationDatabase Migrationschema changeA versioned change that moves operational data structures or constraints from one state to the next. Successful SQL syntax is a separate judgment from compatibility and recoverability.
- Cachederived storageA way to store a reusable copy of a result to reduce latency and source load. A cache hit proves speed, not freshness, authorization, or consistency.
- WebRTC cost gateWebRTC Cost Gatecost and feature boundaryA rule that separates WebRTC feature code from operational entry points and keeps expensive TURN, SFU, and video paths disabled until an explicit configuration and cost approval exist.
- Test fixtureTest Fixturetest setup stateA small bundle of input, state, and doubles prepared so one test can be reproduced under the same conditions. It differs from an evaluation dataset that represents an operational distribution.
- Object storageObject Storagefile byte storageA system that stores large file bytes under an object key with metadata. Storage success is not the same as business completion or authorization verification.
- Tauri capabilityTauri Capabilitydesktop permission boundaryAn explicit boundary that groups the commands and permissions available to a Tauri window. It grants only the needed capabilities instead of opening a local server or filesystem broadly for convenience.