Guides and resources for AI engineers: an agents course, five handbooks, a hands-on second-brain project and a vetted reading list.
The four page types
Four types, each with a job. Every page declares its type in frontmatter, which is what lets you query the vault by shape rather than reading everything.
Sources
One page per ingested item. What this article, video, paper or conversation said.
Records claims as claims: this source says X, with the URL, author and date attached. It does not evaluate. It does not merge in what other sources think.
Source pages are the audit trail. When a concept page says something surprising, the source pages behind it are how you check whether it was ever true.
Entities
People, organisations, products, tools. What it is, why it appears in your vault, and everything that mentions it.
Entity pages are cheap to create and pay off in a way that is not obvious until the vault is large. They become the natural join points: three unrelated sources that all mention the same company suddenly connect through it, and that connection is often the thing worth noticing.
Do not write biographies. An entity page holds what is relevant to your vault, not what Wikipedia holds.
Concepts
Ideas, methods, frameworks, arguments. These are the pages that compound.
A concept page explains the idea in plain language, says where it came from, what supports it, what argues against it, and what is still unclear. Written well, it is readable by someone who has seen none of your sources, including you in a year.
This is the only page type where the agent should be synthesising across sources rather than recording.
Synthesis
Comparisons, themes, open questions. A synthesis page exists only when it says something no single source did: two sources disagree, three describe the same pattern, a question keeps recurring across unrelated material.
The rule that keeps these honest: do not write a synthesis page to have one. An agent asked for synthesis will always produce something, and manufactured themes are the fastest way to fill a wiki with confident nonsense.
Where the types blur
Some things are legitimately two types. A methodology named after its author is both an entity and a concept. Pick one, usually the concept, and give the other an alias pointing at it.
Some things are neither. A recipe, a config snippet, a checklist. Those are reference material, not knowledge, and they belong in a project folder rather than the wiki.