Adds PHASE6E_ROOT_FOUNDATIONS_COMPLETION.md (the phase's own record: what was authored, the dash-vs-bash scenario bug found and fixed, the pre-existing lock-enforcement gap found and fixed, the regression fallout that fix revealed in earlier suites and why each was a stale test assumption rather than a platform bug, and honest test/rehearsal/regression results). Updates ROOT_FOUNDATIONS_PILOT_READINESS.md (full re-audit: all 4 ROOT Foundations courses now READY, not inherited blindly from Phase 6D), ROOT_PROGRAM_DURATION_MODEL.md (real ROOT 02-04 duration data: 24.7 combined hours, landing inside Phase 6D's own estimated range; 67.9 hours across the full authored program), ROOT_PILOT_CURRICULUM.md (ROOT 02-04 move from NOT IN PILOT to IN PILOT with full module-level detail; the pilot is now genuinely self-paced-capable for the entire foundational half, not just instructor-led), ROOT_PROGRAM_ARCHITECTURE.md and ROOT_CURRICULUM_COVERAGE_MATRIX.md (course/module/scenario totals), and ROOT_FOUNDATIONS_ARCHITECTURE.md (marked as-built, not just as-designed). Co-Authored-By: Claude Sonnet 5 <[email protected]>
3.5 KiB
ROOT_ Program Duration Model
Phase 6E §28 — recalculated from actual authored activities in the live database. Run:
SELECT c.course_id, SUM(a.estimated_duration_minutes) ... GROUP BY c.course_id against the
current schema, same method as Phase 6D's original version of this document.
Per-course totals (self-paced estimate)
| Course | Activities | Minutes | Hours |
|---|---|---|---|
| ROOT 01 Computing & Linux Foundations | 35 | 338 | 5.6 |
| ROOT 02 Linux Administration & Networking | 37 | 388 | 6.5 |
| ROOT 03 Git & Collaborative Development | 31 | 312 | 5.2 |
| ROOT 04 Containers & Docker | 43 | 444 | 7.4 |
| ROOT 05 Kubernetes Foundations | 28 | 403 | 6.7 |
| ROOT 06 Kubernetes Application Workloads | 22 | 295 | 4.9 |
| ROOT 07 Kubernetes Networking & Configuration | 27 | 353 | 5.9 |
| ROOT 08 Kubernetes Storage & Scheduling | 15 | 250 | 4.2 |
| ROOT 09 Kubernetes Security | 40 | 745 | 12.4 |
| ROOT 10 Kubernetes Troubleshooting & Observability | 20 | 277 | 4.6 |
| ROOT 11 DevOps & Platform Engineering | 3 | 35 | 0.6 |
| ROOT 12 Real Ops | 6 | 115 | 1.9 |
| ROOT Capstone | 5 | 120 | 2.0 |
| Total (all authored content) | 312 | 4,075 | 67.9 |
ROOT Foundations (01-04) subtotal: 146 activities, 1,482 minutes, 24.7 hours. This is now real, measured data — Phase 6D's own version of this document correctly flagged the eventual "20-25 hour" range as a planning ESTIMATE pending real authorship; the actual total (24.7 hours) landed inside that estimated range.
Self-paced vs. instructor-led
As in Phase 6D's version of this document: the figures above are self-paced estimates (the sum
of each activity's own estimated_duration_minutes). Instructor-led classroom time is still not
a separate summable database field — every Instructor Notes section documents approximate live-
facilitation timing in prose (e.g. ROOT 02 Module 3's "25 minutes read; 15-20 minutes live with
discussion — longer than a typical lesson, deliberately"), but this remains per-activity
guidance embedded in Markdown, not a column a query can sum. A future phase could add a distinct
estimated_duration_minutes_instructor_led column if precise classroom scheduling becomes a
real, measured need.
As a conservative approximation, instructor-led delivery of the full 67.9-hour curriculum should be expected to run somewhat longer once live discussion and demonstration time is added — consult the relevant Instructor Notes before scheduling a live cohort session, don't treat the self-paced total as a classroom-time promise.
What this is NOT
Not a marketing duration, not a promise, not a certification-hours figure.
estimated_duration_minutes values were authored as honest guesses (see
docs/COURSE_AUTHORING_STANDARD.md §4) — this total will get more accurate as real completion-
time data accumulates from actual students, not before.
Program completeness
With ROOT 01-04 now authored, the ROOT_ program's structured curriculum (excluding ROOT 08,
deliberately deferred as non-capstone-gating, and ROOT 11 modules 2-7, deferred pending future
lab infrastructure — see docs/ROOT_PILOT_CURRICULUM.md) now runs a complete, measured
beginning-to-advanced path: Linux fundamentals → Linux administration/networking → Git →
containers → Kubernetes → security → troubleshooting → real operations → capstone. This is the
first phase where the FULL foundational-to-capstone path has real, authored content and a real
measured duration at every step, not a partial curriculum starting mid-stack.