We read the published research on how people learn from video and turned the findings that survived scrutiny into numeric rules our generator must obey. Here is the whole spec, citations and all, with the things we could not verify clearly marked. It is public because a standard you cannot inspect is not a standard.
Anyone can claim to be built on science. We grade every claim so you can tell a verified effect from a working assumption. The honesty is the credibility.
Survived adversarial verification against a primary source.
An arithmetic consequence of a verified rule.
Practitioner canon or Mayer-principle extrapolation, not verified this round.
A product decision, not a research claim.
A measured property of our own pipeline.
What the science actually says, with effect sizes and a link to the primary source for each.
Content built up stroke by stroke measurably beats showing completed scenes. Retention ηp²=0.13 to 0.17, transfer ηp²=0.10 to 0.16, replicated across two experiments with identical narration.
Hand-drawing vs hand-pushing vs no-hand changed intrinsic motivation (p=0.033) but produced no difference in learning outcomes.
Meta-analysis, 32 studies, N≈3,597: cueing gives retention d=0.27, transfer d=0.34, load d=−0.11. The magnitude of the load reduction predicts the learning gain (β=−0.70 retention, −0.60 transfer).
A segmenting meta-analysis found significant retention and transfer gains, small to medium. Part of the benefit comes from the processing time boundaries create.
Across 6.9 million edX sessions, engagement sits near 1.0 under 6 minutes, drops to about 0.55 at 9 to 12 minutes, and falls to roughly 0.2 past 12 minutes. Independently echoed in a 2026 replication.
About 0.72 vs 0.52 normalized engagement at 3 to 6 minutes, attributed to hand-drawn motion plus an extemporaneous, spoken delivery.
A narrative script improved transfer (ηp²=0.12 to 0.20) but not retention on its own. Paired WITH progressive drawing, narrative beat informative for retention (p=0.021). Over STATIC visuals, an informative script won instead (η²=0.21 to 0.24).
Interesting-but-extraneous content does not improve learning.
Prompts that make the learner summarize or explain improve learning. This is the generative activity principle.
More visual and narrative change points mean less mind-wandering.
Explaining quality does not correlate with views once channel size is controlled (r=0.23, not significant). Only likes, relevant comments, and interactions correlate.
The laws above become concrete targets. This is the contract the generator is checked against on every render.
| Parameter | Target | Grade |
|---|---|---|
| Total video length | 6:00 hard ceiling; 1:00 to 3:00 sweet spot per concept | VERIFIED |
| Length granularity | 30-second increments | PRODUCT |
| Scene duration | 12 to 30 seconds, one idea per scene | VERIFIED |
| Elements per scene | 3 to 7 visible at scene end, heading included | HEURISTIC |
| Reveal cadence | a new element every 2 to 5 seconds; no two reveals closer than 1.2s | DERIVED |
| Reveal-to-word sync | element appears within ±500ms of its trigger word | DERIVED |
| Word-sync coverage | at least 95% of elements carry a reveal word that resolves | PIPELINE |
| Post-scene gap | at least 0.7s of narration silence after the final reveal, before the cut | VERIFIED |
| Reveal style | outline draw-on (0.3 to 0.5s), then a staggered fill wash; arrows tip to tail | VERIFIED |
| Visible hand | none | VERIFIED |
| Labels | three words or fewer, all-caps keyword; never a sentence that mirrors narration | HEURISTIC |
| Narration pace | 140 to 160 words per minute, spoken register, contractions allowed | HEURISTIC |
| Script structure | hook within 10s, concrete analogy, mechanism, real-world anchor, retrieval beat, recap | VERIFIED |
| Narrative grammar | actor, goal, obstacle, resolution, whenever the domain allows | VERIFIED |
| Analogy | at least one concrete analogy before the first abstract term | HEURISTIC |
| Extraneous visuals | zero elements unreferenced by narration | VERIFIED |
| Ending | retrieval question, a pause of at least 1.5s, then a one-line recap | VERIFIED |
| Scene transitions | hard cut at an idea boundary only, never mid-idea | VERIFIED |
Every row is an assertion in the engine, not a guideline. A render that misses one is sent back before it becomes a video.
A rule is only real if you can test it. Every video runs through three layers before it is allowed to ship.
Plain JavaScript assertions on the scene graph and the word timings. Zero cost, safe to run in CI. Total duration under the ceiling, every scene in its duration band, 3 to 7 elements per scene, every element carries a reveal word that lands within ±500ms of the spoken word, a final scene with a question and a recap, and no element unreferenced by narration. Pass or fail, no model calls.
A model-as-judge pass, scored 1 to 5, sampled and run on release, never in CI. One idea per scene, icon fidelity, whether the analogy actually maps to the mechanism, hook quality, a seductive-detail scan, and faithfulness to the source document. Any dimension below 3 fails the release gate.
Checks on the rendered file itself. A contact sheet confirms no overlapping elements and legible labels, a frame burst confirms the outline-then-fill reveal is actually present, and the audio is loudness-normalized with no clipped sentences at the cuts.
The spec is only worth anything if a video that breaks it cannot ship. Layer A runs at generation time, on the scene graph, before we spend a cent on voice or rendering. A graph that fails the mechanical checks is sent back to be regenerated with the exact failures fed into the prompt. A graph that keeps failing never becomes a video.
Every check in the list above maps to a real assertion in our engine: the total-duration ceiling, the per-scene duration band, the element count, the reveal-word resolution rate, the post-scene silence, the label rules, and the question-plus-recap ending. Arrows are checked too, so a pointer never crosses an element it is not connected to. The same code runs in the worker’s regeneration gate and in continuous integration, so a change to the generator that would regress quality blocks itself.
Type it, and a narrated whiteboard explainer draws itself. Every scene stays editable.
Get Started