Bounded by what the teacher published.
Teachers see the student view before release, and the tutor declines rather than improvising when the material runs out.
What you are trying to do
Give every classroom a tutor that stays inside the adopted curriculum.
Let a teacher check the student view before a single student sees it.
Keep a clear boundary between what a teacher sees and what a student sees.
What this rests on
- Answers cited back to your own material, with the instructor one tap away when the material does not cover itOn our go/no-go benchmark every answer retrieved the right passage, carried a valid citation and stayed inside the material, and every out-of-scope question routed the learner to the instructor rather than a guess — against 54.2% for handing the model the whole document.
- Interactive STEM visuals — graphs, geometry, circuits, reactions — that the learner can manipulate54 STEM diagrams and 27 interactive ones ship today, and every one is re-drawn and checked before a release.
- Interactive anatomy diagrams with tap-to-reveal labelling for active recallSix anatomy diagrams ship today, each one a labelling task the learner completes rather than a picture to look at.
- Instructors attach their own documents to a course, review them as a draft, and publish when readyFourteen checks driven through a real browser, including that a student cannot see a draft and that publishing opens the document itself.
- Preview exactly what an enrolled student sees before you release anythingThe preview is built from the same rule the database itself enforces, so it cannot drift from what a student actually sees.
- Data export, erasure and guardian consent are implemented and testedExport, erasure and guardian consent each ship today and are driven through a real browser before release.