Tribal knowledge → governed record

Tribal knowledge is how the company really works — in Slack threads, DMs, standups, and the heads of people who have been around. It is fast and often correct. It is also invisible to new hires, hostile to agents, and fragile when someone goes on leave.

A governed record is the promoted form of that truth: owned, attributable, fresh enough to trust, and available through the company brain under policy.

This guide is a path, not a mandate to document everything.

What to promote (and what to leave)

Promote when knowledge is:

Asked repeatedly
Used in customer, compliance, or revenue-critical paths
Required for agents to act safely
Known by few, needed by many

Leave tribal (or light notes) when it is:

One-off debugging color
Rapidly changing speculation
Better left in the system of record (e.g. live ticket state)

A simple promotion pipeline

1. Capture

Mark candidates where they appear: emoji react, “save to brain” action, ticket tag, or weekly “things we keep repeating” note. Capture the claim and the pointer (link to thread), not a novel.

2. Draft

Write a short record: statement, context, links to sources, suggested owner. Prefer structured Markdown or a brain draft object over a long wiki essay. If you use git-owned knowledge, open a draft PR.

3. Own

A human team must accept ownership. No owner → no canonical status. Ownership includes re-verification, not only authorship.

4. Verify

Owner confirms the claim against reality (product, policy, CRM). Set last_verified. Resolve conflicts with older pages explicitly — do not leave duplicates ranking in search.

5. Promote

Move draft → canonical via review (PR, approval queue, or dual control). Agents that only read canonical memory should not see drafts unless policy allows.

6. Serve

Index and expose through human search and agent tools with access control. Cite the record ID in agent traces.

7. Retire

When reality changes, update or tombstone. Retirement is part of governance; silent contradiction is how tribal knowledge wins again.

Anti-patterns

Transcribe all Slack into the wiki — You recreated noise with worse search.
AI auto-promote without review — Useful for drafts; dangerous for canonical.
Owner = “Platform” — Diffuse ownership equals no ownership.
One giant FAQ — Prefer composable records agents can retrieve precisely.

Roles

Capturer — Anyone who notices repeated truth
Owner — Accountable for correctness
Promoter / reviewer — Enforces quality bar
Agent runtime — Reads per policy; may draft, rarely promotes

Tooling

You can run this pipeline on issues + git + CI, or with a company-brain product such as Mensara that supports draft/canonical flows and agent interfaces. The process matters more than the logo: capture → own → verify → promote → serve → retire.

Start this week

Pick ten questions your team already answers in Slack. Assign owners. Ship ten governed records. Point one agent or onboarding doc at them. Measure how often people still paste the old lore — that gap is your real backlog.