Session by session
- Session 46 · Ask & understandWeek 23
Control modes and human authority
Evidence: a question, sketch or new vocabulary
- Session 47 · Build & designWeek 24
Add an override button
Evidence: a design draft, dataset or build
- Session 48 · ImplementWeek 24
Separate auto, manual and stopped states
Evidence: a working version, explained once
- Session 49 · Test & improveWeek 25
Test mode transitions and power restart
Evidence: a test log with at least one failure
- Session 50 · Explain & reflectWeek 25
Publish an operator card
Evidence: an individual explanation
- Tracker
- button
- UNO
- approved supply
Eight transitions plus power-reset and end-limit tests.
A physical circuit, sensor or mechanism, built and tested on the bench.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG09-P09
Serial Data Dashboard
A local sensor-data dashboard with explicit error handling.
Sessions 41-45Innovation only - RoboticsG09-P10
Manual Override Tracker
A tracker with explicit manual control and safe startup.
Sessions 46-50Innovation only - AIG09-P11
NLP Label Explorer
A small text-routing model, not a general chatbot.
Sessions 51-55Innovation only - IntegratedG09-P12
AI Maintenance Adviser
A read-only AI maintenance adviser for the tracker; it cannot move hardware.
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.