Check 01
The finished piece itself
The check runs on the finished video file — the exact artifact that would post — reviewed at full size, never on a draft, a proxy, or a promise that the render came out right.
This page publishes the standard itself — what every video must satisfy before it can post, on our channels and on a client's. It is the same standard the work is actually held to. How the checking machinery works inside stays backstage; what it demands of a finished piece does not.
The standard — applied to every piece, ours and clients'
Check 01
The check runs on the finished video file — the exact artifact that would post — reviewed at full size, never on a draft, a proxy, or a promise that the render came out right.
Check 02
Framing holds the subject; no dead spots, no broken frames, no drift from the channel's animated form. Host footage is watched frame by frame for exactly that drift.
Check 03
Voices are clear and synced to the picture; music sits under the voice, never over it; no clipping, no silence that wasn't chosen.
Check 04
Captions and on-screen text are accurate, readable at phone size, and timed to the speech they carry.
Check 05
Every ingredient — footage, music, images — is material we made, material licensed for this use, or material used under a stated fair-use basis. A piece with an unclear right does not post.
Check 06
Factual claims are checked before publication. Quotations are verified against their sources; a famous line that doesn't check out is named as misattributed, never repeated as fact.
Check 07
The piece belongs on its channel: right format, right cast, right energy for that audience — and, on FragVault, gameplay that is genuinely the featured player's own.
Check 08
Only the current, finished build of a piece can post. A stale file, a superseded cut, or yesterday's export is not a post — the gate refuses it.
Not warns, not flags for later — blocks. The piece goes back for a fix and is checked again, as a finished piece, before it can post. No exceptions for deadlines, ours included.
Every piece carries its pass with it. A post without a recorded pass does not happen — the publishing path itself refuses, so the rule holds on tired days as well as good ones.
Where a check cannot be completed — a right that can't be confirmed, a fact that can't be verified — the piece waits. We do not dress a gap up as a pass, on our channels or in client reporting.
What this page deliberately does not contain: the machinery — the tools, thresholds, and internal workflow that run the checks. That's the part we keep backstage, and it's what a license buys the benefit of without buying the blueprints. The standard above is the whole promise, and you can hold any piece we publish against it.
Answers come from our public pages only.