investigate

Root-cause debugging is a systematic workflow that forces you to investigate underlying issues before applying fixes. It uses a four-phase process covering investigation, pattern analysis, hypothesis testing, and implementation to prevent masking symptoms.

To debug multi-module bugs, follow a structured workflow to investigate symptoms, reproduce the failure, and lock scope. This process isolates the root cause through pattern recognition and evidence-driven hypothesis testing before implementation.

Verify fixes by generating a root-cause hypothesis and a verification report during the implementation phase. This evidence-driven approach ensures the root cause is tested and resolved, preventing symptom masking.

The best way to test a root-cause hypothesis is through a disciplined debugging workflow. After investigating symptoms and analyzing patterns, you test the hypothesis against evidence and produce a verification report to validate the fix.

Pattern analysis is needed during the second phase of root-cause debugging. After collecting symptoms and reproducing the failure, you analyze patterns to lock the investigation scope and form a root-cause hypothesis.

Reproducing the failure is required to initiate the investigation phase. Root-cause debugging begins by collecting symptoms and reproducing the issue to establish a baseline for pattern analysis and hypothesis testing.