The Knowledge Backbone: a single source of truth

How many times does the same piece of information exist, in a slightly different version, across a mid-sized organization? A customer repository in the CRM, another in the ERP, a third in a spreadsheet only one person knows how to update. TEAF's Knowledge Backbone starts from a principle simple to state and demanding to uphold: a piece of information has only one source of truth, and every architecture decision explicitly references it rather than duplicating it.

The invisible cost of duplication

Duplicated information doesn't cost much the day it appears — that's exactly what makes it easy to create. A team that needs a product repository and doesn't know one already exists builds a new one, faster than searching for the existing one. The cost shows up months or years later, as data inconsistencies nobody can explain anymore: two systems give a different answer to the same question, and nobody knows which one is right.

What the Knowledge Backbone actually contains

Not just business data: the Knowledge Backbone groups data, past decisions (via Living ADRs), dependencies between capabilities, and active constraints — regulatory, technical, contractual. It's the source every step of the TEAF loop consults before producing a decision, rather than one database among others queried occasionally.

Single source doesn't mean single copy

A common misunderstanding: "single source of truth" doesn't mean only one technical copy of the data may exist. Different systems can legitimately replicate a piece of information for performance or architecture reasons. What matters is that only one of those copies holds authority in case of divergence, and that this authority is explicitly declared — not implicitly inferred from "it's the system we've used the longest."

The link to the Living ADR and the Decision Fabric

The Knowledge Backbone isn't an isolated data repository: it's what the Decision Fabric consults before a decision is made, and what every Living ADR stays connected to afterward. A decision made without consulting knowledge already available elsewhere in the organization is exactly the mechanism that produces duplicated repositories and contradictory decisions documented among TEAF's anti-patterns. The Knowledge Backbone is the piece that makes that consultation possible — it still needs to be genuinely fed and consulted, which remains an organizational discipline, not a technical given.

• Duplicated information is cheap to create and expensive to undo — the cost shows up months after the decision that produced it.
• The Knowledge Backbone groups data, past decisions, dependencies and active constraints into a single reference point.
• Single source doesn't mean a single technical copy — but one copy that holds authority, explicitly declared.
• Its value depends on genuine feeding and consultation discipline, not just its technical existence.