Teacher / Manager Login
Passwords and API keys stay in your separate Cloudflare Worker. Pages only hosts this index.html.
v0.6.0 flow: Prompt first, then select exact Port 1–4 sensors and A–D motors before AI. These port objects are sent as important specs. AI must only use selected/uploaded hardware and defaults. Work mode is individual by default.
Prompt-first Lesson Generation minimal input
How it works: enter a short prompt, upload EV3G notes/photo if available, and preferably upload EV3-G programming screenshots. Click Analyse + Lock Specs. AI will generate only from selected specs, selected sensors/motors, uploaded evidence, and CSA defaults. Programming screenshots are attached directly to the Programming Phase to reduce EV3G translation errors. It will not invent pair work or extra hardware. If AI returns 401, login again because the Worker session token has expired or was cleared after deployment.
Spec/evidence analysis will appear here.
Defaults Apply, But Can Be Changed override enabled
Leave fields as default for fastest generation. Change any field only when the project needs a different duration, port, motor, sensor, or work mode. AI is not allowed to add unselected hardware.
Class Organisation + AI Guardrails
Default lock: individual work. No pair work, no team roles, and no extra motors/sensors unless selected below or written in the prompt/EV3G notes.
Confirmed Hardware / Components
Time & Lesson Flow
Golden template lock: Build Phase must stay as one 20-25 min section. Do not split it into Checkpoint 1/2/3 with separate timings. Programming may show steps, but main timing remains one Programming Phase.
Strict output rule: AI may list teacher checkpoints as bullets inside Build Phase, but no timed subheadings such as “Checkpoint 1 — 5 mins”. If detected, the app will clean the output before display.
EV3 Port Defaults / Overrides
Port selection lock: Select what is plugged into each EV3 input/output port. These selected objects are sent to AI as important specs. Default is Not used. Uploaded EV3G program files should override photos when exact ports conflict. Staff may still override here.
Input Ports 1–4: Sensors
Output Ports A–D: Motors
Uploads + Generated Plan Memory optional
Cover image policy: Image generation is not automatic. Upload a final robot photo if you want a visual reference. Later, manager-only cover image generation should be explicit, cached once per approved plan, and limited to about 1–4 images/week.
Evidence parser: EV3G / EV3P / ZIP uploads are now scanned for readable project files and likely sensor/motor port evidence before AI generation. Photos are sent to vision-capable providers as mechanism reference, but they do not override selected ports or EV3G/code.
Use this for readable notes/evidence. Exact EV3G translation may be unreliable if file is binary.
Optional cover/mechanism reference. It does not override selected ports/programming.
Recommended for EV3-G: upload screenshots of the actual EV3-G blocks. The lesson will attach these screenshots in the Programming Phase instead of asking AI to guess/translate every EV3G block.
Final Robot Photo Preview
Programming Screenshot Preview
Memory Reference
Auto-selected STEM Concepts editable
Auto-selected from prompt/specs/uploads. Teachers may still tick or untick. AI must follow these selected concepts and not add unrelated ones.