Glossary

The education and Maestro-specific vocabulary a developer will meet across these topics, defined plainly. Where a term has a home topic, it links there.

Term	Meaning
Adaptive Learning System	The learner-facing runtime (branded Maestro Journey) — the part the dev team builds. →
AGS (Assignment & Grade Services)	The LTI Advantage service Maestro uses to push scores/status to Moodle. →
Behavioural Signal Layer	Interaction-level signals (timing, paste, typing rhythm, AI fingerprint…) fed to diagnosis as supportive evidence, never a verdict. →
Bridge node	A node that helps a learner cross from one learning territory to another — a transition, not remediation.
CLO (Course Learning Outcome)	A statement of what a learner should be able to do by the end of a course. Studio refines the official CLOs. →
Confirming probe	A second item, in a different surface form, that separates a stable misconception from a slip. →
Content Specification (Level 2)	The grounded, per-object academic source-of-truth, with preservation rules and grounding references.
Diagnostic band	The runtime diagnosis category: secure · fragile · knowledge_gap · misconception (plus slip, extended-abstract).
DNA (node DNA)	A node's metadata — KC, mastery statement, type, dependencies, assessment, misconception bindings, risk flags. →
Error type	The diagnosis of a learner's state: secure mastery, slip, fragile, knowledge gap, or misconception.
Evidence Check	The diagnostic that ends a node — captures four signals, emits an error type. Not a grade, not a gate. →
Evidence record	The structured output of an Evidence Check, written to the learner model and consumed by routing.
Grounding	Anchoring generated content to approved reference passages; carries a `grounding_strength`. →
Knowledge Component (KC)	The single concept, skill, or judgment a node targets.
Learner model	The evolving per-learner profile of mastery beliefs, depth, and misconception flags across all KCs — the spine. →
Learning Anchor	Authored, bounded in-journey guidance the Companion operates within — fixed or a runtime handoff template. →
Learning object / block	One ordered piece inside a node (orientation, explanation, practice, evidence check…). The blueprint calls these "blocks."
LLM Council	Multiple AI reviewers examining one object through different lenses, consolidated by a Chairman. →
LTI 1.3 / LTI Advantage	The standard by which Maestro embeds in and syncs with Moodle (Core, NRPS, AGS, Deep Linking). →
Mastery belief	A probability that a learner has mastered a KC, updated as evidence accumulates — not a flag set once.
Mastery Credit	Optional academic-opportunity currency (distinct from grades) earned through enrichment.
Mastery Node	The atomic unit of learning — targets one Knowledge Component. →
Milestone Assessment Pack Contract	The summative-assessment contract: a static pack plus dynamic readiness logic the runtime applies per learner.
Misconception library	The governed catalogue of named wrong models per KC; enables closed-recognition diagnosis. →
Node Experience Blueprint (Level 1)	The design object — object sequence, modality, evidence design, adaptive branches.
Node Learning Package	The produced, validated content the runtime consumes.
NRPS (Names & Role Provisioning Services)	The LTI Advantage service that syncs the Moodle roster into Maestro's own roster.
Practice interactive	A formative in-node activity (sorting, matching, classifying) — retryable, immediate feedback, no grade; never how mastery is decided. →
Published Course Package	The versioned, immutable artifact Studio publishes and the runtime consumes — the core hand-off contract. →
Radicals / incidentals	The fixed, difficulty-bearing elements of an item vs. the variable surface details. The basis of per-learner variation. →
Readiness state	The learner-facing label (Not Ready / Partially Ready / Ready / Advanced) derived from the error type.
Rendering contract / compatibility manifest	Per-template behaviour & accessibility contract; per-package declaration of required template versions and capture capabilities, checked at publish. →
SME (Subject-Matter Expert)	The human academic who governs at defined gates — with distinct authoring (Studio) and delivery roles.
SOLO depth	Depth of understanding: surface → multi-element → relational → extended-abstract.
Subtopic	A learning territory within a CLO — the unit reference grounding anchors to. →
Template / instance / renderer	The reusable interaction pattern + schema / one node's filled use of it / the code that displays it and captures signals. →
Trust layer	The learner model + misconception catalogue + next-step rules — the-code's IP, integrated against. →
Variant pool	The pre-generated, SME-reviewable set of incidental variations of one Evidence Check item (Tiers C & D only). →