debug

Root-cause debugging requires systematically tracing data and gathering evidence before attempting fixes. You must follow a four-phase workflow to investigate patterns, test hypotheses, and validate staged fixes to prevent symptom-focused patches.

To prevent symptom fixes, apply a defense-in-depth workflow that enforces root-cause tracing and evidence gathering. This structured process guards against shortcuts and ensures fixes remain grounded in the true trigger rather than superficial patches.

Start phase-based debugging by completing Phase 1: Root Cause Investigation before attempting any fixes. You then proceed sequentially through Pattern Analysis, Hypothesis & Testing, and Implementation to resolve integration issues.

Systematic debugging works for performance issues by defensively tracing environmental factors and deep call stacks. The workflow ensures you identify the true trigger through staged validation rather than applying patches that mask the underlying problem.

You should avoid symptom-focused patches whenever you face deep call stacks or integration problems. Always conduct root-cause investigation first to ensure traceability and prevent incomplete fixes that fail under pressure.

Phase-based debugging requires strict discipline and defensiveness in data tracing, which limits rapid patching. It demands thorough evidence gathering and staged validation, making it unsuitable for quick symptom suppression under time pressure.