MaestroMaestro Overview — contents
The Build
Timeline & Roadmap
What was delivered between August and early October 2026, grouped by theme and roughly by month, and what comes next. This page records what the product's own history shows; it does not carry forward dates the build no longer supports.
August laid the foundations: the shared design language, Course Design and Moodle over LTI 1.3. September brought the Lead Designer and the Lesson Page Standard, the Atlas companion, roles with Dean release, and the assessment experience. Early October joined it up for learners — remediation pieces, Revision, Welcome back, the course road and the spoken defense over live voice — and began removing the old Classic engine.
Delivered, August to October 2026
| Period | What landed |
|---|---|
| August 2026 · Foundations | One design language across Studio and Journey; the Course Design reviews (Course Intake through Topic Architecture) made robust, with faculty approval at each step; Moodle integration over LTI 1.3 Advantage — identity, roster, single sign-on and grade routing; Journey's road grouped by learning outcome; the first Today and guidance flows. |
| September 2026 · One engine, one lesson | Training courses alongside academic courses; Atlas rebuilt so code rules decide when it speaks and the model only words the line, with Atlas made learner-only; the Lead Designer — lesson calendar, division of sources across subtopics, "Fill this gap", produce lesson / subtopic / course, the production monitor; the Lesson Page Standard and the Storyline; tempting errors joining the shared misconception registry; a hosted staging environment with Moodle over LTI; roles, schools and programmes, the Registration desk, the Release board and Dean release; the assessment experience — choose your world, the build, My results. |
| Early October 2026 · The learner's path, end to end | The spoken defense over live voice (WebRTC), where the learner can cut in; every milestone entered through its Milestone Guide; remediation pieces produced for every lesson (mix-up message, worked example, Look again alongside the second way in and firm-up), with publishing refusing incomplete lessons; the moment after a check with five learner results; the Revision page and hub, "Before Milestone" and the Welcome back look-back; the course page with the course road and Your results; a course cannot be signed until its milestones are approved; Classic removal phases 0–2 (no new Classic courses, Classic authoring out of Studio and the backend). |
What comes next
| Work | Status |
|---|---|
| Classic removal, phase 3 — retire the Classic courses and their data, rebuild the affected courses on the Lead Designer, then remove Classic delivery from Journey | In progress |
| Classic removal, phase 4 — separate the pieces still shared with the current engine (for example the realtime voice code used by the spoken defense and Atlas) | Next |
| Classic removal, phase 5 — remove the engine switch once no environment holds a Classic course | Next |
| Assessment resubmission (phase 2) | Parked |
| Stretch work for secure learners | Parked |
Earlier editions of this page carried a month-by-month Phase 1 plan with fixed review and launch dates. The product record no longer supports those commitments, so they have been removed rather than restated. Each Classic removal phase is sequenced to leave the system working on its own, and none is tied to a calendar date. See Status for what is live today and Open Questions for decisions still to be made.