Session by session
- Session 56 · Ask & understandWeek 28
Connect text labels to maintenance advice
Evidence: a question, sketch or new vocabulary
- Session 57 · Build & designWeek 29
Define allowed actions and source notes
Evidence: a design draft, dataset or build
- Session 58 · ImplementWeek 29
Use model output to select an operator checklist
Evidence: a working version, explained once
- Session 59 · Test & improveWeek 30
Validate suggestions against the hardware manual
Evidence: a test log with at least one failure
- Session 60 · Explain & reflectWeek 30
Demonstrate refusal for unsafe requests
Evidence: an individual explanation
- P11 classifier
- tracker manual
- local checklist viewer
Ten requests including three unsupported/unsafe ones.
The AI advises a person. It has no control over the hardware.
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.