MaestroMaestro Overview — contents
The Build
Integration — Moodle & LTI
How students reach the system for January: Moodle via LTI 1.3 with LTI Advantage. This topic covers the four LTI areas, grade pass-back, enrolment and onboarding, and the strict export boundary that keeps diagnostic data inside Maestro.
For the January cohort, integration is Moodle via LTI 1.3 with LTI Advantage. LTI covers four areas: sign-in/launch, roster sync (NRPS), grade pass-back (AGS), and learner-state exchange. Only high-level status and score leave toward the LMS — detailed learner reasoning and misconception data stay inside Maestro. Maestro holds its own roster and gradebook as a system of record; LTI keeps them in sync.
LTI 1.3 — the four areas
| Area | What it does |
|---|---|
| 1 · Sign-in & course launch (LTI 1.3 Core) | OIDC-based SSO from Moodle into the Adaptive Learning System — no separate Maestro login. The launch delivers standard identity, role, and context claims plus custom parameters binding the launch to a specific course-package version and cohort. Deep Linking 2.0 lets an instructor place a Maestro course or a specific milestone into a Moodle course as an LTI activity. |
| 2 · Roster & role sync (NRPS) | Maestro pulls the Moodle course roster and populates its own accounts and roles table. Maestro holds its own roster as a system of record from day one; NRPS is the January mechanism to keep it in sync. Ongoing sync must handle adds, drops, and role changes. |
| 3 · Grade pass-back (AGS) | Scores flow to Moodle via Assignment and Grade Services. See below. |
| 4 · Learner-state exchange | From Moodle at launch: identity, role, course context, cohort. From Maestro asynchronously via AGS: completion status, milestone readiness, milestone submission status, and final scores. Sessions are scoped to the LTI launch and refresh on re-launch, not through a persistent Maestro-side login. |
Grade pass-back (AGS)
Two categories of line items go to Moodle:
| Line item | What it carries |
|---|---|
| Summative milestone line items | One per summative assessment (A1–A4 for MDLD602), each bound to the milestone's stable LMS binding key. Scores are pushed when the SME finalises the grade in Maestro. |
| Course activity line item | A single aggregate score reflecting the learner's engagement and progress (node completion, evidence-check performance, formative practice, and other participation signals as configured). Lets Moodle hold the overall course grade as a weighted combination, with weighting decided by the SME or institution at course setup. |
Enrolment & onboarding
Enrolment runs entirely through the university's existing systems. Students are enrolled in their Moodle course through the standard registration process — Banner/SIS pushes the enrolment to Moodle — with no direct enrolment path into Maestro. On the Moodle course page the student finds a link to their Maestro course (an LTI activity placed by the instructor via Deep Linking); clicking it launches Maestro via LTI 1.3, SSO happens automatically, and NRPS syncs the roster so Maestro has the student's identity, role, and cohort.
Release-one onboarding inside Maestro is minimal: on first entry the student lands on their course dashboard, the Companion introduces itself and orients them, and they start the first node. No separate account creation, no context profile, no baseline diagnostic — richer onboarding (context profiles feeding assessment personalisation, prior-knowledge diagnostics seeding the learner model) is recognised but deferred.
The export & privacy boundary
Two boundaries are worth being explicit about, because they get confused often:
- Content authoring never flows through Moodle. Studio publishes to the Adaptive Learning System directly; Moodle is not involved in the authoring hand-off.
- Maestro is the source of truth for grades internally. Moodle receives the export via AGS; it does not compute grades from Maestro data.
Only completion, score, and readiness leave toward the LMS. Learner reasoning, misconception flags, confidence signals, and process signals stay inside the adaptive system unless the institution explicitly authorises otherwise. Build to this boundary from the start — it is a design constraint, not a later privacy retrofit.
Release one targets desktop and tablet (phone later) and is English first, Arabic later. No formal accessibility conformance target is set for release one, though good accessibility practice applies. These were confirmed as the current direction; see Open Questions.