Relations

Connect entries across Collections — a Project points at its Area, a Task at its Goal. The other side updates automatically, and goals can even reference other goals.

A Relation connects an entry to entries in another Collection. Where a Tag picks from a list of labels, a Relation points at real entries — each with its own page, properties, and history.

The classic setup: an Areas Collection ("Health", "Career", "Personal growth") and a Projects Collection with an Area relation. Each project points at the area it belongs to — and each area's page automatically shows every project pointing at it.

Adding a Relation property

In the Collection builder, add a property and choose Relation. You pick three things:

Name — make it meaningful: Area, Goal, Blocked by. The name is how you (and the AI) understand what the connection means.
Target Collection — where the entries you'll point at live (e.g. Areas). A relation can also target its own Collection — that's how you build hierarchies like Parent goal on a Goals Collection.
One or many — whether each entry points at a single target (a project has one area) or a list (a book can have many authors).

Using it

On an entry's page the relation shows as chips. Click the field to search the target Collection and pick entries; click a chip to jump to that entry's page. Everything updates instantly.

The other side is automatic

You never set up the reverse direction. If Projects have an Area relation, every Area entry's page gets a Related section listing the projects (and goals, tasks, …) that point at it — grouped by where they come from. One connection, visible from both ends, impossible to get out of sync.

Relations and the AI

Relations are built for asking, not just clicking. The assistant can create relation properties, connect entries by name ("put the Marathon project under my Health area"), and read the graph in both directions ("what's in my Health area?"). If a name is ambiguous it asks rather than guessing.

Relation, Sub-entry, or link?

Relation — points at an independent entry that lives its own life. Deleting a project never touches its area.
Sub-entries — the children are part of the entry (a dish's ingredients) and are deleted with it.
@-link in the text — a lightweight mention inside a page's body; no structure, no one-or-many, just a reference and a backlink.

Rule of thumb: if the thing you're connecting to deserves its own page and would outlive this entry, it's a Relation.