Traverse a node in the graph explorer
The /graph view is Atlas’s manual mode. Investigate asks natural-language questions; the graph explorer lets you hand-walk the typed edges yourself. Use it when a Resolve query returns too much or too little and you want to see the shape of the neighborhood.
1 · Search for a node
Section titled “1 · Search for a node”The explorer opens on a search box. Type an artifact name — BAPI_PO_CREATE1, I_Customer, VBAK — and pick the match. The canvas centers on that node and renders its immediate neighbors.
Each node is colored by type: blue for SAP artifacts, green for guidance, pink for documents, amber for version scope, gold when the node is the currently-focused root.
2 · Walk the neighbors
Section titled “2 · Walk the neighbors”Click any neighbor to refocus. The graph fans out one more hop. Common patterns you will want to walk:
atlas:supersedes— what replaces this?atlas:guidesFrom/guidesTo— what guidance connects these two artifacts?atlas:belongsToModule— which module does this live in?atlas:supportedByStatement— what document backs this claim?
Every edge is labeled with its IRI. Hover an edge to see its rdfs:label in plain English.
3 · Read provenance
Section titled “3 · Read provenance”Click a node’s Provenance tab in the right panel. Atlas prints the sourcedFrom chain:
- which document first mentioned this node
- the section and paragraph it came from
- the content hash and the fetch timestamp
A node with multiple sources shows multiple rows — that is the entity-resolution signal: Atlas has collapsed different source names into this one identity. See Why a knowledge graph for the rationale.
4 · Export to table
Section titled “4 · Export to table”The canvas has an Export table button in its toolbar. It flattens the currently-rendered subgraph to a CSV-style grid (one row per node, columns = neighbor types). Useful for handing a slice of the graph to someone who does not have access to Atlas yet.
When to use the explorer instead of Investigate
Section titled “When to use the explorer instead of Investigate”- You have a specific node and want its exact neighborhood.
- You are debugging why Investigate returned a weird result — walk from a known-good anchor.
- You are mapping a small domain by hand for a report.
For “what blocks X?”-shaped questions, Investigate is faster. For “why did Atlas link these two?” questions, the explorer is the only tool that shows you.