Monday Thought: The Metaphysics of ‘Single Source of Truth'

Today I did something deeply philosophical (and lightly operational):

I wrote a Confluence page.

Not because I love documentation. But because at a certain scale, organizations start to experience an odd form of metaphysical drift...where everyone is confident, everyone is misaligned, and nobody can locate the moment the plan became a vibe.

“Single source of truth” is one of those phrases that sounds like it belongs in a cathedral.

In practice, it’s closer to a negotiated settlement with reality.

A few observations from the field:

• A Confluence page doesn’t create truth. It creates a place where truth is allowed to exist without being interrupted. (Briefly.)

• “Alignment” is not an outcome. It’s a recurring cost. The page is just the invoice.

• The value isn’t in the words. It’s in what the words force you to do:

• The real magic of “single source of truth” is that it reduces the number of parallel universes the team is operating in.

And then, inevitably, you hit Publish—and the archetypes arrive like clockwork:

• The Timeline Sorcerer: “Can we ship by Friday?”

• The KPI Paladin: “How will we measure success?”

• The Architecture Astronaut: “Have we considered a service mesh?”

• The Process Cleric: “This needs the standard template.”

• The Platform Stoic: “What’s the blast radius?”

• The Security Oracle: “What’s the threat model?” (already correct, visibly tired)

Here’s the part that’s easy to look over:

A Confluence page is not documentation. It’s an artifact of commitment.

It’s the moment we stop saying “we all sort of agreed” and start saying “we decided (yayyyy!!) and here are the tradeoffs we accepted.”

Which is uncomfortable. Because writing things down removes a precious corporate resource:

plausible deniability.

Anyway, the page is live. Please don’t all ignore it at once.