gds-investigate

To trace a root cause from evidence, generate a structured case file that reconstructs the incident, grading observations and tracking hypotheses to guide cautious debugging and team escalation.

Evidence-led bug investigation reconstructs what happened from available system evidence by generating a structured case file, used when diagnosing failures, tracing incidents, or building mental models of unfamiliar code areas.

Yes, you can use a case file to build a mental model of unfamiliar code by recording observations, hypotheses, and next steps, creating a persistent reference that teammates can pick up cold before working on it.

Start an investigation case by initializing a new case with a descriptive slug, which establishes a persistent slug-based path to collect evidence and write outcomes using the provided case-file template.

Yes, when diagnosing a failing module, this approach generates a case file that records observations, hypotheses, and next steps, supporting knowledge transfer for teammates picking up the investigation cold.

The best way to document an incident investigation is generating a structured case file with evidence-graded findings, calibrated to the input, which engineers can pick up cold to understand what happened.