Review, publishing, and traceability

Use this page to see what checks a module passes before learners can see it, who releases it, and what records link it back to its sources and to the people who made it.

Script reviewCopy Anchor Link

Courses are built in the chat, where admins and members tell Vidext's agents what to teach; only organization admins and members can open it. Vidext's agents are AI agents that plan the course and write a script for each module: the words and screens of that short video lesson, written before it is built. Every script is then reviewed against the course, the module's plan, the request, your messages, and the sources, and the review names each problem it finds: the script Contradicts something, Leaves out part of it, or Repeats itself. When the review cannot check a script against its sources, it says so.

A module is built only from a script its review passed as it stands now: if the script, its plan, or its sources change, it is reviewed again before it can be built. While a script has open findings, the module cannot be built: the module line in the module's conversation, beside the studio (the panel in the chat where you watch and adjust a module), reads Couldn't build · the script has open review issues, and you ask the agents in the chat to resolve them. The review result is kept beside the script in your organization's course files.

What happens after a buildCopy Anchor Link

1. The build runs. Vidext lays out the module's script as screens and speaks the narration. The result is checked against the rules every version is held to before it is kept.
2. The result is built, not live. The build freezes an immutable version, which becomes the module's built version once any presenter video it shows has rendered. Admins and members can inspect and preview it without changing the live version used for learner playback.
3. Publishing the course makes it live. When an authorized person publishes the course, or publishes an update of it, every built module's version becomes its live version in one step. A module that is not built, or was withdrawn, stays hidden.

The explicit Publish course action is the final human release gate. It applies to everyone: Vidext's agents can build a module but never publish, and AI assistants connected over MCP only read. Until a course is published again, learners keep the versions they have; a module whose course has never been published stays hidden.

Inside a workspace, learners receive a live module through its published course and the applicable team assignment. A live module stays inside the organization. Reaching anonymous visitors requires an admin or member to turn on the separate Public access choice in the module line's details, beside the studio.

Stable live versionsCopy Anchor Link

A live module points to a specific content version. Learner playback and learning records use that stable version instead of a mutable working draft. Later changes accumulate on the draft and on newer built versions without silently rewriting the version a learner previously received; the next publication of the course moves learners to the new versions.

Publication historyCopy Anchor Link

Every change to what learners can see is recorded against the course: each publish and update, each unpublish, archive, and restore, and each module withdrawn or restored, with who did it and when. A publish or an update also records the version of each module that went live, so the set of versions a course delivered at any point stays on record.

The product shows the latest of it: the course's publish sheet in the chat says when it was last published and by whom (Last published 2 hours ago by Ana), and a live module's line in its conversation says it is live and how many learners it has (Live · 24 learners). There is no history browser, and no way to roll a course back to an earlier publication: to change what learners have, build and publish again.

Who changed a scriptCopy Anchor Link

Every time the work in a chat conversation is saved, the change is recorded in your organization's course files under the conversation's owner, together with anyone else who worked in that conversation since the last save. Earlier versions of each script are kept. The product does not show this change history as a view today; it is kept for traceability and support.

What can be tracedCopy Anchor Link

Depending on the module and operation, Vidext keeps records that connect:

• the source documents, website pages, or research used as context;
• the course's structure and the script a module was built from, where each part of the narration names the source it draws on, or says it was written without one or follows a decision someone made;
• the review result for that script;
• the generated module version and its media;
• each course publication, who made it, and the module versions it made live;
• each saved change to the course's files and who made it;
• request, workflow, provider, and trace identifiers used for operational diagnosis;
• workspace events such as membership, assignment, settings, and content changes.

These records support product history, troubleshooting, and review. They are not presented as a certified audit log or a complete legal record of every data access.

Reviewing generated contentCopy Anchor Link

Read each script and its review findings in the chat, and use Preview after the build completes, before publishing the course. For source-sensitive material, verify claims against the source each part of the narration names, and change the script and build again when something needs correction.

See What Vidext reads for how sources ground generation, Draft, built, and live for publication behavior, and Data handling for the distinction between content history, activity events, and security records.