The library behind the platform.
Everything we claim on the marketing pages is explained in full here: concise concept explainers for anyone evaluating the approach, and illustrated deep dives for the people who want to see the machinery.
Everything your IT team needs before go-live.
Architecture, minimum requirements, preparation checklists, and operations — written for infrastructure, database, network, and security teams.
The Maestro Overview.
The shared reference for Maestro — the concept and the build. Seventeen chapters and a reference section covering the vision, Studio, mastery, adaptivity, integrity, the course-package hand-off, integration, signals, architecture, and the roadmap.
How Maestro works and why — vision, ecosystem, Studio, mastery, adaptivity, integrity, and the Companion.
8 chaptersThe BuildThe developer contract — scope, the course package, the runtime, integration, roles, signals, and the timeline.
9 chaptersReferenceOpen questions, the glossary of every education and Maestro term, and design-versus-runtime status.
3 chaptersThe concepts, written for anyone.
One knowledge component at a time
Every course is a graph of nodes, each teaching exactly one thing.
ReadEvidence ChecksTrustworthy evidence of what a learner knows
A diagnostic at each node exit — response, reasoning, confidence, and process.
ReadMilestones & spoken defenseGraded work, defended aloud
Every graded assessment ends with the learner talking through their own work.
ReadAcademic integrityThe seven-layer defense stack
Designed so real mastery is the only thing cheaper to have than to fake.
ReadHonesty economicsHonesty is the cheapest path
In learning activities, being wrong is free and instructive — so cheating has no economic logic.
ReadAtlasA companion that knows when to stay quiet
The learner's AI companion: one calm line at the right moment, and help when it is asked for.
ReadThe machinery, in full.
Eight illustrated essays that open the hood — the defense stack, the evidence engine, the authoring pipeline.
The seven-layer defense stack
Seven reinforcing layers that make honest evidence the rational choice — without surveillance.
IIInside an Evidence Check
Four signals, five diagnoses, a coach's readout — and why it is never a quiz.
IIIHow a course is engineered
Re-engineered, never digitised: six ordered reviews, one Lead Designer, a signature and a release.
IVMastery is a belief, not a checkbox
How the learner model decides it truly believes you know something — and why one result never settles it.
VThe misconception library
Wrong models are catalogued, bound to lessons, and confronted by design — not discovered by accident.
VIVariant pools: why answers don't travel
Radicals stay locked, incidentals vary — so no answer bank can ever form.
VIIMastery makes the grade
Practice, Evidence Checks, and milestones — three kinds of assessment, one one-way law.
Developer documentation.
See the concepts working on a live course.
Book a walkthrough and we'll show every mechanism in this library operating on real evidence.