Skip to content
Design record / October 2026

The Master Document pipeline: a design record

The intended path from lecture evidence to readable teaching material, and the checks that make each step inspectable.

Start with the lecture

A Master Document starts with a particular lecture and its source material. Slides, transcripts and recordings supply different kinds of evidence. Keeping their origins visible lets a reader distinguish the source from the explanation built around it.

The Study Library gives those materials a home inside a module and lecture. An uploaded file or lecture shell is an input; it is not proof that parsing or generation has completed.

Make the transformation inspectable

The design separates collecting material, extracting usable content, assembling a document and studying it. Each stage needs a real result before the next stage can claim success.

A useful document should organise the lecture into readable sections while keeping enough source context to check its claims. Fluent prose alone does not establish that the explanation matches the lecture.

Learning needs its own evidence

Reading a generated document and demonstrating understanding are different events. Study activities and recall provide opportunities to show what a learner can use. They should not award mastery just because an activity was opened or completed.

This is a record of the intended method, not a claim that every pipeline stage or learning outcome has been independently validated. The project is still being developed.