---
type: "Article"
title: "How to build your own second brain: a step by step guide to an LLM-maintained wiki"
description: "From an empty folder to a governed knowledge base an agent maintains: the structure, the constitution file, the rules that keep it honest, the tools worth adding, and the order to do it in."
resource: "https://www.laurelinlabs.com/blog/build-your-own-second-brain"
tags: ["how-to-build-a-second-brain", "aeo-guardrails-and-agentic-search"]
generated: { by: "laurelin-site-build/2026-09-02", at: "2026-09-02T12:00:00+00:00" }
status: "stable"
stale_after: "2027-03-02T00:00:00+00:00"
---
# How to build your own second brain: a step by step guide to an LLM-maintained wiki

Published 2026-08-27. Author: [Piers Butler](/entities/piers-butler.md).

Building a second brain takes an afternoon for the structure and a few months for the value. Create a folder with three tiers: raw sources you never edit, a wiki the agent writes, and one constitution file that tells the agent how both work. Add an index the agent reads first and an append-only log it writes to. Then set the rules that keep it honest: capture verbatim, promote by rewrite, log every promotion, cite raw sources rather than derived pages, and let contradictions surface as proposals. Put it in version control. Feed it one real source a day.

## FAQ

### How long does this take to set up?

The structure takes an afternoon: seven folders, a constitution file, an index and a log. Feeding it is the real work, and the useful measure is sources rather than hours. Somewhere around thirty to fifty ingested sources the wiki starts answering questions you would otherwise have gone looking for, which is the point at which people stop having to be reminded to use it.

### Do I need to be able to code?

No. Every file is plain text and every operation is a sentence you say to an agent. The one genuinely technical step is putting the folder in version control, and that is three commands you can copy. If you want the governance without assembling it yourself, that is what the plugin packages.

### What should go in the constitution file?

Only what you want applied on every single task: who you are and what the business does, the folder structure and what each tier means, the promotion rules, your standing style and brand rules, and the handful of decisions that are settled. Keep it short. It is loaded as context every session, so anything speculative or expired in there quietly degrades every answer you get.

### How is this different from just using an assistant with memory?

Memory features write inferences about you into a store you cannot easily read, edit or audit, and they belong to whichever vendor you are using. A second brain is your own folder of plain text, versioned, portable between models, and it only holds what you accepted. The trade is a little friction at capture for the ability to answer why something is in there two years later.

### What is the most common way this fails?

Two ways. Building an elaborate structure and never feeding it, which is a filing cabinet with nothing in it. Or letting the agent write straight into canon because it is faster, which works until the day you need to know why a rule exists and there is no answer. The gate feels like overhead in week one and is the entire value in month six.

Hub: [Guardrails, Agentic & Future-proofing](/topics/guardrails-future.md)