debug

To fix unexpected test failures by tracing the root cause, use a systematic debugging framework that enforces a strict no-fix-without-root-cause-analysis policy. It guides you through investigation, pattern analysis, and call stack tracing to pinpoint the exact origin of the issue.

The best way to systematically troubleshoot performance issues and bugs is to follow a four-phase debugging approach: Investigation, Pattern Analysis, Hypothesis, and Implementation. This ensures thorough problem-solving and evidence-based verification before completing the fix.

Tracing errors backward through call stacks to find the origin of build failures involves systematically investigating the execution flow and analyzing error patterns. This framework isolates the exact failure point before implementing any code corrections.

Yes, you can use this systematic debugging approach to prevent bugs from recurring by implementing defense-in-depth validation. It adds multiple layers of validation during the implementation phase to ensure fixes are robust and verified with evidence.

You should not use a systematic root cause analysis approach for bug fixing when you need a quick, temporary patch, as this framework strictly enforces a no-fix-without-root-cause policy and requires full evidence-based verification protocols before claiming completion.