Scope of Collaboration

What release one covers, what sits outside it, and the architectural instruction that shapes it: Maestro is a real system of record from day one, with LTI in front of it — not a pass-through shim behind the university's existing systems.

The 30-second version

In scope: the whole path from syllabus to graded learner — Studio (Course Design and the Lead Designer), the Dean's release, Maestro Journey for learners, milestones with a spoken defense, Atlas, the six roles, and LTI 1.3 with Moodle. Later: the fuller academic-intelligence and refinement loops, pathway recommendation and the support marketplace. Integration is LTI-embedded, but Maestro keeps its own accounts, roles, enrolment and grades as a system of record from day one.

In scope — release one

Release one is one product with one authoring path and one learner experience. It covers:

Course Design in Studio — six ordered reviews (Course Intake, Learning Outcome Review, Assessment Design, Rubric and Weighting, Academic Integrity, Topic Architecture), each approved by faculty. See Studio · Course Engineering.
The Lead Designer — the only course engine. It plans, designs and produces every lesson to one Lesson Page Standard, with the remediation pieces each lesson needs. See the Lead Designer chapter.
Sign and release — the course owner signs the final report, and the Dean (or IT Admin) releases a frozen version. There is no direct publish. See the released course version.
Maestro Journey — Today, the course road, lessons and their checks, results with learner-chosen next steps, and Revision. See The Adaptive Learning System.
Milestones — graded assessments entered through a Milestone Guide, built over time and closed with a live spoken defense, then reported against the course's rubric weights.
Atlas, the learner-only AI companion.
Roles and staff surfaces — six roles, schools and programmes, course staff, academic dashboards and the Registration desk. See Standard LMS & Roles.
LTI 1.3 with Moodle — whole-course deep linking, sign-in, roster sync and one grade column per milestone. See Integration.

Studio offers two kinds of course: a new academic course, led by the syllabus through Course Design, and a new training course, led by the source material. Both are produced by the Lead Designer and released the same way.

Out of scope & retired

The earlier Classic course engine — node types, template tiers, experience blueprints, content specifications and modality production screens — has been retired. Nothing in release one depends on it, and new work should not reintroduce its vocabulary. Content authoring never flows through Moodle: Studio releases straight to Journey.

Later stages

Some parts of the wider ecosystem are deliberately not release-one work. Release one ships the foundational academic-intelligence layer — staff dashboards over enrolment, progress and workload. The fuller Academic Intelligence (Maestro Pulse) and Refinement loop (Maestro Compass, feeding evidence back into new course versions) mature in later phases, as do the pathway recommendation engine and the Academic Support Marketplace. See Timeline & Roadmap.

LTI now, system of record from day one

Learners reach Maestro through the LMS, not as a separate platform they log into. LTI minimises disruption to the university's existing ecosystem — the course catalogue, student identification, registration and the gradebook. For a live cohort, disturbing any of those layers is not an option, so LTI is the right integration surface for release one.

The consequential architectural instruction

The longer-term intent is that the university progressively bases its ecosystem on Maestro itself. So Maestro is built as a genuine system of record — with its own accounts, roles, schools, enrolment and grade records — with LTI sitting in front of it as the launch and sync mechanism. A launch provisions or updates a Maestro account; roster sync keeps enrolment current; grades are computed in Maestro and sent out. A shim would borrow identity per session and treat another system as the source of truth; Maestro holds its own primitives and uses LTI to populate and sync them.

For engineers — the export boundary is a design constraint

Only milestone scores leave Maestro toward the LMS, one AGS column per approved milestone. Lesson results, learners' answers, mix-ups and Atlas conversations stay inside Maestro regardless of integration depth. See Integration and Learning Signals.

Humans govern every gate

Release one keeps one rule at every hand-off: AI accelerates, people decide. Faculty approve each Course Design review; reviewers comment on lessons; the course owner signs; the Dean releases. Every model is chosen from a catalogue in Admin Center and every prompt runs from an approved version in the prompt registry — see Architecture & the Trust Layer. The work continues iteratively: start from the flows that run a live course end to end, and widen from there.