What is a company brain?
A company brain is one shared memory of what a company knows: the decisions it has made and why, how its systems work, who owns what, and the conventions it follows. People can read it, and so can every AI assistant they use, so nobody's assistant starts from zero.
In short
- A company brain holds short facts rather than documents: “The billing service runs on Postgres and Stripe”, “Priya is the account lead for Acme”.
- Its busiest readers are now AI assistants. Claude, ChatGPT and Cursor each start every conversation knowing nothing about your company unless something tells them.
- It needs three things a wiki does not have: assistants that write to it as they work, facts that retire when they stop being true, and a wall between what is shared and what is personal.
- A GuardianMemory team bank is one way to build it: one URL for every assistant, and owners, members and readers.
Why teams are building one now
Most people now work alongside an assistant or three, and every one of them starts each conversation knowing nothing about the company. So people paste the same background into chat after chat: the stack, the customer, how you do things here. Or they don't, and the assistant fills the gaps with confident guesses.
Meanwhile what the team knows is scattered across heads, chat threads, old documents and a dozen private assistant memories that nobody else can read. When somebody leaves, the part that only lived in their head and their assistant leaves with them.
A company brain puts the lasting part in one place that every person, and every person's assistant, reads from before it answers.
What goes in a company brain
One fact per entry, written as a sentence that makes sense on its own. Keep the things a new colleague would need to be told, and leave out the rest.
| Keep | For example |
|---|---|
| Decisions, with the reason | “Billing moved to Postgres in 2025 because the team needed row-level security.” |
| How systems work | “The billing service runs on Postgres and Stripe.” |
| Who owns what | “Priya is the account lead for Acme.” |
| Conventions | “Customer-facing copy uses British English.” |
| Dates and commitments | “Project Atlas launches on 3 November 2026.” |
Leave out anything personal about anyone, opinions about colleagues, anything confidential to one person, passwords and keys, and whatever only matters today. A company brain is not a document store either: keep the fact a document establishes, and link to the document for the detail.
Company brain, wiki or enterprise search?
They are not rivals. A wiki explains, search finds the document, and a company brain is what every assistant already knows before you ask.
| Wiki or handbook | Enterprise search | Company brain | |
|---|---|---|---|
| What it holds | Pages written for people | An index of the documents you already have | Short facts, one per entry |
| Who keeps it up | People, when they find the time | Nobody: it follows the documents | People and their assistants, as they work |
| When something changes | Somebody edits the page | Somebody updates the document | The new fact retires the old one |
| Best at | Explaining at length | Finding where something is written | Giving every assistant the context it needs |
What makes a company brain work
Assistants that read it first and write to it as they go
If keeping the brain current is a chore, it is out of date within a month. The assistants people already use should read it at the start of every conversation and save what they learn along the way. With GuardianMemory that is two tools, search_memory and create_memory, which any assistant that speaks MCP can use.
Facts that retire when they stop being true
“The launch is on 20 October” becomes “The launch is on 3 November”. A brain that holds both is worse than none, because an assistant will pick one. GuardianMemory merges near-duplicates, and when a new fact replaces an old one it marks the old one outdated: people still see it as history, and no assistant is shown it again. How that works.
A wall between shared and personal
The obvious risk is an assistant saving to the wrong place. The subtler one is an assistant that can read your private memories and write to the team's, and passes one into the other by rephrasing it. No instruction reliably prevents that, so GuardianMemory prevents it by design: an assistant that writes to a team bank cannot read anybody's personal bank at all.
People who can see and fix everything
Every memory is a sentence somebody can read, edit, pin or delete, and each one records who wrote it and through which assistant. The bank's activity shows who saved and searched what.
How to build a company brain with GuardianMemory
- Create a team bank. Open Banks in the app and create one. Your personal bank stays separate.
- Invite the team by email. People with an account get access straight away. Anybody else joins when they sign up with that address.
- Choose what each assistant writes to. Each person's own assistant can keep saving to their personal bank and still search the team's. Point a shared connection at the team bank for anything the team should know: a project assistant, a CI bot, a second connector added for team work.
- Tell those assistants what the bank is for. Paste the team instruction from Prompts and tips: save decisions and why they were made, how systems work, who owns what and the conventions you follow, and nothing personal.
- Seed it. Paste the facts the team already relies on into the Import page, one per line, and pin the handful that should shape every answer.
Who can read and who can write
| Role | Can |
|---|---|
| Owner | Everything a member can, plus invite people, change roles, remove people, and rename or delete the bank |
| Member | Read the bank, search it and save to it |
| Reader | Read and search it, and nothing more. No assistant a reader connects can save to it |
Readers are for the contractor, the auditor and the new starter: people who should know what the team knows without adding to it yet. More on roles and connections in Team banks.
Questions people ask
Is a company brain the same as a knowledge base?
Not quite. A knowledge base is documents written for people to read. A company brain is the short, current facts a team relies on, kept so that people and AI assistants can use them directly. It often points to the knowledge base for the detail.
Which AI assistants can use a GuardianMemory company brain?
Any assistant that connects to MCP servers, including Claude, Claude Code, ChatGPT, Cursor, Windsurf and VS Code. Scripts and custom agents can use the REST API instead.
Can a company brain leak personal information?
Not from anyone's personal memory. An assistant connected to a GuardianMemory team bank cannot read any personal bank, so it has no private memory to repeat. What people type into that assistant is still up to them, which is why the team instruction tells it not to save anything personal.
What happens to the company brain when someone leaves?
Their access ends the moment they are removed, and what they wrote stays. Memories belong to the bank, not to the person who saved them.
How much does a GuardianMemory team bank cost?
Nothing while we learn what people need. Each bank holds up to 5,000 memories, and each person can make 2,000 saves and searches a day.
Give your team one memory
Create a team bank, invite the team, and connect any assistant with one URL.
Free while we learn. No card.
We are letting people in a few at a time.