avadbeta-investigate

To identify the root cause of a reported bug, you need a structured investigation workflow that gathers evidence, reproduces symptoms, and tests hypotheses to verify the exact failure point before applying a fix.

The best way to reproduce a failure for evidence-driven debugging is to systematically gather reported symptoms and inspect the error outputs, creating a reproducible scenario to form testable hypotheses about the root cause.

The three-strikes rule in root-cause analysis limits guesswork by allowing a maximum of three failed hypothesis tests before escalating the unresolved issue to human review, ensuring structured and evidence-first verification.

Yes, you can use this investigation workflow without automated tests by manually providing a concrete symptom description and error messages to initiate the hypothesis-driven analysis and evidence-based verification process.

You should escalate an unresolved bug investigation to human review after the three-strikes limit is reached, meaning three structured hypotheses have been tested and failed to identify the root cause of the reported failure.