didactical.ai

Didactical · makers of LORE

A course explains each thing once. LORE explains it again, a different way, until it lands.

Every training course ever written picks one explanation per idea and hopes. The learners it doesn’t reach get the same words again, slower. LORE was built the other way round: it carries several routes to the same fact, and when someone misses a question it teaches that point again by a different route — narrated, in a voice that sounds like a person, in the moment.

Then it records which explanation finally worked — for that person, and across the whole cohort.

1 doc
Is all a course needs to start
5
Different routes to the same fact
576
Course corrections behind one 16-lesson build
18 min
Of GPU to narrate every one of them

What we do

From the document you have to a record of what your people actually understood.

The didactic method — one instructor, one lecture, one pace for everyone — does not survive contact with a workforce. LORE keeps the instruction and drops the single pace.

  1. 1

    Bring the document

    A manual, a guidance document, a standard operating procedure. PDF or text, up to 40 MB.

  2. 2

    LORE builds the course

    Lessons in order, with every question tied to the exact passage of the source it came from.

  3. 3

    Your instructors approve

    Nothing reaches a learner until your staff have read it. Nothing is narrated before that.

  4. 4

    Learners listen

    Each lesson narrated, on iPhone or Android, offline when there’s no signal.

  5. 5

    A miss says something specific

    Every wrong answer is a named misconception, written from the passage that warns against it.

  6. 6

    LORE teaches it again, differently

    A new explanation on that exact point plays next — and which one worked is the thing worth knowing.

When it doesn’t stick

Re-explaining the same way, slower, is what a bad teacher does.

Each route is a different cognitive path to the same fact — not a restyled version of the same sentence. However an explanation is produced, it has to quote the approved script to reach a learner; where the script gives no figure to work with, the analogy route produces nothing rather than inventing one.

Restate
The rule again, plainly, in the module’s own terms.
Contrast
Names what they chose against what the procedure asks for — “you chose consent; the procedure asks for containment.”
Consequence
Walks forward from their answer to what actually goes wrong.
Procedure
The concrete step to take, in that moment, at that bench.
Analogy
Uses a figure the script itself supplies — “the clock has become the most influential piece of safety equipment in the room; unfortunately it has terrible containment.”

Why the voice has to be this good

A course that keeps finding new words needs a narrator who can say them.

Hundreds of alternative explanations only exist as a product if narrating one costs nothing but machine time. Thirteen corrections rendered in twenty-three seconds — six times faster than real time — which is why a whole course’s adaptive layer is minutes of GPU rather than a studio calendar. And a voice a learner will hear that often has to be one they can stand for an hour.

  Hosted voice API LORE
Who the voice is A stock voice from a shared library, or a clone you upload. Your learners may have heard it selling software last week. Craig and Randi. Professional talent we licensed by name, who know their voice is teaching this material.
What it learned from Largely read-aloud corpora — audiobooks and studio reads. The model learns what reading sounds like. Broadcast voice-tracking: working announcers performing to an audience. The model learns what talking sounds like.
Inflection and emphasis Tuned per request, sentence by sentence. Stress lands where the model guesses, usually mid-sentence. Trained on long segments, so phrasing carries across a paragraph — the emphasis falls on the word the sentence is about.
How the audio gets made Chunk the script, call the API, stitch, listen for the seams. A human narrator means a booked session and an edit. Approved text renders straight through on the first pass. No session to book, no second take, no punch-ins.
Where the narration is made On the vendor’s servers. Your lesson scripts go with it. On a GPU we control, against our own model weights. Approved scripts and finished audio stay on infrastructure we run.

Listen

A full lesson, start to finish, unedited.

Randi reading section 1.7.3 of Applied Engineering Principles — shipboard ungrounded electrical systems — exactly as LORE built it. Two and a half minutes off the renderer in one pass; nothing re-recorded, punched in or cut. Listen for where she leans on a word.

Randi Section 1.7.3

Shipboard Ungrounded Electrical Systems

0:002:26
“Your ship’s electrical system is ungrounded. So, no path to ground, right? … It sounds like solid logic. It is a deadly mistake.” Lesson script · drafted from the source, approved by a human

Where the read comes from

The same voices, doing the job they trained on.

Before it narrated a lesson, this voice read live radio — retail copy, forecasts, breaks. That is the performance the model was built from, and it is why the instruction above doesn’t sound read. Three reads, unedited.

Randi Retail spot

Hometown Auto Group

0:000:27
“Doors open Saturday at nine a.m. sharp — and the first twenty-five buyers get a five-hundred-dollar gift card.” Broadcast read · one pass, no edit
Randi Forecast

Hometown Forecast

0:000:13
“We’ll top out at eighty-four this afternoon, down to sixty-one overnight.” Broadcast read · one pass, no edit
Randi Break

Coming Up After the Break

0:000:06
“Brand new music, plus your chance to win tickets. Stick around.” Broadcast read · one pass, no edit

Sources: Applied Engineering Principles, chapter 1 · broadcast copy · licensed voice talent, signed consent on file · rendered on our own GPU

What it learns

Which explanation worked is a more useful fact than who got it wrong.

Because the same idea is taught several ways, LORE can record not just that someone missed a point but which route finally reached them. Roll that up across a cohort and a raw pass rate separates into four very different situations that look identical from the outside.

01

A broken question

The students who did well overall got this one wrong more often than the students who did badly. A miskeyed or ambiguous item can carry a perfectly unremarkable pass rate and be invisible to any amount of reading — and obvious to the statistic.

02

Something the lesson never taught

Failed first time, passed after the correction. The retry is carrying the module, which means the script has a defect with a specific address — this is the signal that turns an adaptive loop into a course-improvement loop.

03

A genuinely hard concept

Low pass rate, and the retry is no better. Nothing is broken here — the topic simply deserves more of the course than it is getting.

04

A question doing no work

Everybody passes it. It distinguishes nobody, and it is taking up a slot that could be telling you something.

Two things we will not do with this data. We do not hide the sample size: item statistics are noisy below thirty responses and meaningless below ten, so every figure carries its n and anything under the floor is reported as provisional. A course change made on six answers is a guess with a decimal point on it. And we do not sort people into learning styles — the visual/auditory/kinaesthetic typology does not survive testing. What gets recorded is observed behaviour: which explanation this person responded to, on this concept.

Straight about the state of it

What runs today, and what we are still building.

Working now

  • Document to published courseLessons and questions drafted from the source, held at a human review gate, narrated and published.
  • Narration on our own hardwareWhole courses rendered in one pass against a licensed voice, verified lesson by lesson before anything attaches.
  • Listening, checks and correctionsLecture playback, offline, with short checks after each lesson and a corrective lesson on a missed point.
  • Grounding enforced in codeNo question and no correction is published unless it quotes the approved script verbatim.
  • Course corrections at scaleThirteen rendered in twenty-three seconds in the prototype; about eighteen minutes of GPU covers a sixteen-lesson course.

In development

  • The full correction matrixWritten by hand against the script so far. The generator that writes it is the current build.
  • Live generationWriting the explanation in the moment rather than choosing from a prepared set — with the same verbatim-source check standing in front of it, so nothing reaches a learner that cannot cite the script.
  • Recording which route landedThe selection logic and the store behind it — the piece that makes the learning map real.
  • Cohort item analysis in the consoleThe statistics exist and are verified against a planted defect; surfacing them to instructors does not yet.
  • Two-voice podcast formatThe second narration register, alongside the single-voice lecture.

Bring us the course people keep failing.

Send the manual you’d start with. A pilot is one document, a small group of learners, and a few weeks.