Skip to content

use case

verified July 2026

The course that can afford to be updated.

Course content goes stale on a schedule nobody controls — a regulation changes, a product ships, a statistic is a year old. On a meter, re-narrating the affected modules has a price tag, so it waits for the annual refresh and the audio quietly drifts out of date.

01

Why update cost decides curriculum quality

The cost of changing a course is what determines how current it is. When a module costs money to re-voice, the rational move is to batch changes and ship them once a year; when it costs nothing, you fix the sentence the week it becomes wrong.

The same arithmetic applies across a catalogue. Localising every module into six languages is priced by total characters on a meter, so the long tail of less-popular courses never gets translated at all.

The module goes out of date

Film

When re-narrating costs nothing per character, a correction ships the week the content changed rather than at the annual release.

02

What the engine gives a course

  • One cloned instructor voice across 23 languages, so the same person teaches every localised edition.
  • Spell tags for codes, formulas and acronyms — read character by character rather than mangled into a word.
  • Break tags to hold a beat where a slide changes, so the audio and the deck stay in step.
  • Reproducible seeds, so re-rendering one corrected sentence does not shift the rest of the module.

03

Notes — an engineer's checklist

01Can one instructor voice cover every language we publish in?

Yes. One reference clip carries the identity across 23 languages, so the localised editions keep the instructor rather than replacing them per market. Eight languages carry published, dated specimens at /languages/.

02How do we handle acronyms and formulas?

Wrap them in a spell tag and they are read character by character with letter and digit groups paced naturally; a pronunciation dictionary handles domain terms that should sound a specific way.

See also — related sheets

A key and one seat to build this on — the same production API this page measures.

Request access for this use case