The Concept

The Ecosystem at a Glance

A map of the whole ecosystem before the deep topics — the four branded parts, the roles that run them, how a course reaches learners, and what is deliberately later-stage. Maestro was designed not only as a learner platform but as a governed academic ecosystem.

The four parts

Each part has a branded name and a plain functional name. This documentation leads with the branded name and gives the functional name in parentheses on first mention.

Part	What it is	In one line
Maestro Studio (authoring)	Where faculty make a course.	Course Design runs six ordered reviews from syllabus to topic architecture; the Lead Designer plans, designs and produces every lesson from the course's sources. →
Maestro Journey (learner delivery)	Where learners take it.	Today, the course road, lessons, Revision, results in five plain words, milestones with a spoken defense, and Atlas. →
Maestro Pulse (cohort insight)	Academic dashboards for staff.	Who is active, how mastery is moving, mix-ups several learners share, and the interventions staff open on them.
Maestro Compass (curriculum governance)	The governance layer.	The audit trail, the misconception registry, and improvement suggestions back to faculty — learner history preserved across every change.

Journey, in brief

A learner lands on Today, which says where to start. Each course has four tabs: Your journey, Lessons, Revision and Your results.

Piece	What the learner meets
The course road	One lane per learning outcome, a stop per topic (solid, firming up, you're here, ahead), Revision markers, milestone diamonds, and the credential at the end. Minutes are shown on every lesson.
Lessons and results	Every lesson ends in a check. The result is one of five plain words — Solid · Nearly there · Not yet · Not sure · A mix-up — followed by options the learner chooses from.
Revision	One page per course and a hub across courses. Each item says which lesson it came from; "Short on time?" offers 5 minutes, 10 minutes or everything.
Milestones	Entered through a Milestone Guide. The learner chooses a world, builds the work, then defends it in a live spoken conversation. A weighted report follows.
Atlas	The learner-only AI companion. Rules in code decide when it speaks; it stays quiet while a check is open and inside assessments. Full topic →

Roles and release

Six roles, one per person: IT Admin, Academic Lead, Dean, SME, Registration and Student. Courses belong to schools; a school's Dean manages its courses. On each course, staff are the owner, co-authors (who edit) and reviewers (who comment). The Registration desk follows up cases and learner messages for the programmes assigned to it.

There is no direct publish. The owner signs the final report, which submits the course to the Dean; the Dean (or IT Admin) releases the signed version, which becomes live and immutable. A rollback can only go back to an earlier released version. Roles are covered in Standard LMS & Roles; Moodle in Integration.

What's later-stage

The vision is wider than what ships today, and it is built in phases — a testable, iterative approach, not the whole future at once. Two components in the original vision remain later-stage:

Component	The intent
Recommendation Platform Later stage	Helping learners discover and design a pathway across certificates and degrees, governed by the university's credential rules. →
Academic Support Marketplace Later stage	Governed access to human academic support — approved professors, tutors and mentors — with the university managing quality. →