Skip to content

Incident Review Guide

Guide Fit

flowchart TD
  family["Reproducible Research"] --> program["Deep Dive Snakemake"]
  program --> pressure["A concrete learner or reviewer question"]
  pressure --> guide["Incident Review Guide"]
  guide --> next["Modules, capstone, and reference surfaces"]
flowchart TD
  question["Name the exact question you need answered"] --> skim["Skim only the sections that match that pressure"]
  skim --> crosscheck["Open the linked module, proof surface, or capstone route"]
  crosscheck --> next_move["Leave with one next decision, page, or command"]

Read the first diagram as a timing map: this guide is for a named pressure, not for wandering the whole course-book. Read the second diagram as the guide loop: arrive with a concrete question, use only the matching sections, then leave with one smaller and more honest next move.

Use this page when the question is about incident response, reproducibility under pressure, or workflow debugging with evidence instead of intuition.

  1. Read Capstone Walkthrough.
  2. Use Proof Matrix to choose the narrowest command for the current symptom.
  3. Compare the result with Profile Audit Guide and Publish Review Guide if the problem spans multiple boundaries.

Back to top

What A Good Incident Review Can Answer

  • whether the failure is about workflow semantics, execution policy, or downstream trust
  • which command gives the most honest first evidence
  • which files should remain unchanged until stronger proof exists

Back to top