analyze

Root cause analysis for runtime bugs uses a structured investigation process of tracking observations, forming hypotheses, and validating evidence across files. It preserves file:line references to maintain provenance and systematically narrows down the root cause.

Investigating a performance regression requires evidence-driven cross-file reasoning to identify the root cause. You document observations, test hypotheses against evidence, and record the current best explanation with file:line references to pinpoint the regression source.

Yes, architecture and dependency analysis supports team-mode orchestration with parallel tracer lanes. This allows you to investigate complex cross-file dependencies concurrently, preserving structured observations and evidence for comprehensive architecture reviews.

Evidence-based code analysis works by following a structured reasoning loop: Observation to Hypotheses to Evidence For/Against to Current Best Explanation to Critical Unknown to Discriminating Probe. This ensures root causes are validated through provenance-preserving file:line references.

Structured reasoning is needed for cross-file code investigation when problems require comprehensive root cause analysis, such as runtime bugs, performance regressions, or architecture reviews. It organizes observations and hypotheses to prevent losing critical evidence across complex codebases.

Yes, the root cause analysis investigation operates with no external dependencies or components. You simply provide a description of the issue and request an evidence-based analysis across relevant files to begin the structured investigation.