Session by session
- Session 46 · Ask & understandWeek 23
Startup, running, lost-line and stopped states
Evidence: a question, sketch or new vocabulary
- Session 47 · Build & designWeek 24
Draw event and transition rules
Evidence: a design draft, dataset or build
- Session 48 · ImplementWeek 24
Implement timeout and manual isolation
Evidence: a working version, explained once
- Session 49 · Test & improveWeek 25
Test state priority and reset
Evidence: a test log with at least one failure
- Session 50 · Explain & reflectWeek 25
Publish an operator checklist
Evidence: an individual explanation
- LFR kit
- physical power switch
- local console
All transitions plus five intentional faults.
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
- 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.