Session by session
- Session 66 · Ask & understandWeek 33
Integration risks and test order
Evidence: a question, sketch or new vocabulary
- Session 67 · Build & designWeek 34
Integrate one subsystem at a time
Evidence: a design draft, dataset or build
- Session 68 · ImplementWeek 34
Commit every change with a clear message
Evidence: a working version, explained once
- Session 69 · Test & improveWeek 35
Run the full acceptance suite twice
Evidence: a test log with at least one failure
- Session 70 · Explain & reflectWeek 35
Report what passed, failed and was fixed
Evidence: an individual explanation
- Capstone build
- test log
- Git
The full acceptance suite run twice; a repeat run catches regressions.
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
- RoboticsG12-P13
Capstone Specification and Build
A written specification with acceptance tests, and capstone hardware built to match it.
Sessions 61-65Innovation only - RoboticsG12-P14
Integration and Acceptance Testing
An integrated build that passes its own acceptance tests, with every failure fixed or recorded.
Sessions 66-70Innovation only - AIG12-P15
Independent Model Audit
A peer-audited model card covering data, metrics, limits, privacy and misuse.
Sessions 71-75Innovation only - IntegratedG12-P16
Sound-Aware Smart Room Capstone
A defended smart-room system with a safety case, reproducible evidence and an honest limits statement.
Sessions 76-80Innovation 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.