# Reflection: This Is the Same Framework You'll Use for the Rest of ROOT_

## Reflection questions

1. Which framework step did you personally find easiest to skip or rush through in this
   module's Lab? Why do you think that step specifically tempts shortcuts?
2. You've now used this exact seven-step framework — Observe, Gather Evidence, Form Hypothesis,
   Test, Repair, Validate, Prevent Recurrence — at the Linux level. Where do you expect to use
   it again?

## Real Ops takeaway

**This entire course, from Module 1's five-question service checklist through Module 5's
failure-category taxonomy, was building toward this one repeatable discipline.** You'll meet
this exact framework again, formally named, in ROOT 10 — applied to Kubernetes instead of raw
Linux. Having already practiced it here means ROOT 10 won't be teaching you a new skill, just
retargeting a skill you already have.

This module — and ROOT 02 — is complete. Continue to ROOT 03: Git & Collaborative Development.

## Instructor Notes

**Discussion questions for a live classroom:** question 1 tends to surface "Prevent Recurrence"
and "Form Hypothesis" (jumping straight to a guessed fix) as the two most commonly admitted
shortcuts — worth normalizing as a real, common temptation rather than a personal failing.

**Approximate timing:** 8-10 minutes live discussion; 5 minutes self-paced writing.

**Milestone note:** this is the last module of ROOT 02 — consider a short recap connecting all
six modules (services → storage → networking model → inspection tools → DNS/HTTP → framework)
before moving to ROOT 03.