Adds PHASE6D_ROOT_FOUNDATIONS.md (the phase's own record: the generic-scenario-engine finding, the tested container-runtime decision, what was authored, the bugs found and fixed, and honest test/regression/rehearsal results) and ROOT_FOUNDATIONS_PILOT_READINESS.md (module-by-module READY/DEFERRED classification for ROOT 01-04 against the unchanged Phase 6C readiness standard — ROOT 01 READY, ROOT 02-04 DEFERRED by design). Adds ROOT_PROGRAM_DURATION_MODEL.md — real per-course instructional-hour totals computed from actual estimated_duration_minutes values (2,931 minutes / 48.9 hours across all authored content), not invented, with an explicit note on why instructor-led timing isn't a separate summable field yet. Updates ROOT_PROGRAM_ARCHITECTURE.md (ROOT 01's new READY status and the real 01-04 prerequisite chain), ROOT_PILOT_CURRICULUM.md (ROOT 01 added to the pilot, module-level detail), and ROOT_CURRICULUM_COVERAGE_MATRIX.md (updated module/scenario totals) to reflect what Phase 6D actually built, without restating Phase 6C's own Kubernetes-scenario tables. Co-Authored-By: Claude Sonnet 5 <[email protected]>
66 lines
4.2 KiB
Markdown
66 lines
4.2 KiB
Markdown
# ROOT Foundations Pilot Readiness — ROOT 01-04
|
|
|
|
Phase 6D §24 — the honest READY/PARTIAL/DEFERRED classification for ROOT 01-04, using the same
|
|
bar `docs/ROOT_PILOT_READINESS_STANDARD.md` established in Phase 6C. The standard is not
|
|
lowered because these courses are new.
|
|
|
|
## ROOT 01 — Computing & Linux Foundations: READY
|
|
|
|
All 6 modules meet the 8-point standard:
|
|
|
|
| Module | Status | Evidence |
|
|
|---|---|---|
|
|
| M1 How Computers Run Software | READY | Lesson, guided exercise, real hands-on lab (`linux-inspect-hardware`), reflection. Verified via `e2e-phase6d.js` and the real-Lab rehearsal (`infra/scripts/drills/test-phase6d-foundations-rehearsal.js`). |
|
|
| M2 Linux and the Shell | READY | Full gold pattern (lesson/demo/kc/guided/lab/reflection). Lab (`linux-shell-basics`) tested end-to-end via the real scenario-validation API, including a negative test (fails when unsolved). |
|
|
| M3 Navigating the Filesystem | READY | Full gold pattern. Lab (`linux-filesystem-navigation`) tested end-to-end. |
|
|
| M4 Files and Text | READY | Full gold pattern. Lab (`linux-files-and-text`) tested end-to-end. |
|
|
| M5 Processes | READY | Full gold pattern. Lab (`linux-process-management`) tested end-to-end, including a negative test (fails while the process is still running). |
|
|
| M6 Users & Permissions Foundations | READY | Full gold pattern. Lab (`linux-permissions-foundations`) tested end-to-end via the real-Lab rehearsal, including a REAL permission denial (a second Linux user genuinely denied read access) before the fix. |
|
|
|
|
**Self-paced readiness:** confirmed programmatically — `infra/scripts/validate-course-content.js`'s
|
|
deferral-phrase check and `e2e-phase6d.js`'s equivalent live check both scan every ROOT 01
|
|
activity's student-visible content for "ask your instructor" or equivalent and found none.
|
|
|
|
**Instructor-led readiness:** every lesson/demonstration/guided_exercise/reflection activity has
|
|
a real Instructor Notes section (timing, misconceptions, discussion questions), verified hidden
|
|
from students both statically and via a live API check.
|
|
|
|
**Assessment:** `rootnode-linux-foundations-assessment` wired and verified live (real draw: 2
|
|
required hands-on tasks + 2 random hands-on tasks + 2 random MCQs, 6 scenarios total).
|
|
|
|
## ROOT 02 — Linux Administration & Networking: DEFERRED
|
|
|
|
Architecture fully designed in `docs/ROOT_FOUNDATIONS_ARCHITECTURE.md` (6 modules, including the
|
|
explicitly "critical" Networking Mental Model module). Zero modules authored this phase — course
|
|
remains `status = 'planned'`, honestly, with a real (not fabricated) `prerequisites` gate to
|
|
ROOT 01 already in place so the sequence is correct once it IS authored.
|
|
|
|
## ROOT 03 — Git & Collaborative Development: DEFERRED
|
|
|
|
Architecture designed (6 modules, local-repository-only strategy documented in
|
|
`docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md` §4). Zero modules authored this phase.
|
|
|
|
## ROOT 04 — Containers & Docker: DEFERRED (content) / PLATFORM EXTENSION DONE
|
|
|
|
Architecture designed (8 modules). **The platform extension ROOT 04 needs — a nested Docker
|
|
Engine inside the Lab — was built and verified this phase** (`docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md`
|
|
§3: real `docker run`, `docker build`, and `docker compose` all tested working inside the actual
|
|
`rootnode-academy:test` image under production resource constraints). No course content was
|
|
authored against it yet — that's a real, substantial content-authoring effort left for a future
|
|
phase, now unblocked by this phase's platform work.
|
|
|
|
## Why ROOT 02-04 were not authored this phase
|
|
|
|
Given realistic effort constraints in a single phase, authoring, testing, and verifying ROOT 01
|
|
to the same rigor as every ROOT 05+ module (real scenarios, live end-to-end verification, a
|
|
real-Lab rehearsal, an assessment) was prioritized over shallow architecture-only coverage
|
|
across all four courses. This mirrors Phase 6C's own precedent: some content built to a genuine
|
|
READY bar, the rest explicitly and honestly DEFERRED with a real reason, rather than every
|
|
course padded to look further along than it is (`e2e-phase6d.js`'s own first test explicitly
|
|
asserts ROOT 02-04 have zero modules, catching any future accidental over-claim).
|
|
|
|
## Honest totals
|
|
|
|
**READY: 1 course (ROOT 01), 6 modules. DEFERRED: 3 courses (ROOT 02-04), 0 modules — by
|
|
design, not oversight.**
|