What a company brain is

The problem

Say you use three agents. One fixes a bug in your app. One changes a server setting. One helps you pick a price. Each one learns something new. None of them tells the others.

Next week a fresh session starts. It knows none of it. So it guesses. Or it reads an old note that is now wrong.

The idea

A company brain is one private GitHub repo. Inside it are short pages. Each page covers one topic. Your product. Your repos. Your servers. Your costs. Your decisions.

Agents read the pages before they work. That part is easy.

The hard part is keeping the pages true. Here is the one rule that does it: agents do not edit the pages. When an agent changes a fact, it leaves a short note in an inbox folder. One agent, the librarian, reads the notes. It checks the proof. Then it edits the pages. You say yes before the change counts.

How it flows

1. An agent does its work.
2. It leaves a note (an "update") in the inbox, as a pull request.
3. Once a day, the librarian reads every new note.
4. It checks each note against the real source.
5. It edits the right page, or it writes you a question.
6. You read one short report, answer the questions, and approve.

Why only one writer

Picture ten people writing in one notebook at the same time. They cross out each other's lines. Nobody knows which line is right.

Now picture ten people who each drop a note in a box. One person reads the box and writes the notebook. The notebook stays clean. Every note is kept, so you can always see who said what, and when.

That is the brain. Many readers. Many note writers. One page writer.

Words you will see

• Repo: a folder that Git tracks. GitHub keeps a copy online.
• Branch: your own line of changes. It does not touch the main copy until someone merges it.
• Pull request (PR): a request to add a branch to the main copy. A person reads it first.
• Page: one short Markdown file about one topic.
• Update: a small JSON note an agent leaves when a fact changes. The template also calls it an event.
• Inbox: the folder where updates wait for the librarian.
• Librarian: the one agent that reads updates and edits pages.
• Flag: a question the librarian cannot answer alone. It names who must answer.
• Receipt: the librarian's record of what it did with each update.

Set it up

1. Pick the owner. This is the one person who makes company decisions. The brain only calls something a decision when the owner made it.
2. Pick a name for your private repo, such as acme-brain.
3. List your sources. These are the repos, docs and tools that hold real facts about your company.
4. List your agents. Write down every tool that should read the brain.
5. Write down one fact you can check, such as "Our website runs on Cloudflare Pages." You will use it later to test that an agent can read the brain.

The prompt

Not sure what your sources are? Paste this to your agent. It only reads. It changes nothing.

Help me plan a company brain. Do not change any files.

1. Look at the repos and folders you can open on this machine.
2. List the ones that hold facts about my company: what we sell, how it is built, where it runs, what it costs, and what we decided.
3. For each one, write one line: the name, where it lives, and what kind of facts it holds.
4. List the AI agents and tools you can see that I use.
5. Ask me who owns company decisions.

Keep the list short. Mark anything you are not sure about with "(not sure)".

What you can do now

You know what the brain is, who owns it, what feeds it, and who reads it.

Next module

Module 2 makes your private brain from the free template.