Policies people will defend
Refunds, privacy, acceptable use, vendor rules. If you would not say it on a recorded call, it does not belong in the company brain.
Company brain
The company brain your agents actually read.
A company brain is not another wiki. It is the approved memory of how you work — the pages a person will stand behind, and the only pages ChatGPT, Claude, Cursor, and your own agents are allowed to use.
What it is
A company brain is the memory you are willing to put an agent in front of.
Every company already has knowledge. It lives in Notion, in a shared drive, in Slack threads, in the head of the person who has been here the longest. That is not a company brain. That is a pile. Agents cannot tell which paragraph is current, which is a draft, and which was true last quarter.
A company brain is smaller on purpose. It holds the policies, product facts, processes, and brand rules you would repeat on a recorded call. Each page says when an agent should use it. A person publishes the version other agents may read. Everything else stays a draft.
Memrio is that brain for teams whose AIs already answer customers, write code, and draft copy. One workspace. One MCP URL. A key per agent so support does not see the legal tree, and the coding agent does not quote an unpublished price.
What belongs
Put in the company brain what you would bet a ticket on.
If the page is a brainstorm, a meeting note, or a maybe, leave it out. Agents are literal. The company brain should be too.
Product facts
What ships, what it costs, what it does not do. Facts the agent should quote, not paraphrase into a launch that never happened.
Processes with a first step
Onboarding, escalation, offboarding, how a credit is issued. Nested subpages hold the branches. The parent page tells the agent when to open them.
Instructions on the page
Every page says when to use it. Browse is a catalog of those lines. That is how a company brain stays small enough to trust.
Not a dump
A wiki is a library. A company brain is a desk.
People can wander a wiki. An agent should not. Pointing a model at your entire Drive teaches it to sound confident about pages nobody has reviewed this year.
Wiki or Drive
- Written for people who already know the folder
- Agents get a dump, a crawl, or a similarity search
- Edits go live the moment someone types
- No record of which file an AI used
Company brain in Memrio
- Written so an agent can pick the right page
- Browse the catalog, then open the whole page
- Draft, review, publish — other agents see the approved version
- Every MCP call logs the pages it hit
How Memrio is the brain
People govern it. Agents plug in over MCP.
You write pages the way you write for a careful colleague: short, owned, with a note about when they apply. You submit a version. An owner or admin publishes it — or you publish yourself if the workspace allows it. Until then, production agents do not see the change.
Each agent gets a page set and its own API key. The key is the scope. There is no workspace header to forget. Support reads policy. Engineering reads runbooks. A test agent can read drafts. A Writer can edit any page, publish, and create narrower agents later. You can pause any of them.
Agents do not receive embeddings. They call browse, pick pages by title and use-when text, then get_page for the packed contents — instructions, body, attached file text. If they may write, they read the source first, send the whole page back, or nest a subpage under a parent. Every call lands in the request log with the pages it hit.
That loop is the company brain: a person decides what is true, an agent uses only that, and when the agent learns something new it writes a version instead of hiding the fact in a chat.
Who uses a company brain
Same memory. Different desks.
Support
One answer at the desk
The support bot and the human on chat both read the same refund, shipping, and account pages. When an exception is approved, it is written back once. The next ticket does not invent a new policy.
Sales
Packaging that does not drift
Quote only published SKUs, limits, and competitive language. A new plan lives as a draft until someone publishes it. Cursor and ChatGPT stop promising a feature that is still in review.
Engineering
Runbooks the coding agent can open
Incident steps, ownership, and “do not touch” rules sit on pages with use-when instructions. The agent browses, opens the runbook, and follows [CRITICAL] lines instead of guessing from an old README.
Legal & ops
The version that is allowed to exist
Contracts language, DPA notes, and retention rules are numbered versions. An agent can draft. It cannot silently replace the published page. Review frequency flags anything that has gone stale.
Stand one up
A company brain in an afternoon, not a migration.
You do not import the company. You publish the pages that already cause damage when they are wrong, then connect the agents that answer those questions today.
01
Open a workspace
Name the company brain. The workspace slug becomes the MCP URL every agent will use.
02
Publish the first pages
Write the policies and facts agents already get wrong. Add use-when instructions. Nest subpages when a topic should split.
03
Connect an agent
Issue a key. Point Cursor, Claude, or ChatGPT at the MCP server. The key is the page set — there is no extra header.
04
Let it write back, with review
Turn on edit for a trusted agent, or hand a page to the workspace Writer. Versions wait for a person unless you allow publish.
Questions
Company brain, plainly.
- What is a company brain?
- A company brain is the approved memory of how your company works — policies, product facts, processes, and the instructions that tell an AI when to use them. Memrio is that brain: people write and review pages, and every agent reads the same published version over MCP.
- How is a company brain different from a wiki or a knowledge base?
- A wiki is written for people who already know where to look. A company brain is written for agents. Each page carries “use when” instructions, lives in a page set, and only becomes visible after someone publishes it. Agents browse the catalog and open whole pages — they do not scrape Drive or rank chunks.
- Why do AI agents need a company brain?
- Without one, every tool has a different prompt, a different doc dump, and a different idea of your refund policy. A company brain is the shared source. ChatGPT, Claude, Cursor, and the agents you build all read the same approved pages, and the request log shows which page they used.
- Can Memrio write back into the company brain?
- Yes. A writing agent can create pages, nest subpages, update source, or append. Those edits become versions. Unless you trust the agent to publish, a human reviews them before other agents can read the change.
- What should go in a company brain first?
- Start with the pages agents already get wrong: refund and billing policy, product packaging, brand voice, onboarding steps, and the escalation path. Publish a handful. Connect one agent. Grow the tree with subpages as topics split.
- Who owns the company brain?
- People do. Owners and admins approve versions, set which agent may edit or publish, and pause a key at any time. The brain is not a scrape of Slack. It is what your team is willing to stand behind.
Start today
Give the company a brain the AIs can share.
Open a workspace, publish a page, connect an agent. From then on, every tool in the stack reads the same approved memory.