systematic-debugging

Root cause investigation starts by reading error messages completely, reproducing the issue consistently, and checking recent changes. Then trace the failure backward through the call stack until you find the original trigger, and fix at that source rather than where the error appears.

Trace backward from the immediate cause by asking what called each function and what values were passed. Add stack trace instrumentation with console.error before the failing operation to capture the full call chain and identify the original trigger.

Defense-in-depth validation adds checks at every layer data passes through: entry point validation, business logic validation, environment guards, and debug instrumentation. This makes the bug structurally impossible rather than fixed at a single bypassable point.

Stop after three or more failed fix attempts and question whether the underlying architecture or pattern is fundamentally sound. Repeated failures indicate the hypothesis is wrong or the design itself needs reconsideration, not another quick patch.

Fixes fail repeatedly when they address symptoms instead of root causes, or when multiple variables change at once. Form a single hypothesis, test it with the smallest possible change, and verify the result before forming a new hypothesis.