Educators & schools
You need safety, visible progress each week, and language that works for parents and admins. This path front-loads hardware students can see move, then adds software as “recipes,” then broadens to platforms.
Teacher one-pager — copy this into your syllabus or club handout.
- 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.
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.
Pair with Getting Started for ML vocabulary. Use the Forum for curriculum Q&A.