investigate

Root-cause debugging uses a phased investigative workflow to identify underlying causes before applying fixes. You collect symptoms, inspect code paths, check recent changes, and form evidence-based hypotheses to prevent wasted effort and repeated regressions.

Debugging intermittent errors requires a structured investigation workflow with deterministic steps. You apply phased analysis—investigate, analyze, hypothesize, implement—to systematically trace symptoms through code paths and verify outcomes using telemetry.

Hypothesis testing during debugging validates root-cause theories with minimal, safe changes and controlled experiments. You verify each hypothesis systematically before implementing fixes to ensure the change addresses the actual cause without introducing regressions.

Phase-driven investigation applies to debugging tasks ranging from failing reproductions to intermittent errors. The workflow enforces structured analysis across investigate, analyze, hypothesize, and implement phases, with escalation when needed for complex cases.

Telemetry and documentation record decisions, outcomes, and rationale during root-cause debugging to verify fixes and enable future audits. This structured recording prevents repeated regressions and supports knowledge transfer across teams.