Educators & schools
This is the educator view of the same Academy. It keeps the curriculum coherent while front-loading safe, visible wins and giving you a way to explain pacing, challenge design, and discussion habits to students, parents, and administrators.
- Safety & space: Clear volume, hair/lanyards, estop rehearsal before student contact.
- Materials: One powered arm or sim per 2–3 students; journal for hypotheses and failure logs.
- Pacing: One SVRC chapter ≈ 1–2 weeks with a visible “win” (motion, graph, or short video).
- Differentiation: Strong coders → Software stack; builders → Design & integration.
- Community: Use the Forum for curriculum Q&A; tag posts with your school if helpful.
Standards: map outcomes to CSTA K–12 CS practices or NGSS science & engineering practices — each Academy chapter ends with a short outcomes list you can align.
Best for
Classrooms, clubs, and mentor-led cohorts that need one predictable rhythm: concept, bounded practice, and a challenge students can share publicly.
Keep in reserve
Treat Humanoids & mobile and larger platforms as stretch units. The core educational value still starts with visible motion, safe logging, and system vocabulary.
Recommended module order
- 1 · Motion first: SO-101 arm — Big, safe motions; teach & repeat.
- 2 · Hands & grasp: Dexterous hands — Why grippers vs fingers.
- 3 · Software story: Software stack — Drivers → sim without shame.
- 4 · Systems talk: Communication & architecture — How parts become a system.
- 5 · Optional stretch: Humanoids & mobile — When the cohort is ready.
Use the Academy as a teaching system: follow the curriculum hub for the canonical order, then use this page to decide pacing, what to skip for now, and where to send students for chapter-specific discussion.