What has to be true before we say published

Every Autoretto release walks the same path. Suno builds the audio. Gemini writes the title and description and makes the cover art. If a creator wants motion, Sora generates a few cinematic shots. Then a renderer puts it all together into a video that hits the beat. That video does not go straight to YouTube. It passes a quality gate first. That gate is a set of automated checks. They are not ceremonial. They decide whether a release exists.

This gate exists for one reason. An automated pipeline will happily report success even when the output is garbage. A silent audio file is garbage. A video that lost sync halfway through is garbage. A publish event with no MP4 behind it is garbage. That kind of slop degrades a channel and wastes a creator's trust. Autoretto was built to avoid it. So we made the gate strict.

The first check is real audio decoding. The file Suno returns is nothing more than bytes. We do not trust the download or the metadata that came with it. We decode the actual audio samples and look at what is really there. We verify the sample rate matches the project configuration. That matters because a renderer can assume a different rate and stretch the audio. We measure loudness and scan for long stretches of digital silence. A blank section that lasts more than a second is a red flag. We check for clipped, flattened peaks that would sound terrible. We also run the policy scanner against the audio content. If any of these fail, the release stops right there.

The second check is audio-to-video sync. The render step creates cuts and motion on the musical beat. But software can drift. A renderer might drop a frame or introduce a small offset. So we verify the finished video, not the intended one. We extract audio from the MP4 and align it with the source audio from Suno. We measure the offset at the start, middle, and end. The offset must stay under one frame, about 33 milliseconds at 30 frames per second. The total duration must also match to the frame. If the video is longer or shorter, something went wrong. We also look for repeated frames and frozen sections. Those are signs the renderer choked on the beat structure.

The third check is the verified MP4 artifact. This sounds simple, but it is the most important gate. Autoretto will not claim a publish unless the final MP4 exists as a real file we can open. We store the file on durable storage, not just in memory. Then we run ffprobe on it and inspect the container. We look for a valid video stream and a valid audio stream. We decode a few frames to make sure they are not black or blank. We compare the file's checksum against what the render step logged. If the file is missing, truncated, or even slightly different, we do not record a success. The verification happens after the renderer closes the file handle. We open the file again from its path and read it back. That double-open proves the data is durable, not sitting in a cache.

Together, these three checks act as anti-slop. Slop is content that looks automated because it carries no care. A video with silent or distorted audio is slop. A video where the visuals drift away from the music is slop. A publish row in a database with no MP4 behind it is the worst kind of slop, because it is a fabricated success. The quality gate rejects all of it.

The gate also feeds learning. When a release fails, we store the failure reason and the context around it. That data shapes how future releases are generated. Maybe a Suno prompt keeps producing low volume output. The system will learn to boost the gain. Maybe a render setting causes a periodic drift in sync. The system will avoid that setting. None of that would be possible if we skipped the verification and declared victory early.