kbrain

Governance

How to organize knowledge in your company with brains

Do not build one giant company knowledge base. Split it into focused brains - Engineering, Product, HR, Sales, Legal, plus personal brains - so AI assistants route to the right one and answers stay sharp.

Build your first knowledge brain

Create a brain

When companies first give AI access to their knowledge, the instinct is to build one giant knowledge base with everything in it. That is the wrong move. The better pattern is a set of focused brains - one per domain - that an assistant can route between, plus personal brains for individual work. This article shows how to structure it.

A brain per domain

Structure - 01
Focused brains, not one monolith
Each team owns a brain in its domain. Assistants route to the right one.
🛠️
Engineering
shared org-wide
Architecture decisions, runbooks, coding conventions, and internal API docs.
📦
Product
shared org-wide
Specs, roadmap decisions, and the reasoning behind what got built.
🧑‍💼
HR
shared org-wide
Policies, benefits, and onboarding - the questions everyone asks and no one wants to repeat.
🚀
Sales
shared org-wide
Positioning, competitive intel, and objection handling for every rep.
⚖️
Legal
shared org-wide
Policies, contract templates, and approved language teams can check before acting.
🙋
Personal
private to you
Your own notes, drafts, and context - private brains that stay with you.
Focused brains route better and stay owned. Each has a clear owner, a clear scope, and a clear audience.

Why not one monolithic knowledge base

  • Routing: an assistant picks the right brain from clear descriptions; one giant brain gives it nothing to choose between
  • Ownership: a domain brain has a domain owner; a monolith belongs to no one
  • Permissions: some knowledge is company-wide, some is not - separate brains let you scope each correctly
  • Freshness: a focused brain is easy to keep current; a sprawling one is impossible to maintain

Company brains and personal brains

Company knowledge lives in brains a Knowledge Manager shares org-wide, so every member reaches them through their own MCP connection. Personal knowledge - your drafts, your notes, your working context - lives in private brains only you can query. A member sees both in one connection, without the two ever mixing.

Start with the two or three domains where people ask the same questions most often. You do not need to map the whole company on day one - add brains as the need becomes obvious.

Related reading

Build your first knowledge brain

Subscribe to KBrain, create a brain from your expertise or your data, and make it available to Claude, ChatGPT, or any MCP compatible assistant.

Create a brain

Frequently asked questions

Should we build one company knowledge base or many brains?

Many focused brains, not one monolith. A brain per domain - Engineering, Product, HR, Sales, Legal - routes better, has a clear owner, and is easy to keep current. An assistant chooses the right brain from its description, which only works when brains are scoped.

How do company brains and personal brains coexist?

Company brains are shared org-wide by a Knowledge Manager and reach every member through their own MCP connection. Personal brains stay private to the individual. A member sees both in a single connection, and the two do not mix.

Where should we start?

Start with the two or three domains where people repeatedly ask the same questions - often HR, engineering runbooks, or sales positioning. Build focused brains there first, then add more as the need becomes clear. You do not have to map the whole company at once.