problem-analysis

To perform root-cause analysis for a software bug, you describe the observed problem to trigger a guided investigation that identifies underlying factors. The script orchestrates a structured workflow to synthesize signals and report the most plausible cause.

Investigating user-reported incidents requires evidence-based reasoning to collect and synthesize signals. A structured gate-hypothesize-investigate workflow logs decisions and formulates a root-cause report rather than providing immediate solutions.

The debugging workflow operates through a script-driven orchestration with a five-iteration cap. It progresses through Gate, Hypothesize, Investigate, Formulate, and Output phases to systematically narrow down root causes.

Yes, script-driven automation analyzes symptoms and identifies root causes without requiring custom logic. You simply describe the observed problem, and the built-in script orchestrates the investigation phases automatically.

Root-cause analysis does not provide solutions to fix software bugs or system failures. It strictly focuses on identifying the underlying causes and explaining supporting evidence, deliberately leaving solution implementation to other processes.

A five-iteration cap limits incident investigation to five script-driven cycles through the hypothesize and investigate phases. This constraint prevents infinite loops but means highly complex issues may require manual intervention if the root cause is not found within the limit.