Folder Brain

Organise your business before you touch AI

AI is only as good as what it can read. The work that fixes that is old and boring. Write down what the business is, who can do what, where things live, and how the work gets done. Businesses did this long before AI. Here is how to do it in four plain files you own.

Four plain filesOne folder you ownWorks with any AI

Sources opened and quoted on 24 September 2026

The problem is not the AI

Look at where your business information lives. Some of it is in your head. Some is in email. Some is in a chat from last week. And the three copies of your price list do not agree.

That was a problem before AI. A new hire hits it on day one. AI hits it on every single task, because it only knows what it can read.

So put AI to the side for a minute. Organise the information first. Everything else works better after that, including the people.

The four B's, and the names they already had

The four B's are four questions. None of them is new. Each one is something businesses ran on long before AI, and each has a proper name. The B makes it easier to remember.

Agents go underneath, not beside. An agent is only as good as the context it stands on.

Brief

01-brief.md

What is this business, and who is it for?

What you sell, who you sell it to, what you are trying to hit this quarter, and how you sound. Add the words you use that an outsider would not understand.

The proper name: A knowledge base. The facts anyone needs before they can do any work here.
Where it lived before AI: A company wiki, a shared drive, or somebody's head.

Boundaries

02-boundaries.md

Who is allowed to do what?

What people and AI may do on their own, what they must never do, and what has to come back to you first. Write drafting and sending as two different things. Same with preparing and spending.

The proper name: Permissions, or access control. The security rule behind it is called least privilege. Give each person, and each tool, only what the job needs.
Where it lived before AI: The user roles inside each tool you pay for.

Breadcrumbs

03-breadcrumbs.md

Where does the current version live?

Where the live version of each thing sits. Your client list, your prices, your calendar, your files. Point at it. Do not paste a copy in, because then you have two and one of them is wrong.

The proper name: The system of record. The one place that holds the official version of each thing.
Where it lived before AI: Your CRM, your calendar, your accounting tool, your drive.

Blueprints

04-blueprints.md

How does a job get done here?

The steps for one job you repeat. Write the order, and write how you know it is finished. Be blunt about it: a good cold email for my software does name the problem in the first line and never opens with a compliment. That sentence is worth more than a page of description, because anyone, AI included, can check the work against it.

The proper name: Standard operating procedures (SOPs), or runbooks. The steps for a job. The test for finished is called acceptance criteria.
Where it lived before AI: An SOP folder, a training doc, or whoever has done the job longest.

“Every program and every user of the system should operate using the least set of privileges necessary to complete the job.”

Saltzer and Schroeder, The Protection of Information in Computer Systems, 1975.

Where AI comes in

The reader is new. The work is not. Here is what AI adds to each piece, and nothing more.

Knowledge baseBrief

Once your tool is pointed at the folder, the AI reads it before it starts. It cannot ask around the office. If it is not written down, it does not exist for the AI.

PermissionsBoundaries

The AI becomes one more user. Write what it may draft, what it may send, and what it may never touch.

System of recordBreadcrumbs

Connectors. The AI can read your CRM or your inbox through a connector, so you point at the record instead of pasting a copy in.

SOPsBlueprints

Skills. A skill is a Blueprint written for the AI, and it loads only when that job comes up.

“organized like an onboarding guide you’d create for a new team member”, and “until a Skill is triggered, only its name and description occupy context.”

Anthropic, Agent Skills overview, on what a skill is.

“MCP provides a unified way to connect AI models to different data sources and tools.”

Anthropic, glossary, on MCP, an open protocol for connecting AI to your tools.

Knowledge goes in the folder. Records stay where they are.

In the folder

What is true for every job. Your offer, your voice, your rules, where things live, and how the work gets done. It changes slowly.

In the tools you already use

One row per person, deal, or payment. Clients in your CRM, bookings in your calendar, payments in your payment tool, messages in your inbox. It changes every day.

Never copy records into the folder. Two copies means one of them is wrong. Your Breadcrumbs file points at where each record lives, and a connector lets the AI read it there.

Those tools already have their own permissions, so you do not need to build a database for any of this. If you handle health data, patient records stay in your clinical system and never go in this folder.

How to set it up

1
Make one folder
Name it after your business. On your own computer is fine. Everything below goes inside it.
2
Take stock of where things live
List every place your business information sits today. For each thing, pick the one home, and archive the other copies. This is the step that organises your data. Do not skip it.
3
Get interviewed
Paste the prompt below into any AI chat. It asks one question at a time and hands you the four files at the end.
4
Save the four files into the folder
The first version will be wrong in places. That is fine.
5
Add the one file your tool looks for
Each AI tool looks for one small file at the top of the folder. It only needs to say: read the four files first.
6
Keep it current
The second time you correct the AI about the same thing, fix the file instead. The same goes for a person.

