Knowledge map controls

Knowledge map controls help you move between overview and detail, inspect relationships, adjust generated structure, and reuse the visible map outside Atlas.

Core interactions

Control	What it does	Use it when
Zoom	Changes the visible scale of the map.	You need either a high-level overview or readable node detail.
Pan	Moves around the canvas.	The map is larger than the current viewport.
Select node	Opens or highlights a concept.	You want to inspect a claim, idea, method, or finding.
Select edge	Shows the relationship between nodes.	You need to understand why two concepts are connected.
Open nested node	Moves into a more detailed map level.	A concept needs decomposition.
Reset view	Returns to a stable framing.	You are lost in the canvas.
Export	Captures the map for sharing or reuse.	You need the map outside Atlas.

Generated structure

Knowledge maps are generated from source material. Node labels and relationships summarize the source, so treat the map as an interpretation layer. Verify important nodes against the original document before relying on them.

Editing

Use editing to clarify labels, remove noise, or make the map easier to present. Do not edit a map in a way that makes it look more certain than the source. If you change meaning, capture that as your own interpretation in notes rather than as source-derived structure.

Nested maps

Nested maps are useful when one concept contains multiple subclaims, mechanisms, steps, or evidence clusters. Use nesting to keep the top-level map readable while preserving detail.

Export quality

Before exporting, zoom to a level where labels are readable and important relationships are visible. A good export should communicate the structure without requiring the viewer to already know the source.

Common mistakes

Treating a map as proof instead of a navigation aid.
Exporting while zoomed too far out.
Editing away caveats that matter in the source.
Trying to force every source into a dense map when a summary or note would be clearer.