ced4568andClaude Sonnet 5
e007bcf000
Adds all 6 ROOT 02 modules (Linux system administration, storage & filesystems, the Networking Mental Model, Linux network inspection, DNS & HTTP, Linux troubleshooting) — 37 activities, each with a real lesson, demonstration/guided exercise, knowledge check, hands-on Lab, and reflection. The Networking Mental Model module (M3) gets deliberately extra depth per its "critical module" designation, with no lab by design — conceptual mastery via knowledge check and guided exercise, matching root-05-m00's own precedent. Adds 6 new hands-on Linux/networking scenarios plus 2 MCQs: linux-service-inspection (inspects the platform's own real nginx without touching it — a genuinely safe, real service-inspection target that avoids ever risking the Lab's own connectivity), linux-service-lifecycle (start/ verify/stop a fully controllable service), linux-storage-inspection, linux-network-inspection (ip/ss/getent/curl, each framed as answering one specific diagnostic question), linux-dns-http-diagnosis (a genuine DNS-resolves-but-wrong-port failure, diagnosed and fixed), and linux-troubleshooting-framework (a real missing-config-file failure, resolved via the RootNode Observe/Evidence/Hypothesis/Test/Repair/Validate/Prevent framework). All tested end-to-end via the real scenario-validation API, including negative tests confirming they fail when unsolved. Wires rootnode-linux-networking-assessment (2 required + 4 random-draw scenarios) using the existing Phase 3B assessment engine. Co-Authored-By: Claude Sonnet 5 <[email protected]>
32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# 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.
|