ced4568andClaude Sonnet 5
d066410451
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]>
2.3 KiB
2.3 KiB
ROOT_ V1 Student Requirements
Phase 6F Step 14. RootNode's Labs run remotely — nothing computationally heavy needs to happen on a student's own device.
Remote / self-paced learners
- Browser: any current Chromium-based browser (Chrome, Edge) or Firefox. No browser extensions or plugins required.
- Internet: a stable broadband connection sufficient for a persistent web session and a terminal-like interface (similar bandwidth needs to a video call, generally lower).
- Device: a laptop or desktop with a physical or usable on-screen keyboard. A Chromebook is sufficient — all Lab computation happens on RootNode's infrastructure, not the student's device.
- Tablets/phones: not recommended as a primary device — the terminal-and-multi-pane interface assumes a real keyboard and a reasonably sized screen; nothing about it is technically blocked on a tablet, but it will be an uncomfortable experience.
- Local installation: none. No Docker, no Kubernetes, no Git client needs to be installed locally — every Lab (including the nested Docker Engine and the Kubernetes cluster from ROOT 05 onward) runs in RootNode's disposable, remote Lab environment.
- Microphone/camera: not required by the platform itself. Only relevant if a specific instructor-led delivery format (e.g. a live video cohort) separately requires it for its own video conferencing — that's a delivery-format decision, not a platform requirement.
In-person / camp delivery
- RootNode provides: the Lab environment (accessed via any device meeting the remote requirements above), course content, and instructor tooling.
- Student/venue provides: the device itself (or the venue provides one), a keyboard, and internet access to reach RootNode's platform. No specialized hardware, no local software installation, no purchase requirements beyond program enrollment.
- Venue/instructor should verify in advance: enough physical outlets/devices for the cohort size, and that the venue's network doesn't block outbound HTTPS to RootNode's domain.
What RootNode explicitly does NOT require
No specific CPU/RAM/GPU spec, no paid software license, no local admin rights on the student's device (nothing is installed), and no specific operating system beyond "runs a current browser."