ix-debug

Root cause analysis traces an execution path from a failure symptom to the most likely failing entry point and downstream nodes. It uses graph queries to locate and explain roles, callers, and failure positioning with minimal source reading.

Debugging orchestrator sequencing issues is handled by tracing downstream from an entry point to narrow down one to three suspicious nodes. It limits source reads to at most two candidate functions for confirmation, preserving token efficiency.

Pinpointing boundary or input problems starts by providing the error message or symptom description. The system locates likely entry points and identifies actionable root-cause candidates using graph reasoning and targeted tracing.

Diagnosing utility or helper assumption violations can optionally check upstream callers when invocation is likely. It traces downstream from the entry point first, then adaptively checks callers to narrow the suspicious nodes.

Root cause analysis fits debugging workflows for medium-complex codebases by narrowing the likely faulty boundary, orchestrator, or utility contract. It outputs one to three candidates with evidence, limiting source reads to suspected failure points.

Failure triage using graph queries limits source reading to at most two candidate functions for confirmation. It is designed for medium-complex codebases and focuses on boundary, orchestrator, and utility failures rather than widespread architectural issues.