Session by session
- Session 56 · Ask & understandWeek 28
Design read-only tools and a command schema
Evidence: a question, sketch or new vocabulary
- Session 57 · Build & designWeek 29
Connect triage labels to approved troubleshooting cards
Evidence: a design draft, dataset or build
- Session 58 · ImplementWeek 29
Keep drive actions unavailable
Evidence: a working version, explained once
- Session 59 · Test & improveWeek 30
Test adversarial or irrelevant input
Evidence: a test log with at least one failure
- Session 60 · Explain & reflectWeek 30
Document permissions and refusals
Evidence: an individual explanation
- P11 model
- local manual
- simulated tool API
Ten valid and five rejected requests; no hardware writes.
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
- 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.