# What is a personal knowledge graph?

> A personal knowledge graph connects the people, projects, ideas and sources in your notes with typed links. Learn how it differs from backlinks and a second brain, and how AI agents can maintain one in plain Markdown.

Updated 2026-11-08. Canonical: https://cozy.cloud/personal-knowledge-graph

> A personal knowledge graph is a set of notes about the people, projects, ideas and sources in your life, connected by named relationships such as "depends on", "reports to" or "decided in". Plain backlinks only say two notes are related. A knowledge graph says how, which lets you and your AI agents traverse, query and check it.

## Backlinks vs typed links

A backlink is an untyped edge: page A links to page B. Note apps such as Obsidian, Roam, Logseq and Notion show these, and their graph views draw them as lines. A typed link names the relationship. Typed links turn a pile of connected notes into a graph you can ask questions of, such as "what depends on the API project?" or "which decisions came from the kickoff?".

| | Backlinks | Typed links |
| --- | --- | --- |
| Example | Billing links to API | Billing depends_on API |
| Answers | What is related? | How is it related? |
| Query | List incoming links | Traverse by relation, type or tag |
| Common in | Most note apps | Tana supertags, Obsidian plugins, Cozy |

## Personal knowledge graph vs second brain vs personal wiki

- A **second brain** is a practice: capture and organize what you learn so you can reuse it.
- A **personal wiki** is a format: pages with titles, links and an index.
- A **personal knowledge graph** is a structure: entities and named relationships, usually with sources.

You can have all three at once. A wiki whose pages declare a type and link to each other with named relations is a knowledge graph.

## How to write one in plain Markdown

You do not need a graph database. Cozy derives the graph from conventions in ordinary Markdown every time a page is saved:

```markdown
---
type: person
description: Leads the billing rewrite.
aliases: [Ann]
tags: [finance]
---
# Ann Lee

- owns:: [[wiki/projects/billing.md]]
[[Ann Lee]] | reports to | [[Bob]]
Joined in March. [[sources/files/org-chart.md]]
```

- **Frontmatter** gives each page a `type`, `description`, `aliases`, `tags`, `status` or `as_of`. Frontmatter keys whose values are wikilinks become relations.
- **Relation lines** such as `owns:: [[target]]` and triples between two other pages create typed edges.
- **Plain wikilinks** become `links_to` edges, and links into `sources/` become `cites` edges.
- **Name links** like `[[Acme]]` resolve by path, title or alias, ignoring case and accents.
- **CONFLICT: lines** record disagreements between sources so they can be resolved later.

## Why agents are good at maintaining it

People rarely keep typed links up to date by hand. AI agents can: when a new meeting transcript arrives, an agent can update the people and project pages it mentions, add relations, cite the transcript and flag anything that conflicts. In Cozy, agents read the graph with `cozy_graph` and `cozy_context`, and `cozy_health` tells them what to fix next: broken links, duplicates, orphans, stale pages and unsourced claims.

## Get started

Sign in at [cozy.cloud](https://cozy.cloud), connect an agent through the [MCP server](/mcp-server), and ask it to organize your first sources into typed pages. The [hosted LLM wiki guide](/llm-wiki) explains the full workflow.

## Frequently asked questions

### What is an example of a personal knowledge graph?

A set of notes where a person page says they own a project, the project page says it depends on another project, and a decision page says it was decided in a specific meeting, with each claim citing its source. Those named relationships make it a graph.

### Do I need a graph database for a personal knowledge graph?

No. Typed links can live in plain Markdown as frontmatter and relation lines. Cozy parses them on every save and keeps the files portable.

### Does Obsidian support typed links?

Not natively. Obsidian links are untyped, and typed relationships rely on frontmatter properties or community plugins such as Breadcrumbs or Wikilink Types.
