A knowledge base becomes a graph once something else can query it
PARA and Zettelkasten pushed back on hierarchy for a human reader. The graph shape only starts to matter once an agent can traverse it multiple hops and audit what it finds.
PARA and Zettelkasten pushed back on hierarchy, arguing notes should link the way ideas actually relate — in webs, not trees. The insight is obvious in retrospect; the problem is most tools claiming to support networked notes still treat linking as a cosmetic afterthought. My system splits across three backends by function: a core knowledge graph on Postgres holding structured knowledge across projects, meetings, people, and career history; a separate store for small atomic facts that need fast lookup; a third holding behavioral instructions for how my agents should act, not facts about the world. The core is a real graph, not markdown files that happen to link — pages connect via wiki-links into explicit nodes and edges, and the graph shape itself carries meaning. I enforce hygiene mechanically: no duplicate pages, orphan tracking for pages with no incoming links, bi-temporal facts so a changed role gets a time boundary instead of overwriting history. I publish a curated subset as a digital garden, deliberately exposing structure rather than polished standalone essays. The consequence that matters most is what happens when an agent reads and writes to it. Vector search tells you what sounds similar; it can't traverse three hops from a person to a project to a decision. A flat index gets fuzzy under pressure. The graph holds the error.