Gateway courses, held by the material you already teach.
Instructors publish once. Every enrolled student gets a tutor bounded by that material, and the roster shows who has produced no evidence yet.
What you are trying to do
Support high-enrolment gateway sections without hiring proportional tutoring staff.
Give adjuncts a tutor that cannot contradict the course material.
See which concepts a section is stuck on while the term is still running.
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.
- 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.
- See which learners are struggling and which concepts they are stuck onTwenty-nine automated checks on the cohort report, plus five more driven through a real browser.
- Load a roster by CSV, join code or verified email domain, and re-run it safelyFifty-five checks against a live environment, including that importing the same roster twice creates no duplicate students. LTI 1.3 and SCIM ride the same seam and become live under a signed pilot.
- 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.
- Each institution’s data is isolated at the database level, not by application codeTen checks run as a real signed-in user, so the database’s own access rules are genuinely exercised rather than assumed.