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]>
59 lines
2.3 KiB
Markdown
59 lines
2.3 KiB
Markdown
# Readiness Check: Are You Actually Ready?
|
|
|
|
This isn't a graded quiz — it's a genuine self-assessment before you attempt something you can't
|
|
easily "retry with different answers memorized." Answer each honestly.
|
|
|
|
---
|
|
|
|
**1. Can you explain, without looking it up, the difference between a liveness probe and a
|
|
readiness probe, and diagnose which one is failing from `kubectl get pods` output alone?**
|
|
|
|
*If no:* revisit ROOT 10's gold-standard Health Probes module before attempting the Capstone —
|
|
this exact distinction shows up in Real Ops-style incidents.
|
|
|
|
---
|
|
|
|
**2. Given a Service with zero Endpoints, do you know the first two commands you'd run to find
|
|
out why, without being told which module this relates to?**
|
|
|
|
*If no:* revisit ROOT 07's Services & Service Discovery module.
|
|
|
|
---
|
|
|
|
**3. Can you apply the Observe → Evidence → Hypothesis → Test → Repair → Validate → Prevent
|
|
framework to an unfamiliar failure you've never specifically seen before, not just to the exact
|
|
examples from the lesson?**
|
|
|
|
*If no:* this is worth practicing deliberately — pick any Practice-tab scenario you haven't done
|
|
yet and narrate the framework out loud to yourself while solving it.
|
|
|
|
---
|
|
|
|
**4. Have you completed the Real Ops incidents in ROOT 12 for real — diagnosed and repaired
|
|
them yourself, not looked up the answer?**
|
|
|
|
*If no:* do this before attempting the Capstone. The required scenarios in every Capstone
|
|
attempt are drawn from exactly this style of incident.
|
|
|
|
---
|
|
|
|
**5. Do you have a rough time-budget plan for a 90-minute, multi-scenario attempt?**
|
|
|
|
*If no:* re-read the time-management lesson in this module before you begin.
|
|
|
|
## What to do if you answered "no" to more than one
|
|
|
|
That's genuinely useful information, not a failure — it tells you specifically where to spend
|
|
your remaining prep time. Go back to the relevant module, do the work for real, and come back
|
|
to this check again before attempting the Capstone.
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** In a live classroom, this works well as private/individual reflection rather
|
|
than a group discussion — the value is honest self-assessment, not a public performance.
|
|
|
|
**Approximate timing:** 5-8 minutes.
|
|
|
|
**Expected takeaway:** Readiness is something a student can genuinely self-assess against
|
|
concrete, specific criteria — not a vague feeling of confidence.
|