parallel-debugging

Debug ambiguous multi-module issues by organizing parallel agent investigations using the Analysis of Competing Hypotheses (ACH) methodology, generating hypotheses across six failure categories and arbitrating root causes with structured evidence.

The Analysis of Competing Hypotheses (ACH) is a root-cause-analysis methodology that generates parallel failure hypotheses across six categories, collects formal evidence with citations, and arbitrates findings to determine the true root cause.

Conduct a parallel investigation for software debugging by generating hypotheses across six failure-mode categories (Logic Error, Data Issue, State Problem, Integration Failure, Resource Issue, Environment), collecting cited evidence, and following a stepwise arbitration workflow.

Yes, this debugging approach is designed for multi-module systems, systematically addressing integration failures alongside logic errors, data issues, state problems, resource issues, and environment failures through structured parallel investigation.

The best way to validate fixes after root-cause-analysis is to follow the stepwise arbitration workflow, which uses evidence templates, citation rules, and risk assessment to confirm the determined root cause before applying fixes.

Use parallel hypotheses for debugging instead of standard methods when facing complex issues with ambiguous root causes in multi-module systems, where systematic evidence collection and structured arbitration are needed to isolate the failure category.