Session by session
- Session 51 · Ask & understandWeek 26
Define supported maintenance intents
Evidence: a question, sketch or new vocabulary
- Session 52 · Build & designWeek 26
Use synthetic short text examples
Evidence: a design draft, dataset or build
- Session 53 · ImplementWeek 27
Train a local text classifier
Evidence: a working version, explained once
- Session 54 · Test & improveWeek 27
Test unknown and contradictory requests
Evidence: a test log with at least one failure
- Session 55 · Explain & reflectWeek 28
Link results to source-backed checklists
Evidence: an individual explanation
- Local Python
- reviewed synthetic phrases
- device notes
Twenty held-out cases; unsafe requests routed to a teacher.
A model, an evaluation study or an AI-checking workflow.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG11-P09
Local Telemetry Monitor
A local telemetry dashboard and error log.
Sessions 41-45Innovation only - RoboticsG11-P10
Fail-Safe State Machine
A deterministic robot supervisor independent of ML output.
Sessions 46-50Innovation only - AIG11-P11
Text Maintenance Triage
A restricted maintenance-triage model, not a free-form repair authority.
Sessions 51-55Innovation only - IntegratedG11-P12
AI Maintenance Console
A read-only AI-assisted troubleshooting console for the robot.
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.