Taking stock looks like this

The thing	Where it lives now	The one home
Price list	A Google Doc, two old PDFs, a chat from March	The Google Doc
Client list	A spreadsheet and your inbox	Your CRM
How you onboard a client	Your head	04-blueprints.md

Let the AI interview you

Staring at four empty files is how this stalls, so get interviewed instead. Paste this into any AI chat. Answer out loud if that is easier, then paste your answers in. It does the taking stock with you, then hands you the four files.

The interview prompt

I want to write down how my business works, so any AI, and any new person, can work with it.

Interview me. Ask me one question at a time and wait for my answer.

Cover these four things, in this order:
1. Brief. What the business is, who it serves, what matters right now, and how I sound.
2. Boundaries. What people and AI may do on their own, what they must never do, and what comes back to me first.
3. Breadcrumbs. Every place my business information lives today. For each thing, ask where the copies are and which one is the current version.
4. Blueprints. The steps for the jobs I repeat, and how I know each one is done.

Rules:
- One question at a time. Short questions.
- If my answer is vague, ask me for a concrete example before moving on.
- If I name two places for the same thing, ask me which one is the current version.
- Do not write anything until you have asked about all four.
- At the end, give me four separate markdown files: 01-brief.md, 02-boundaries.md,
  03-breadcrumbs.md, 04-blueprints.md.
- In 03-breadcrumbs.md, make a table: the thing, its one home, and the old copies I should archive.
- Do not copy client records, passwords, or payment details into any file. Point at where they live.
- Use my words. Do not tidy my voice into something more corporate.

What the folder looks like after

my-business/
  CLAUDE.md          the one file your tool looks for
  01-brief.md
  02-boundaries.md
  03-breadcrumbs.md
  04-blueprints.md

The one file each tool looks for

Claude Code and CoworkCLAUDE.md
Codex, and most coding toolsAGENTS.md
Gemini CLIGEMINI.md
A chat window with no file accessPaste the files in, or attach them

The folder travels. That one file does not. When you move tools, you rewrite it. Not your business. Only the doorbell.

If a team uses it

Sharing works on the folder, not on a line inside a file. So split by who needs to see it. One shared folder for what everyone may see, and a separate folder, shared separately, for anything only some people may see.

Why plain files, and not an app

Four markdown files in a folder are not a feature of anything you pay for. Nobody can move them to a higher tier. Nobody can retire them. If you stop paying for a tool tomorrow, the folder is still on your computer.

You should not have to trust any one company with your business. Plain files mean you can leave. Your context is the expensive part. The model is the part you should be able to swap.

And there is a mechanical reason too

Every AI chat has a limit on how much it can hold at once. When a long conversation reaches that limit, it summarises itself and carries on from the summary. Anthropic calls this compaction and describes it like this:

“Compaction is the practice of taking a conversation nearing the context window limit, summarizing its contents, and reinitiating a new context window with the summary.”

Their own warning about it is the part that matters to you: “overly aggressive compaction can result in the loss of subtle but critical context”.

So everything you explained in the chat is at risk the moment the window fills. Everything in a file is not.

Anthropic, Effective context engineering for AI agents, page dated 29 September 2025. They have a name for the fix too, and it is the same idea as this page: “Structured note-taking, or agentic memory, is a technique where the agent regularly writes notes persisted to memory outside of the context window.”

Want to point your folder at a different model, or a cheaper one? Read the guide to other AI models.

What this page does not say

Plain files are not private. Any AI you point at the folder can read all of it. Keep what it should not read somewhere else.
Four files is a starting shape, not a rule. The four B's are four questions. Answering them matters more than where you put the answers.
This does not make AI accurate. It gives it the right facts to start from. Check what comes back.
I have moved one folder between two tools and had to rewrite the tool file by hand. That is one test, on one folder, so treat it as the shape of the problem rather than a measurement.

Why I care about this

There is so much hype about AI on the internet, and I feel like people are not understanding what it is. It is a tool for leverage. It does give you leverage. But like any technology, you have to understand its strengths and its weaknesses.

I care about you getting something useful out of it. I have a master’s in health informatics, the science of how information gets stored, moved, and understood by whoever picks it up next. I care about data, and I care about the truth.

That is why this page starts with your data, and not with AI.

My first-author paper on why health data was hard to share is free to read on Europe PMC.

Last checked 2 October 2026.