Eleven templates, four tiers
Every interactive in Maestro is an instance of one of eleven hardened templates, classified into four tiers by what it can prove. Here is the architecture, the tiers, and why the rules cannot be broken.
Template-first, by design
Interactives are never built bespoke per node. A template is a reusable interaction pattern with an editable form schema, built once, QA-tested, accessibility-validated, and approved into the library. An instance is one node's use of it — structured data, not code — filled by the generation pipeline with that node's approved content. A renderer, one per template, turns any valid instance into the learner-facing experience.
Bespoke interactions are slow, untestable, impossible to keep accessible, and ungovernable at scale. With templates, roughly eleven renderers are built and hardened once; content scales through instances without new code. And the template's schema is where the defense stack physically lives: required reasoning and confidence fields, the radical/incidental split, diagnostic bands, and the signal contract are all schema — so a non-compliant instance cannot exist.
The four tiers
P · Presentation
Accordion reveal, tabbed panels, process steps. They present content and produce no evidence — completion only.
B · Practice
Classify & categorize, match pairs, sequence order. Formative only: retryable, immediate feedback, never an official check. Screenshot-solvable — and honest about it.
C · Evidence
Select & justify, compare & decide, misconception confrontation. Structurally force the learner's own explanation — required reasoning, confidence, a not-sure path, diagnostic bands, variant pools.
D · Context-bound
Prior-answer probe, scenario decision pathway. The strongest class: items reference the learner's own history or unfold as a branching scenario no screenshot can capture.
The classification that cannot be talked around
Every template carries an AI-resistance profile: presentation-only, screenshot-solvable, reasoning-required, or context-bound. Only the last two are eligible to carry an official Evidence Check, and the rule is enforced mechanically at three points — the classification lives on the template profile, the generation pipeline can only assign checks to eligible templates, and the validator hard-fails any check riding on an ineligible template. It cannot be published and cannot write to the learner model.
Published course packages carry a compatibility manifest declaring every template version and signal-capture capability they require. If the delivery platform's renderer registry cannot satisfy the manifest, the package does not publish. No silent degradation.
Accessibility is first-class
Every template must be keyboard operable, screen-reader supported, and mobile responsive, with a text equivalent wherever the interaction encodes content. Enhanced media modes are additive — the text-only mode must always be fully functional.