Skip to content
Maestro.
MaestroMaestro Overview — contents
Developer Documentation

Maestro

The AI-native academic learning platform — the concept, and the build

Read this first

This is the shared reference for Maestro — written so a developer who has never worked in education can build against it. It's organised as topics you can read in order or jump between. The Concept explains how Maestro works and why; The Build is the developer contract — scope, the course-package hand-off, integration, roles, signals, and the timeline. The sidebar is the map.

How to read it

Layered on purpose. Plain-terms lines carry the whole idea; tables are for scanning; the dark “For engineers” call-outs hold the field-level contract. If a term is unfamiliar (it's an education term, not a coding one), it's in the Glossary. Every point raised in the development brief is mapped to a topic below.

The Concept

01
Vision & Positioning
What Maestro is, why it isn't an LMS, and how it treats adaptivity.
02
The Ecosystem at a Glance
The four pillars, the supporting components, and what's later-stage.
03
Studio · Course Engineering
The authoring tool: outcomes, integrity, grounding, subtopics, nodes.
04
Studio · The Nodes Engine
Nodes, blueprints, node types, modality, the five production steps.
05
Mastery & the Knowledge Check
The Evidence Check, the structured diagnosis, and the learner model.
06
Adaptivity & Routing
The concrete adaptive mechanisms that decide the next step.
07
Academic Integrity
Integrity by design, gaming resistance, the Behavioural Signal Layer.
08
The AI Companion
The bounded reflective partner in the live layer.

The Build

09
Scope of Collaboration
In / out of scope, LTI now, and system-of-record from day one.
10
The Published Course Package
The hand-off contract — ten contents, delivery, open items.
11
The Adaptive Learning System
What to build: rendering, delivery, Evidence Checks, grading.
12
Integration — Moodle & LTI
LTI 1.3, NRPS, AGS, enrolment, and the export boundary.
13
Standard LMS & Roles
The LMS foundations, must-haves, and the delivery-side roles.
14
Learning Signals
The full signal inventory and the same-shape principle.
15
Interactives & the Evidence System
The defense stack, template-first architecture, tier library, design laws.
16
Architecture & the Trust Layer
Model layer vs. trust layer, ownership, and no runtime dials.
17
Timeline & Roadmap
Phase 1 month by month, anchor dates, and dependencies.

Reference

Ref
Open Questions
The four decisions still open from the brief.
Ref
Glossary
Every education and Maestro term in one place.
Ref
Status: Design vs Runtime
What the design defines vs. what release one implements.
Status

Skeleton draft. The structure and navigation are in place and every topic from the development brief is mapped. Sections are being written in agreed order (the Studio walkthrough first). Each unwritten section shows a dashed “To be written” block listing exactly what it will cover — so this doubles as a coverage checklist.