Relations & tags

Typed relations

A Type can declare a typed relation to another Type — Task.context → Person, Book.author → Person — which shows up in queries, backlinks, and the graph view as a real edge, not a string reference that happens to match a title.

The mentions relation

Writing [[Book Title]] anywhere in a body creates (or resolves) an Object and adds a system mentions relation automatically — you don’t declare this relation yourself. It’s what powers:

• Wikilink pills — [[Title]] renders as a type-colored inline chip; unresolved titles show a dashed underline until the target exists.
• Backlinks — every Object shows what mentions it, grouped by relation.
• Unlinked mentions — a title scan surfaces plain-text occurrences that aren’t yet linked, one click away from becoming a real mentions relation.

Tags are Objects, not strings

Writing #reading doesn’t set a string field — it creates or reuses a real Tag Object and adds it to the Object. That means a tag has its own page, can carry its own properties, and shows up in the graph as a node other Objects connect to — not a label with no substance behind it.

Block-level references

Beyond whole-Object links, Lar supports two finer-grained reference forms:

• Transclusion — ![[Title]] or ![[Title#section]] embeds another Object’s content inline.
• Block references — use the block-reference action to link to one specific block inside a body, with ⌘-click navigation back to it.

Next: The editor — how all of this surfaces while you’re writing.