Session by session
- Session 56 · Ask & understandWeek 28
Define a command schema
Evidence: a question, sketch or new vocabulary
- Session 57 · Build & designWeek 29
Validate allowed pose names and required approval
Evidence: a design draft, dataset or build
- Session 58 · ImplementWeek 29
Show a preview before movement
Evidence: a working version, explained once
- Session 59 · Test & improveWeek 30
Test bad data, injection-like text and link loss
Evidence: a test log with at least one failure
- Session 60 · Explain & reflectWeek 30
Export an auditable command log
Evidence: an individual explanation
- P11 model
- local console
- arm or LED simulator
Fifteen cases including malformed commands; invalid input produces STOP.
A laptop model sends named commands only after bench tests, with a simulator as fallback.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG10-P09
Gesture Input Mapper
A one-joint flex-input controller, not an ML gesture recogniser.
Sessions 41-45Innovation only - RoboticsG10-P10
Sensor-Interlocked Arm
An arm model whose movement is inhibited by a separate sensor rule.
Sessions 46-50Innovation only - AIG10-P11
NLP Command Classifier
A restricted text-intent model with explicit refusal behaviour.
Sessions 51-55Innovation only - IntegratedG10-P12
AI Command Approval Console
A supervised command console; text never becomes arbitrary code or angles.
Sessions 56-60Innovation only
For school leadersChoose a starting point.
Build from evidence.
Pick the classes and a plan. We map the timetable, kit and safety checks with you, then pilot one class first.
- Prospectus and class-wise plan
- Kit and readiness check
- Pilot one class first
- Evidence at every milestone
Let's plan your pilot.
Share a few details and we will send the right plan for your classes.