Why the order matters
Most knowledge base projects start by buying a tool and end with a search box over a mess. The mess is the problem, and no tool fixes it. The order below puts the discipline first, the connections second, and the intelligence last, because each step is useless without the one before it.
Step one: the folders
One node shape, repeated everywhere
Every part of the business gets the same skeleton: a front door file that says what it is and who is on it, a constitution file that says the rules, an inbox for unsorted drops, a knowledge folder for what is known, an operations folder for contracts, billing and meetings, and a children folder for the parts underneath, which have the same shape again.
The point is that anyone, or any agent, can open any folder cold and know where things are.
The four laws
Everything unsorted goes to an inbox, and nothing stays there. Every document lives with the thing it is about. Every folder works on its own when opened alone. A session writes only inside the folder it has open, and drops anything aimed elsewhere into that folder's inbox.
Four rules. Written at the root, mirrored in every folder, read by every agent before it does anything.
Step two: the constitution
The file every agent reads first
A single file at the root, in plain language, that says what this company is, the four laws, the folder shape, and where things go. We keep two byte-identical copies, one named for the agent tools that read it by name and one named for everyone else, and a script that checks they never drift.
This is the file we give away. It is the first file of every brain we build.
Step three: the capture habit
Five seconds, no leaving the task
A thought mid-task, a file someone sent, a contact from a call: it goes into the nearest inbox as a dated note. Nobody files it in the moment. A router, human or agent, files it later, proposes where it goes, asks when it is unsure, and logs every move.
Without this step the folders decay in a month. With it they get better every week.
Step four: the connections
Read-only, where it already lives
Email, files, the CRM, the chat history, the calendar. Connected read-only, indexed with where each thing came from, and never copied out of where it lives. The index knows that the promise to a client is in an email from March and the price is in the proposal, version two.
Step five: the brain
An answer with its source, or an honest no
Only now does an agent go on top. It answers in plain words and then shows the email, the file, the record or the SOP it came from. If it cannot cite, it says it does not know. And when two of your own documents disagree, it says so, with both, which is the part nobody else builds.
Where to start today
Take the folder you use most and give it the shape in step one. Write the constitution in an afternoon; ours is the starter on the marketplace and you can begin from it. Put the inbox habit in place for a week before connecting anything. The brain is one of the three prices, and it is a short project when the first three steps are done.