ced4568andClaude Sonnet 5
de6c5b3286
root-12-real-ops gains a Detect -> Triage -> Diagnose -> Mitigate ->
Recover -> Verify -> Learn incident-response framing lesson at the
front of the existing 4-incident module, and a post-incident reflection
at the end — the incidents themselves are unchanged, still deliberately
un-guided ('you are responsible for this environment,' not 'complete
this exercise'). No fixes revealed; instructor notes carry the deeper
solution guidance the student-facing lesson intentionally withholds.
root-capstone-m02-capstone-readiness — a new READY orientation module:
what the Capstone measures, how the timed/randomized draw works, time
management and troubleshooting strategy under a clock, and a genuine
self-assessment checklist. Never publishes the current draw or answers.
See docs/ROOT_CAPSTONE_READINESS.md for why this module's completion is
deliberately independent of the real capstone's server-side unlock gate.
Co-Authored-By: Claude Sonnet 5 <[email protected]>
43 lines
2.2 KiB
Markdown
43 lines
2.2 KiB
Markdown
# Readiness Reflection: What Completion Means
|
|
|
|
Before you move toward the actual Capstone attempt, take a moment to reflect on the whole ROOT_
|
|
journey up to this point.
|
|
|
|
## Reflection questions
|
|
|
|
1. Think back to ROOT 05's opening lesson on desired state. How differently would you explain
|
|
that concept now, after everything since, compared to how you understood it the first time?
|
|
2. Which single module across ROOT_ changed how you approach a problem the most — not which was
|
|
most interesting, but which actually changed your behavior when something breaks?
|
|
3. What does passing the Capstone mean to you, beyond a completion record on the platform?
|
|
|
|
## What completion actually represents
|
|
|
|
A `capstone_completed` achievement isn't a certificate claiming you've memorized Kubernetes
|
|
trivia. It's the platform's record that you demonstrated, under real time pressure, without
|
|
step-by-step guidance, that you can diagnose and repair real operational problems using
|
|
frameworks you internalized rather than looked up in the moment. That's a materially different
|
|
and more durable skill than passing a multiple-choice exam about Kubernetes objects.
|
|
|
|
## When you're ready
|
|
|
|
There's no "perfect" moment where every module feels fully mastered — that's normal. If the
|
|
readiness check in the previous activity mostly came back "yes," and you've done the Real Ops
|
|
incidents for real, you're ready to attempt it. The Capstone will unlock automatically once the
|
|
platform confirms your prerequisite stages are genuinely complete — when you see it unlocked,
|
|
that's the platform's own confirmation, not just this module's.
|
|
|
|
This module is complete. Good luck.
|
|
|
|
## Instructor Notes
|
|
|
|
**Discussion questions for a live classroom:** question 2 tends to produce genuinely varied,
|
|
interesting answers across a cohort — worth having students share out loud if time allows.
|
|
|
|
**Approximate timing:** 8-10 minutes live discussion; 5 minutes self-paced writing.
|
|
|
|
**Preparation:** None — this is a closing/orientation activity, not a technical one.
|
|
|
|
**Expected takeaway:** Completing ROOT_'s Kubernetes sequence is a real, demonstrable skill
|
|
change, not just curriculum progress — the Capstone is where that becomes visible and provable.
|