diagnose

Debug flaky tests and performance regressions by building an evidence-driven diagnosis loop that establishes a deterministic pass/fail signal before hypothesizing or changing code. Generate ranked falsifiable predictions, instrument specifically to distinguish them, and verify the fix.

Root-cause-analysis for hard bugs uses a reproduction-first discipline, requiring a deterministic repro command, trace replay, or disposable harness to establish a clear signal. It refuses to proceed with hypothesis testing until a reliable trigger exists.

Create a failing regression test at the correct seam to capture the bug before applying a fix. Once the original scenario no longer reproduces, the test passes, ensuring the regression is verified and preventing future recurrences.

Verify falsifiable hypotheses during debugging by generating three to five ranked predictions and instrumenting only what distinguishes them. This evidence-driven approach targets specific variables within the diagnosis feedback loop to isolate the root cause.

Yes, this debugging approach applies to scenarios requiring minimization, trace replay, differential runs, or disposable harnesses. It establishes a deterministic signal across failing, throwing, flaky, or slow behaviors.

Hand off to TDD, architecture improvement, or prototype harnesses during root-cause-analysis when the right diagnosis loop or test seam does not exist yet. This enables evidence-driven handoffs to establish the necessary deterministic feedback signal.