Skip to main content
Start with a specific subsystem or concept, then narrow your investigation. A compact query is usually more useful to an assistant than the whole architecture report.

​
Gather context with query

query finds relevant starting nodes and traverses their relationships. Breadth-first traversal gathers a broader neighborhood. --dfs follows a deeper chain:

​
Inspect one concept with explain

Take a label or node ID from the query results:
Look at its source, community, and incoming and outgoing relationships. Inspect the source itself when a precise implementation detail matters.

​
Trace a relationship with path

This uses the tutorial’s example project. In your project, replace the labels with real nodes. Stored direction is respected; add --undirected when you want connectivity rather than a directional path.

​
Ask the assistant to preserve uncertainty

Use Graphify to trace how a request reaches persistence. Show the path and source references. Flag inferred or ambiguous edges, and tell me if the graph is missing evidence.
The tool supplies context, and the assistant interprets it. Ask for evidence and avoid treating an absent path as proof that two systems are independent.