debug-standard

A structured root-cause analysis workflow systematically traces reproducible software bugs to their underlying cause using a four-phase process: observation and reproduction, hypothesis investigation, root cause identification, and fix implementation.

Debug cross-component defects by documenting steps to reproduce, recording observed versus expected behavior, generating hypotheses, collecting evidence, and planning a robust fix with safe escalation for large-scale changes.

Document steps to reproduce by clearly recording the reproduction actions, environment details, observed behavior, and expected behavior to support a structured hypothesis investigation and evidence collection process.

Use a phase-based debugging workflow when diagnosing reproducible bugs with clear symptoms that span multiple components, environments, or builds, ensuring repeatable root-cause analysis and safe escalation for large-scale failures.

Yes, a hypothesis-driven approach supports investigating cross-component failures by requiring documented hypotheses, evidence collection, and clear checkpoints between observation, investigation, root cause identification, and implementation phases.

Root-cause debugging includes safe escalation guidelines specifically for large-scale or cross-component failures, ensuring that complex fixes are planned with proper evidence and documentation before implementation.