root-cause-debugging

Diagnose production incidents, recurring bugs, teardown failures, race conditions, and misleading timeout symptoms by reconstructing evidence, asking three closing why questions, checking current primary-source practices, and designing fixes that remove the causal mechanism instead of masking it. Use for “find the root cause,” “look into this bug,” “why did this recur,” incident recovery plus follow-up work, and postmortem-quality debugging. Do not use for a straightforward known fix that needs no diagnosis.