Full-length AI training courses, up to 30 hours

Thirty hours, planned as modules, in order

Ask for a whole subject and set the runtime to 30 hours. What comes back is a numbered, titled module list in the order the material should be learned, sized to the runtime you chose.

The arc the deterministic plan runs is orientation and prerequisites, foundations, core mechanics, worked problems, common failure modes, deeper structure, derivations and proofs, applications, edge cases, extended practice and synthesis, closing on recall and self-test. On a 30-hour course that arc runs many times over, in numbered parts, so the plan stays readable at scale. A chapter model that names the modules itself is told the same thing in a different way: open with what the learner needs before anything else makes sense, and close on consolidation or the judgement calls that only make sense once the mechanics are known.

Where the module list comes from

No step asks you to approve a module list before you commit. The runtime you pick is the lever that decides the shape: no module may run longer than 30 minutes, so a longer runtime is split into more modules rather than longer ones, and the deterministic plan for a 30-hour course is 225 modules of 8 minutes.

The chapter titles themselves are decided when the build starts, by a model that reads the whole brief - your own words, every answer you tapped, the track, the level, the runtime, and each file you attached with the line you wrote on it. If that model cannot be reached or answers unusably, the deterministic plan is used instead. Either way the plan lands on the build card in your library, and the event log on that build names which of the two decided it. If particular chapters matter to you, say so in the notes box in your own words.

What every module carries

Every module has one job, and it says what that job is before it starts. It carries its own narration and its own worked examples. Nothing you already understand gets explained again, because the level is fixed before anything is built.

On a whole-subject course, worked problems and extended practice are modules in their own right, not an afterthought. Chapter titles are held to one standard: name what you will be able to DO, not the topic the module covers.

Every finished build gets a watch page of its own. It is private to begin with - you, and the team on your account - and you can open it to people you name by email address, or make it public, in which case anyone holding the link can watch it and only then can it be embedded on another site or posted to a social network.

Pick the level, then the runtime

Four levels: beginner assumes nothing, intermediate assumes the vocabulary, advanced assumes the formalism, expert assumes the literature. The level changes how the course is pitched, never what it costs.

Minutes are the only meter, and nothing else is rationed: a 30-hour course costs 1800 minutes of your monthly allowance or top-up balance, whatever level it is pitched at. The pricing page lists what each plan grants.

Files you hand over

A request can carry reference files, and the Files step is where they go. It is optional - the default answer is no and it costs one tap. The picker offers PNG, JPEG, WebP and GIF images, PDF, plain text and Markdown, and nothing else: there is no DOCX, PPTX or EPUB path, and a file dragged past the picker is refused with the same sentence.

You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it.

Each file has to be under 10 MB, at most 20000 characters are read out of a PDF or a text file, and what you attach is material to work from rather than an instruction that must be obeyed: the pipeline decides whether each one fits the video it is building.

Asking for a change afterwards

A change to a finished video is a NEW BUILD, not an edit inside the file you already have. You type the change in plain words, a confirm strip names the cost before anything is spent - the full runtime of that video in minutes, so a 30-hour course is 1800 minutes again - and the new build appears in your library beside the first one.

Nothing in the product edits inside an existing file, so there is no way to ask for one stretch of a video to change and leave the rest alone. The build you have is kept exactly as it is, with its own event log, and the new one is a build of its own.

Early build: an update request spends real minutes and hands back another sample file, not your rendered course. The video you have now is kept exactly as it is, and we will tell you the day real rendering begins.

What this early build does today

ZUQ is an early build, and the part of it that is live is the part that costs money. A request is saved, minutes really are debited, the build runs and its chapter list is decided - and then it hands back a sample file rather than your rendered video. We will say so on this page the day real rendering begins.