Live on Product Hunt Intraface launched today. Less steering, more vacations. See the launch
Start for free

What is a single source of truth?

A single source of truth is the one place where a piece of information is kept and edited, so every other copy, view or report is derived from it rather than maintained on its own. When the fact changes, you change it there once, and nothing else can quietly disagree with it.

Part of Glossary: the terms behind MCP, coding agents and shared pages, defined plainly.

How it works

Two people edit one page, and the slides and the report are generated from it, so nothing else needs editing when a fact changes.a designeran engineeredited here onlythe one pagewhere the facts livethe slidesgenerated from itnever edited by handthe status reporteditseditsrebuilt from itrebuilt from it
  1. Pick one home for each fact: the figure, the design token, the decision. Everything else points at it or is generated from it.

  2. Edits happen only there. A copy that someone edits by hand stops being a copy and becomes a second truth.

  3. Derived views (a slide, a report, a summary) are rebuilt from the source, so they can lag behind it but they cannot drift from it.

  4. Keep a history of the source, so when two people disagree about what it says, you can see who changed it and when.

Source: Wikipedia: Single source of truth

Single source of truth versus a single version of the truth

The two phrases get swapped, and the difference is where edits happen. A single source of truth is the place a fact is mastered: you change it there and nowhere else. A single version of the truth is an agreed view assembled from several sources, the way a data warehouse reports on numbers that were born in other systems. The warehouse is where everyone looks, but it is not where anyone edits, so a fix in the warehouse does not fix the record upstream. If you want copies to stop disagreeing, you need the first thing, not the second.

The test is simple. Ask where a given fact is edited. If the answer is "in two places", you have two sources, however often they happen to agree.

Example: a team page several agents edit

Suppose a team keeps its launch plan as one HTML page on a shared board, and each person's coding agent edits that page rather than a private copy. Marketing's agent updates the dates, engineering's agent updates the dependency list, and the slides for Friday are generated from the page, not written by hand. The page is the source. Rebuild the slides and they match; edit the slides directly and you have just created a second truth that will drift the moment the dates move again.

On Intraface the board's collab.md plays the same role for the house rules: every agent that pulls the board reads it, so the rules exist once instead of being pasted into each agent's prompt.

Why it matters

Duplicated facts do not fail loudly. Both copies look fine until someone acts on the stale one. With a single source, the cost of a change is one edit, and the cost of being wrong is confined to one place you can inspect and fix. It also makes history meaningful: if the fact lives in one file with version history, you can see who changed it and when, which you cannot do across five copies.

There is a trade-off. One source means one place to contend over. When many people, or many agents, edit it, you need a way to order their writes and to merge or reject the ones that collide. That is where version numbers, three-way merges and merge conflicts come in; they are the price of having one source instead of many.

Common mistakes

  • Declaring a source without removing the copies. The wiki page says "canonical" but the spreadsheet is still edited. Delete the spreadsheet or make it a read-only export.
  • Making the summary the source. A dashboard or report that aggregates other systems is a convenient view, not the place to edit. Fixes have to go upstream.
  • Treating a chat thread as the source. Decisions made in chat need to land in the document, with the date, or the document stops being trusted.
  • Guarding it with one owner. A single source does not need a single editor. It needs a single location and a record of edits. Bottlenecking every change on one person is how copies start.

FAQ

Is a single source of truth the same as a database?
No. A database can hold several copies of the same fact in different tables, and a team can keep its source of truth in a document or a page. The term is about where a fact is edited, not about the storage technology.
Can a single source of truth have more than one editor?
Yes, and usually it should. What makes it a single source is that there is one location and every change goes through it. With many editors you need version history and some way to order or merge their changes, so nobody overwrites anyone else.
How do you keep a single source of truth from going stale?
Make it the thing people actually use. If the slides or the status page are generated from the source, people have a reason to update the source. A canonical document nobody reads goes stale because the real work moved somewhere else.

Stop sending HTMLover Slack.

Create an account in a minute, connect your coding agent, and make your first board.