Teams hunt the one true file, a JSON export, a Figma library, a tokens package, and assign religious status. Six months later, three expressions disagree and nobody knows which one production actually uses.
A single file in a drawer nobody opens isn't SSOT, it's a myth.
The contract layer
The contract layer looks like this:
- Semantic tokens are the contract.
- Figma variables express them for design.
- CSS and TypeScript express them for code.
- Docs explain usage.
- Agents diff drift between expressions.
Governed sync with automated drift detection is what actually ships.
Precedence beats purity
When expressions conflict, you need a rule, not a meeting. Usually: semantic token definitions win, implementations follow, Figma and code are peers under the contract. Breaking changes get semver and a changelog. No silent renames.
I score this in audits under the tokens and parity lenses. Most teams are green on components, red on sync. They wonder why the system doesn't stick.
Build the sync loop
Stop hunting the one true file. Build the loop: change the contract, propagate to expressions, agent diffs before merge, human approves. Repeat.
One source of truth was never a file, it was a discipline.