Session by session
- Session 36 · Ask & understandWeek 18
When should a system refuse to act?
Evidence: a question, sketch or new vocabulary
- Session 37 · Build & designWeek 19
Add confidence and freshness gates
Evidence: a design draft, dataset or build
- Session 38 · ImplementWeek 19
Write an append-only decision log
Evidence: a working version, explained once
- Session 39 · Test & improveWeek 20
Replay held-out sessions through the full link
Evidence: a test log with at least one failure
- Session 40 · Explain & reflectWeek 20
Trace one decision through the log
Evidence: an individual explanation
- P04 to P07 builds
- USB or simulator
- manual override switch
Same held-out sessions and safety limits; every rejection logged with a reason.
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
- RoboticsG12-P05
Trigger Timing and Latency Lab
A debounced trigger window and a measured end-to-end delay for the sound channel.
Sessions 21-25Builder and up - RoboticsG12-P06
Power-Budget Bench
A measured power budget for the model room, with a battery-life estimate checked against a timed run.
Sessions 26-30Builder and up - AIG12-P07
False-Trigger Budget Study
An operating threshold justified by the cost of false triggers against missed knocks.
Sessions 31-35Builder and up - IntegratedG12-P08
Confidence-Gated Smart Room
A smart-room link that acts only on confident, fresh predictions and logs every decision.
Sessions 36-40Builder and up
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.