ix-investigate

You can investigate a function symbol by building a graph-backed mental model of its role and execution flow. This approach uses graph data to locate and explain the target, producing caller and callee connections to clarify the execution path before any source reading.

The best way to perform root cause analysis on a bug candidate is using graph reasoning to trace the symbol's upstream and downstream connections. This evidence-driven method maps the execution path and limits source scanning to at most one targeted code read if the graph cannot resolve the question.

You need graph-based code understanding when you must deep-dive a specific feature or symbol without getting lost in large files. It locates and explains the target using graph evidence first, preventing excessive searching and unbounded scanning across the codebase.

Yes, you can save the investigation report to a markdown file. By using the save mode with a chosen or auto-generated markdown path, the final graph-based execution flow and symbol analysis output is written directly to that file.

Yes, graph reasoning for call graph tracing can include relevant recorded decisions affecting the symbol when Ix Pro is available. This provides additional design context alongside the execution flow and caller or callee connections during the investigation.

The main limitation is that graph data may not always fully resolve the execution path. When this happens, the investigation falls back to a single targeted source code read, bounding the effort but indicating the graph lacked sufficient evidence to complete the understanding.