CloviTube Review the live run
How it works

Ten states. Four of them require a person, not a model.

This is the real state machine every production moves through — nothing skips a gate, and nothing publishes itself.

stage 01

DRAFT

Script written, not yet reviewed

stage 02

RESEARCHED

Source material gathered for the topic

stage 03

SCRIPT APPROVED

Human sign-off

Human gate
stage 04

AUDIO LOCKED

Locked-in voice narrates every beat

stage 05

ASSETS READY

Still-frame visuals + music/SFX mixed

stage 06

EDIT DRAFT READY

Full cut assembled

stage 07

QC PASSED

10 automated checks

Human gate
stage 08

RELEASE APPROVED

Human sign-off

Human gate
stage 09

UPLOAD PACKAGE READY

Packaged for YouTube Studio

stage 10

PUBLISHED

Manual upload only

Human gate

Script & scene planning

One pass covers the whole script for scene descriptions — avoids beats repeating or contradicting each other's visuals, a real defect found and fixed this build.

Demonstrated

Voice

The channel's auditioned, locked-in voice narrates every beat with a short pause between beats and tuned stability settings, so a 7-beat video sounds like one take, not seven.

Demonstrated

Visuals

One still-frame image per beat, generated under an explicit no-dense-text rule. No motion, pan or zoom — a deliberate decision, re-examined each cycle, not an unexamined default.

Demonstrated

QC gate

Ten re-runnable checks (see Governance) must pass before a production can move to release.

Demonstrated

Release & upload package

A person approves release. The system prepares an upload package — it does not publish on its own, by design.

Demonstrated

Post-publish analytics

Performance data is entered manually today. A live YouTube Analytics API pull is a planned, not built, capability.

Not available yet