The Company Brain Course

What this is

Every new agent session starts from zero. It does not know your product. It does not know what you decided last week. So it guesses, or you type the same facts again.

A company brain fixes that. It is one private GitHub repo full of short pages about your company. Agents read it before they work. When they change something that matters, they leave a note. One agent, the librarian, checks each note and keeps the pages true.

I run Ducktate this way. This course is that setup, written down in plain steps. Seven short modules. Each one ends with a prompt you can copy and paste to your agent.

Who it is for

You use at least one AI agent for real work. Claude Code, Codex, a chat bot, or a few of them. You are tired of repeating yourself. You want your agents to share one set of facts.

You need a GitHub account, Git, Python 3.11 or newer, and one agent that can read and write files.

The short version

Agents read the brain. Agents never edit the pages. They leave notes. The librarian checks the notes and edits the pages. You approve.

The free template

Everything here uses The Librarian, a free public template on GitHub. It has the folders, the rules, the commands and fake example data. You make your own private copy. Your real facts only go in your copy.

Free, and it stays free

No email. No signup. Copy anything on any page.

The modules

1. 6 min

   What a company brain is

   The idea in plain words: one private repo of short pages, agents that read it, notes instead of edits, and one librarian who keeps every page true.

2. 8 min

   Make your brain

   Copy the free Librarian template into a private GitHub repo, set your company name and owner, run the checks, and let an agent fill the first pages.

3. 7 min

   One rules file for every agent

   Write the brain rules once, in one versioned file. Point every repo and every agent at that one link, so Claude, Codex and your bots never drift apart.

4. 9 min

   How agents read and report

   Before work, an agent reads a few pages. After work, it leaves one update from its own branch and opens a pull request it never merges. Here is how.

5. 9 min

   The librarian

   One agent, once a day: it brings in the updates, checks each one against the real source, edits the pages or asks a question, and opens one PR for you.

6. 8 min

   The agent team and the brain

   One orchestrator reads the brain and hands each worker only the facts it needs. Workers never write to the brain. The orchestrator writes one update.

7. 6 min

   Run it every day

   The owner's ten minute daily habit: read the report, answer the flags, merge the librarian's pull request. Plus the five rules that keep a brain true.

Where to go next

• The Librarian template on GitHub, the free template this course builds on, with every command and rule.
• The Librarian prompt page, the full setup, handoff and schedule prompts in one place.
• The agent team prompt, set up an orchestrator and its workers in one paste.
• The Orchestrator Course, the agent team in depth: one brain, many cheap hands.