Why Cairn
Trust how the work actually got done last month — not a document from 14 months ago
You already have somewhere to put documentation, and Cairn is not another one. The question is simply which account of your business you act on: what one person wrote down over a year ago, or what the people doing the work told us a few weeks ago.
The gap
You can have complete documentation and still not know how the work runs
Documentation is how-to knowledge — what someone should do. None of these sentences get answered by a better wiki, because what is missing is how-does knowledge: what actually happens, who really owns it, and as of when.
“Ask Dana, she's the only one who knows.”
One person is the single point of failure for a process the company depends on.
“The wiki says that, but that's not how we do it.”
Documentation exists and nobody trusts it, so everybody asks a human instead.
“We've been paying for that for two years?”
Tools renew because nobody can say which processes would break without them.
“Their last day is Friday.”
Years of context is about to walk out, and the handover doc was started yesterday.
Side by side
Two different kinds of knowledge, not two competing tools
The left column is not a rival product — it is what you can know when how-to documentation is the only record you have.
| Documentation alone | Documentation + Cairn | |
|---|---|---|
| What it records | What someone decided the process should be | What the process actually is, according to the people running it |
| Who does the work | Somebody is asked to write it up in their spare time | Cairn asks one short question at a time, in Slack or email |
| Knowing it is current | A last-edited date on the whole page, and hope | A freshness score per fact, with its own re-verification prompt |
| Who said it | One author, at one moment, for the entire document | Provenance per fact, traceable to the statement it came from |
| Conflicting accounts | The last editor wins and the disagreement disappears | Surfaced as a conflict and reconciled by the people involved |
| Workarounds | Invisible — the page still names the official tool | Recorded, because that is what people answer when asked |
| Tool spend | An expense line nobody can tie to a process | A registry of who uses what for which process, attested quarterly |
| AI and agents | Scrape whatever the page says, stale or not | Query it over MCP — permission-aware, with freshness and provenance |
Who it's for
You probably recognise one of these
Cairn is useful the moment more than a handful of people depend on knowledge that only exists in conversation.
Scaling teams
You grew past the point where everyone knows how everything works, and the people who do know are the bottleneck.
Operations leaders
You need to see the real process — not the documented one — before you can improve or automate any part of it.
Finance and procurement
You want to know which tools are genuinely load-bearing and which are renewing out of habit.
Teams adopting AI
Your agents are confidently wrong because the only thing they can read is documentation nobody has updated in a year.
Companies facing turnover
Someone critical is leaving in six weeks and most of what they know has never left their head.
Regulated and audited teams
You need to show not just what the process is, but who confirmed it and when they last did.