Browsing and editing pages

Once there are pages, Brain becomes something you read as well as ask.

Four views

View	What it is for
Browse	The page tree — the structure, top down
List	A dense table, sortable, for finding one thing
Grid	Cards with snippets, for skimming what exists
Graph	The constellation — pages as nodes, links as edges

The graph is not decoration. Clusters show where your knowledge is dense, and isolated nodes show pages nothing links to — usually a sign of something written once and never connected.

The overview also tracks how the brain is growing, how knowledge breaks down by type, and which pages are linked to most.

What a page holds

Title and type. What it is, and which category it belongs to — person, company, concept, note, source, or one of your own.

Subtitle. A one-line descriptor: a person’s role, a company’s stage. Captured automatically if your workspace has it switched on.

Content. Markdown. Write it however you would write a wiki page.

Properties. Free-form fields — a person’s team, a client’s renewal date, a process’s owner. Structured enough to be useful, open enough not to need a schema.

Open questions. Things a source raised but did not answer. They surface as gaps, and you can snooze one that is not worth chasing yet.

Connections. Both directions: this page mentions and pages linking here. Backlinks are how you discover that four processes depend on a policy nobody told you about.

History. Every edit is snapshotted, with who made it. Nothing is quietly overwritten.

Links and stubs

Write [[page name]] anywhere in a page to link it. If the target does not exist yet, a stub is created — an empty page in the right place in the graph.

Stubs are deliberate. They keep the graph whole, and they double as a visible to-do list: a stub with five things linking to it is the page you should write next. Writing a real page over a stub claims it, keeping every link that already pointed there.

Editing

Pages edit in place and save as you type. You can also ask the AI to help — rewrite a section, tidy a page taught from messy source material — the same way you would in any document.

Deleting a page removes it from the graph. Links that pointed at it become stubs again rather than breaking.

Keeping it healthy

Link liberally. The leave policy to the holiday calendar, the escalation process to the on-call rota. Links are how a question spanning two pages gets one coherent answer.

Split pages that grew. If a page answers four questions, it will be retrieved for all four and be the best answer to none.

Fix the page, not the answer. When the assistant gets something wrong about your organisation, the durable fix is upstream — edit the page and every future answer changes.

Watch the stubs. They are the cheapest possible list of what your organisation has never written down.