Links and scenarios

Where links come from

Every link shows its origin:

• you linked it manually;
• the auto-linker linked it — automatic matching;
• the agent linked it;
• a direct link — structural, from the data itself: a task belongs to a project, an email came from a contact.

And its role: references · wiki link · backlink · embedded · semantically close · related · depends on · blocks · creates · discusses · attends · belongs to a project · participant · meeting recording · mentions · sent from · recipient · author of · works at · extracted from · attachment · derived document.

The distinction matters when something looks wrong: a link you made and a link the auto-linker guessed carry different weight. Check a doubtful one against the source via “Extracted from”.

Everyday scenarios

Find out where a fact came from. Search for a node in the Understanding area → double click → “Extracted from” → “Open”: you land in the original email, note or meeting.

Gather the context around a project. Find the project node → single click: its links light up and the neighbourhood pulls in → you see the tasks, meetings, people and documents around it.

Find what was forgotten. The Clusters view → lone nodes on the periphery: few links usually means the object dropped out of work.

Check a doubtful link. Open the node → look at the origin. A link from the auto-linker with low confidence is worth verifying in the source.

See what the agent knows at all. Double click on the background to fit the map → the legend shows which areas are populated. An empty area is not a bug — it means no data, or indexing switched off in Settings → Data and privacy.

Inspect a dense spot. Pause the rotation → select a node in the middle of a cluster → the neighbourhood gathers around it → double click flies the camera closer.