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") with a Projects relation. On any area's page you pick — or create — the projects that belong to it, and every project's page automatically shows its area in return.

Put the relation on the Collection whose page you want to edit from. Want to manage projects while viewing an area? The relation lives on Areas. The other side always updates by itself.

Adding a Relation property

Open + Add a property — in the Collection's settings or right on any entry's page — and choose Relation (at the bottom of the picker). 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.

Don't see the entry you want? Type its name and hit Create "…" — the new entry is created in the target Collection and linked in one step, just like creating a tag option from the tag picker.

When there are a lot of them

A relation with many links doesn't take over the page. The field shows the first couple of lines of chips and puts the rest behind … N more — click it to open the full list, which grows to five lines and then scrolls on its own. Show less folds it back. The + button stays reachable the whole time, so you can keep linking without expanding first.

This holds at any size: hundreds or thousands of links stay fast, because only a slice is drawn at a time (with a Load more button for the next batch). In table cells, where there's no room to expand, you see the first few chips and a +N count — open the entry to see them all.

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.