Review and traceability

"How do we ensure the content is accurate?" is the right first question to ask any AI system. Vidext's answer is structural: the system produces a reviewable draft, humans decide when to publish, and everything that ships is traceable.

The gates

1. Draft review. An explicit creation request plans and builds immediately, but its output remains a team-only draft that you can inspect, preview, and edit.
2. Publish and verification. A person decides when to publish. Vidext renders the presenter video and verifies the complete candidate version before switching learners to it.

The publication gate is not an optional workflow setting — it applies to everyone, including AI assistants operating over MCP. Planning still produces a structured internal artifact and validated builder handoff for consistency and auditability; it is no longer a separate human approval screen.

Immutable published snapshots

Publishing creates a stable snapshot of the module — the precise version served to learners. Drafts and published versions are stored separately, which is why learners never see in-progress work and why learning analytics can attribute results to the exact content version a learner saw.

The trail

For any published module you can trace:

• the sources that grounded it (your documents, imported pages, connected content);
• the structured internal plan and build handoff it was built from;
• the edit history after publishing — conversational edits are validated, applied as structured changes, and backed up, so the previous state is recoverable and the change is auditable.

Workspace activity history

Beyond content, meaningful organizational actions — membership changes, team and enrollment changes, settings changes — are recorded in a first-party activity history, with metadata sanitized of personal content (see Data handling).