How a course is engineered
Maestro doesn't digitise your course — it re-engineers it from its academic foundations. Here is the full path: Course Design, the Lead Designer, the owner's signature, and the Dean's release, with human gates throughout.
Re-engineering, not digitising
Most courses are built for a teacher in a room — weeks, lectures, readings, a final exam. Turning week one into module one only digitises the old shape. Maestro rebuilds the course from its academic foundations: refined outcomes, authentic assessment, and mastery you can actually verify. The weekly plan becomes scope evidence, not the structure.
Studio has one path from syllabus to live course. Course Design settles the “what” — outcomes, assessment, weighting, integrity and the shape of the course — through a fixed sequence of faculty-approved reviews. The Lead Designer then does the “how”: it plans, designs and produces every lesson from your own sources. Only when the owner signs and the Dean releases does a learner see any of it.
Course Design: six ordered reviews
Each review is approved by faculty before the next opens — so every lesson traces back to a real, refined outcome and an assessment designed before any content exists.
- Course Intake. The syllabus and sources come in, and the course's scope is set.
- Learning Outcome Review. Outcomes are refined into diagnosable targets, not vague aspirations.
- Assessment Design. Milestones are designed as authentic work, before content exists.
- Rubric and Weighting. Criteria and their percentage weights are fixed — the same weights the milestone report and the gradebook use.
- Academic Integrity. The integrity model is settled at design time — it is architecture, not an afterthought.
- Topic Architecture. The course is mapped into topics and subtopics, ready for the Lead Designer.
The Lead Designer: plan, design, produce
One course engine does the production work, and you can watch it happen — a production monitor shows each course being planned, designed and produced live.
- Plan. Your sources are divided across the subtopics and the lesson calendar is set. Where sources are thin, “Fill this gap” lets AI write the missing material — which is reviewed like everything else.
- Design. Every lesson follows one Lesson Page Standard: an opening case and a choice, parts that can be watched or read, “Try it” and pause moments, the lesson's check, a close, and what to carry forward — tied together by a storyline, and built phone-first.
- Produce. Produce one lesson, a subtopic, or the whole course. Each lesson also gets its remediation pieces — a mix-up message, a second way in, a firm-up prompt, a worked example, and Look again — and publishing refuses a lesson missing any of them.
From signed to live
- The owner signs. The course owner signs the final validation report. A course cannot be signed until its milestones exist and are approved.
- The Dean releases. The Dean releases the signed, frozen version, and it becomes live and unchangeable for learners. There is no direct publish; a rollback can only return to an earlier released version.
AI generates. Humans govern.
Nothing reaches a learner unreviewed. Faculty approve each Course Design review, review what the Lead Designer produces, and sign the result; the Dean decides when it goes live. Every model is chosen by the institution and every prompt is versioned and approved. The human never authors on the machine's behalf; your standards and your voice remain faculty decisions throughout.