Reading the Map
What becomes a node
Every workspace, agent, session, bit page, and file is a node. Pinning a note to project memory — from a session's own settings — becomes a node too, as long as that session's "Knowledge fabric enabled" setting is on, which it is by default.
A richer set of node kinds — Task, Decision, Handoff, and Artifact — exist in the node-type legend and are drawn from the same underlying knowledge fabric, but they depend on a feed that ships off by default with no exposed switch to turn it on. A typical installation will not see any of these four kinds appear. A further kind, Conflict, is reserved in the legend for a future human-arbitration signal; nothing in NEXUS produces one today, so you will never see a Conflict node regardless of settings.
What a connection means
Connections carry a label describing the relationship between the two nodes they join:
| Label | Meaning |
|---|---|
| contains | A workspace contains an agent, bit page, or file. |
| runs | An agent runs its terminal session. |
| links to | One bit page links to another via a [[wiki-style]] link. |
| touches | A session touches a file inside its working directory. |
| reflects on / related to | A captured bit relates to whatever it was captured from, or to a node you've linked manually. |
| messaged | Two agents exchanged mesh messages. |
| delegated to / handed off to / handed off from | Knowledge-fabric task and handoff relationships — only visible when that feed is active. |
| produced by / informed by | Knowledge-fabric artifact and decision relationships — only visible when that feed is active. |
Why this matters even when a node kind never appears
The node-type legend lists all eleven kinds — Workspace, Agent, Session, Bit, File, Memory, Task, Decision, Handoff, Artifact, Conflict — regardless of whether the knowledge-fabric feed is active or whether anything has ever produced a Conflict node. Seeing an entry in the legend is not the same as expecting to see that kind of node on your own map; see Navigating for how the same legend doubles as a visibility filter for whatever kinds do appear.
Always live
There is no "rebuild" or "refresh" step. The map reacts to what you do elsewhere in NEXUS — starting a session, capturing a bit, importing a file, sending a mesh message — on its own, as it happens.
Where to go next
- Navigating — search, zoom, pan, and the legend as a filter.
- Inspecting Nodes — what selecting a node actually shows you.
- Settings Reference — the node's own contextual settings panel.