Company Brain Playbook · Chapter 2 · Free to read
What a company brain is.
A company brain is not a folder of notes, a better wiki, or “Confluence but tidy.” It is a working context system with five moving parts:
- Capture.Useful context is generated constantly — in Slack, meetings, tickets, emails, docs, CRM notes, support conversations, code reviews. Step one is knowing where it’s being generated.
- Curate. Raw captures are noise. Someone (or something, with review) cleans, deduplicates, classifies, and decides what matters. This is the step every failed knowledge base skipped.
- Store. Curated context lives in one versioned, structured, agent-readable place. Every document has an owner, a source link, and a freshness date.
- Use. Agents retrieve the right context automatically while doing real work — answering questions, drafting documents, writing code, preparing meetings. People stop pasting.
- Write back. When work produces a new decision, learning, or pattern, it flows back into the brain — through review, not free-for-all. The brain gets better every week instead of staler.
If any one of the five is missing, the system fails in a predictable way. No capture: the brain is empty. No curation: it fills with noise. No structure: agents retrieve weak context. No use: nobody maintains it. No write-back: it gets stale.
The one design principle that matters most
Storage is the back office. Agents are the front door.
The brain’s storage layer should be visited regularly by two or three maintainers. Everyone else interacts with the brain through their AI tools. They ask Claude to prep them for a meeting. They ask ChatGPT what was decided about pricing. The agent fetches from the brain; the person never browses a folder tree.
If your plan requires every employee to learn a new tool, navigate a repository, or “remember to check the brain,” the plan fails. People work where they already work. The brain comes to them.
And sometimes agents need a runtime.
For simple use, the front door might be Claude, ChatGPT, Cursor, or Copilot. For operational use, the front door might be a persistent company agent in Slack, Discord, CLI, webhooks, or scheduled jobs. That runtime is not the brain. It is the place agents run, load brain context, use tools, and propose updates back through review.
Keep the separation clean: the Company Brain stores trusted context; the runtime executes work around it.
This is 1 of 9 chapters.
The full playbook covers what to capture, what should never be ingested, the folder structure, how agents connect, and the 30-day pilot plan — free, sent to your inbox.