MaestroMaestro Overview — contents
The Build
The Adaptive Learning System
What the learner runtime, Maestro Journey, does with a released course: where each day starts, the course page and its road, what happens after every lesson's check, Revision and "Welcome back", the way into milestones, and Atlas alongside it all.
Journey runs the course version the Dean released, frozen and unchanged. Every screen is composed on the server: the client lays out what it is sent and derives no states, placements or counts of its own. A learner starts on Your day, opens a course on four tabs (Your journey · Lessons · Revision · Your results), takes a short check at the end of each lesson, sees one of five results in plain words, and chooses where to go next. Milestones are always entered through their Milestone Guide. The litmus test still holds: anything that exists because a specific learner is interacting is Journey's job.
Your day
The learner's home page (Today, titled "Your day") answers one question: where should I start? The server composes it in a single payload: a greeting, a short orientation line from Atlas, the next step with a Continue button and the reason for it, the learner's courses (each with a compressed view of its road), and anything waiting. Two additions support Revision:
- A revision line from Atlas, shown only when three or more items are waiting in a course or that course's milestone is open or next. It names the course, how many short items wait and roughly how long they take, with one link: "Start now". There is no dismiss button; ignoring it is fine.
- "Short on time?": 5 or 10 minutes of short look-backs instead of a new lesson. Hidden when nothing is waiting.
Learners arriving from the institution's LMS land here too (see Integration — Moodle & LTI).
The course page
Each course page has a header with Up next (the next lesson and its minutes) and four tabs:
| Tab | What it shows |
|---|---|
| Your journey | The course road (below). |
| Lessons | Every topic and lesson, with lessons ahead greyed and still locked. Each lesson shows the minutes Studio set for it ("15–20 min"). Each outcome ends with its milestone row: weight, title, readiness line, Guide, and Revision · N when items are required. Filters: All / To do / Firming up. |
| Revision | The course's Revision page, with a count on the tab. |
| Your results | The learner's milestone results for this course, with a link to results across all courses. |
Inside a lesson, a sidebar carries the same list (every topic expandable, minutes, milestone rows, "Revision · N"). On a phone it opens as a drawer from a "Lessons · 5 of 12" button.
The course road
The Your journey tab draws the course as a road. Its data is one course map payload, composed on the server from the released version and the learner's progress:
- One lane per learning outcome, alternating direction, with the outcome's title centred above it and its progress ("4 of 18").
- One stop per subtopic. Its ring fills as lessons are done; its state is shown in learner words: solid, firming up (with a small count), you're here, or ahead. Under it: the name and "2 of 3 lessons".
- Revision markers: the number of items waiting before the next milestone. A marker opens the course's Revision page.
- Milestone diamonds, placed where each milestone opens in the learning order: "Milestone 1 · 50%" and its status (ahead, open, in progress, passed with its mark).
- The road runs from start to your credential, which fills one socket per milestone passed.
Selecting a stop opens its detail under the road: for a subtopic, its lessons with full names, minutes and state, and Continue: lesson N; for a milestone, the outcomes it covers, its readiness line and its weight, with every button going through the Milestone Guide. On phones the road runs top to bottom.
Placement (which subtopic a milestone follows), the outcomes it covers, its weight, lesson numbers, minutes, Revision counts and credential sockets all arrive in the payload, validated by a shared contract. The client draws; it never works out a state. The same layout rules drive Studio's map of the course, so authors and learners see the same shape.
After a lesson's check
Each lesson ends with a short check. The learner then sees one result in plain words, Solid · Nearly there · Not yet · Not sure · A mix-up, with a short headline, the message for that result, and their own answer "kept for you". Below it, Where to next · you choose offers up to four options, one marked Recommended: continue, firm it up with one example, see it another way, walk through a worked example, rewatch the part, practise again, or show your thinking with a fresh question. Which options appear is decided by fixed routing rules, not by the AI. After "A mix-up", the next lesson opens once the learner has tried any one option; passing it is not required.
The rules behind each result and option are in Adaptivity & Routing; the signals behind the result are in Learning Signals.
Revision and Welcome back
Revision is one page per course, open any time, plus a Revision hub in the main menu listing the learner's courses. Every item says where it came from ("From lesson 3 · … · open the lesson"). Items are short: look again at your own earlier answer, try the lesson's check, give one example, or answer a fresh question. "Short on time?" picks what fits in 5 minutes, 10 minutes or everything: required items first, then mix-ups, then the oldest. When a milestone is open or next, its required items show first as "Before Milestone N"; each needs one honest try before the assessment starts, and passing is not needed.
"Welcome back" appears before the first lesson of a new day when an item is due: one item, about a minute, never marked. Any honest answer moves the learner on. It only holds back starting the next lesson (the server refuses that start until it is done); the course page, the guide, results and Revision are never blocked.
Milestones
Graded assessment happens at milestones, and every milestone is entered through its Milestone Guide: the criteria with their weights and the outcomes covered. The guide can be read from any point in the course. Its main button follows the learner's progress: disabled with the reason while the milestone is ahead ("Opens after Topic 4"), then Start assessment, Continue your assessment, or Continue your defense. The learner chooses a context for the brief, builds the work with autosave and version history, submits it (the work is then locked but readable) and gives a short spoken defense. The weighted report then appears under Your results. The detail is in Mastery & the Lesson's Check and Academic Integrity.
Lesson checks and milestones are separate systems. A lesson check produces a diagnosis that updates the learner model and drives routing; it carries no mark. A milestone produces a graded piece of work, a defense transcript and a weighted report. Do not merge them into one "assessment engine".
Atlas
Atlas is the learner's AI companion, present across Journey. Code rules decide when it speaks; the AI only words the line. It is grounded in the learner's own course data, offers a help ladder in chat, and stays quiet while a check is open and inside assessments. The full design is in The AI Companion.
Later, not in the current build
Earlier plans placed a pathway recommendation engine and an academic support marketplace (governed, paid sessions with human tutors) inside Journey. Neither is part of the current product. They remain ideas for a later phase and should not be described as live.