[[Links]]: how knowledge pages connect

The knowledge base would be just a folder of notes if the notes did not know about each other. The link is what turns it into a map.

What a link is

Inside any knowledge page, a name in double brackets — Acme Corp, Q3 launch, Dana — is a link to that thing's own page. Rango writes these links itself as it takes notes: when the launch meeting mentions Dana and Acme, the launch page links to both, and both link back. Follow the links and you can walk from a person to their projects to the decisions those projects produced, the same way you would walk the real relationships.

Why the agent needs them

The links are not decoration; they are how retrieval works well. When you ask about the Q3 launch, the launch page's links tell the agent which neighbouring pages are relevant — who is involved, what was decided, which customer it is for — so the answer can pull in exactly the surrounding context and nothing else. A flat pile of notes forces a search engine to guess relevance; a linked graph states it.

Writing them yourself

Pages are editable, and your own links are as real as the agent's. Writing name to a page that does not exist yet is fine — it marks something worth having a page for, and connects the moment the page appears. If you already keep a wiki in this style, the habit transfers directly.

Seeing the shape

The Knowledge section renders the graph — pages as nodes, links as edges — which is occasionally useful and always satisfying. Clusters show you what your meetings are actually about; an isolated page with no links is usually either brand new or wrongly named.

One practical rule

Name pages the way people say the names in meetings. The link between what is spoken in a call and what is written in the base is exact-by-name, so a page called Website refresh will not catch a team that always says "the redesign." Rename the page to the spoken name and the memory snaps into focus.