docs(phase6f): document ROOT_ V1 pilot readiness
New: PHASE6F_ROOT_V1_PILOT_READINESS.md (phase summary), ROOT_V1_CURRICULUM_MANIFEST.md (canonical V1 scope), ROOT_V1_PREREQUISITE_MAP.md, ROOT_V1_ASSESSMENT_MAP.md, ROOT_V1_SYLLABUS.md, ROOT_V1_INSTRUCTOR_GUIDE.md, ROOT_V1_STUDENT_REQUIREMENTS.md, ROOT_V1_INSTRUCTOR_LED_PILOT.md, WINTER_BREAK_CAMP_CURRICULUM_OPTIONS.md. Updated: ROOT_PROGRAM_ARCHITECTURE.md (course-sequence table reflects real V1 statuses), ROOT_PILOT_CURRICULUM.md (self-paced-readiness correction), ROOT_PROGRAM_DURATION_MODEL.md (real post-integration totals: 64.2 V1 hours / 68.3 program-wide), ROOT_CAPSTONE_READINESS.md (§1b, the new root-09 course-layer gate), platform/README.md (test list). Co-Authored-By: Claude Sonnet 5 <[email protected]>
This commit is contained in:
@@ -27,6 +27,19 @@ This module derives its own completion the same way every other lesson-only modu
|
||||
capstone assessment engine checks before allowing a start (see §3 below for why these two gates
|
||||
are deliberately independent).
|
||||
|
||||
## 1b. A third, independent gate added in Phase 6F
|
||||
|
||||
Phase 6F added `root-09-kubernetes-security` to `root-capstone`'s own `courses.prerequisites`
|
||||
array (alongside the pre-existing `root-12-real-ops`) — a course-content-model-level gate,
|
||||
distinct from both this readiness module (still non-gating) and the curriculum-path
|
||||
`unlock_rule` in §3 below (still unchanged: six K8s scenario stages, no security stage). This
|
||||
means the `root-capstone` COURSE itself (visible in the student/instructor course tree) is now
|
||||
locked until ROOT 09 is also complete, even though the underlying `/api/assessments/rootnode-
|
||||
capstone/start` route's own gate did not change. See `docs/ROOT_V1_CURRICULUM_MANIFEST.md`
|
||||
Step 7 for the full evidence and reasoning, and `031_phase6f_capstone_security_prerequisite.sql`
|
||||
for the migration. This adds a third independent layer rather than blurring the existing two —
|
||||
consistent with this document's own §3 reasoning for keeping enforcement layers separate.
|
||||
|
||||
## 2. What was NOT built
|
||||
|
||||
No answers, no exact scenario IDs from the current pool, no capstone-specific hint content
|
||||
|
||||
Reference in New Issue
Block a user