parallel-debugging

Debug distributed system bugs by applying the Analysis of Competing Hypotheses (ACH) methodology to generate multiple hypotheses and orchestrate parallel investigations across modules. This coordinates specialized agents to collect evidence and arbitrate root causes efficiently.

The Analysis of Competing Hypotheses (ACH) is a structured debugging methodology that generates multiple hypotheses, runs parallel evidence collection across components, and cross-references findings to arbitrate the true root cause of complex multi-module failures.

Coordinate parallel investigations by deploying specialized agents to focus on distinct failure modes like logic, data, state, integration, resource, and environment. The ACH framework structures their evidence collection and ensures clear exit criteria for arbitration.

Yes, structured hypothesis generation is designed for multi-module or distributed system bugs where several root causes are plausible. It requires generating hypotheses, collecting cited evidence across domains, and coordinating specialized investigators to pinpoint the failure.

Use parallel debugging when a bug spans multiple components and several root causes are plausible. If evidence must be collected across modules or services and standard linear troubleshooting fails to pinpoint the failure, ACH-based orchestration fast-tracks root cause arbitration.

Agent-based orchestration requires structured hypothesis generation upfront and depends on clear exit criteria for arbitration. Without specialized investigators assigned to distinct failure modes and proper evidence collection, the parallel debugging process cannot effectively converge on a root cause.