What problem does it solve?
It helps you perform evidence-driven root cause analysis when an outcome is ambiguous and you need to justify the “why” using competing explanations rather than guesswork.
Core Features & Use Cases
- Evidence-driven causal tracing: Preserve an explicit chain from observation to hypotheses through evidence for/against.
- Competing hypotheses in parallel: Generate and evaluate multiple distinct cause categories (implementation, environment/config/orchestration, and measurement/assumption mismatch).
- Discriminating probe design: Recommend the single next test that would most reduce uncertainty between the top competing hypotheses.
- Rebuttal and ranking: Use a structured rebuttal round and synthesize the best explanation with clearly stated unknowns.
Use cases: runtime regressions, performance/latency anomalies, architecture/orchestration behavior, config or routing issues, and postmortem/analysis of surprising system behavior.
Quick Start
Ask: trace this: <observation to trace> and include the exact observed result and any relevant logs or metrics you have.