The Passage went into YouTube Studio on 24 July: 864×496 landscape, 32.7 seconds, a Seedance-generated training fight. The pack applied the one-week house rule. PublishAt: Friday 31 July 17:00 BST.
Sixty seconds of review later: the format was wrong.
The Short threshold
CJ’s call, same day: 32.7 seconds in standard landscape would be penalised. It has to be a Short.
Shorts require 9:16 orientation. The Passage was 864×496 — landscape, not vertical. A sub-60-second clip in landscape doesn’t land on the Shorts surface; it goes through standard video distribution and competes against content it has no business competing with. The original upload had to go.
The re-render
The fix was a blurred-fill conversion: the 864×496 master centred in a 1080×1920 canvas, the letterbox bars above and below filled with a blurred version of the source. Standard interim for a landscape master that needs to be vertical quickly. Visually noisier than a purpose-shot Short; classifies correctly and the content reads fine on a small screen.
New upload: AbVoGj7jzOw. #shorts metadata applied. Same publishAt: Friday 31 July 17:00 BST. Original landscape upload went private.
The Passage teaser on captainrandom.co.uk pointed at the original upload ID. That updated immediately — fix commit one on 24 July.
The production master
Later the same day, the production team shipped their own Short master: branded fill areas, vertical thumbnails, a cleaner deliverable than the blurred-fill interim. Upload ID: gyeKLxX4ExA. Both prior uploads — the original landscape and the blurred-fill AbVoGj7jzOw — went private. publishAt held unchanged: Friday 31 July 17:00 BST.
The teaser updated again to gyeKLxX4ExA. Fix commit two.
Three uploads in one day. Two that got privated within hours. One that made it to the premiere.
What the chain actually cost
Each swap carried overhead: fix commit, redeploy, teaser update. The less visible cost was the live window between swaps. AbVoGj7jzOw was the active teaser target for part of 24 July before gyeKLxX4ExA superseded it. Anyone visiting the captainrandom.co.uk videos section in that window would have seen a teaser embed that would later resolve to a private video — a broken embed on a live page, for however long the gap lasted.
The thing that absorbed the damage: publishAt. Friday 31 July 17:00 BST held across all three uploads. Neither CJ nor the production team let the schedule shift. That discipline was informal; no system enforces publishAt consistency across upload swaps. The chain resolved without moving the premiere date, which is the only reason the audience-facing outcome was correct.
One misaligned publishAt from either side would have orphaned the premiere.
The upstream fix
The blurred-fill is a post-production patch for a pre-production decision. The Passage was 864×496 because that’s the Seedance generation output. The correct fix for a Short isn’t re-rendering landscape output after the fact — it’s generating in 9:16 from the start.
That option wasn’t available here: the generation had already happened, the clip was handed over, the re-render was the only tool available. But 9:16 at generation time is the decision that prevents the chain entirely. For any Seedance handover where the destination is YouTube Shorts: specify the aspect ratio in the generation brief. The intake checklist addresses format post-generation; the generation brief needs to address it upstream.
Out of scope: re-running the generation. The re-render was the right call given what was in hand.
Back-to-back premiere week
The Passage was the second handover in two days. On 23 July, the videos section on captainrandom.co.uk opened for the first time — /creative/videos/ had been sitting on “Coming soon” until B-054 shipped. The section launched with two entries: Lyrical Assassin as a published embed and Torture Dance as a premiere teaser. One day later, The Passage arrived.
Both premieres ran in the same week. The format problem with The Passage — the re-render, the two abandoned uploads, the two fix commits — landed while the videos section itself was still new, its first two entries less than 48 hours live. The teaser embed for The Passage was being updated in the same deploy window that Torture Dance’s teaser was new on the page.
On a slower cadence, these are contained adjustments. Back-to-back, they compressed into the same operational window.
What the intake checklist was missing
The format question wasn’t in the intake flow. The Passage arrived as a landscape clip, was scheduled as a standard upload, and the format problem surfaced in review rather than at handover.
Three additions:
- Duration and format. Sub-60 seconds means Short. Landscape master means 9:16 deliverable required before upload — not optional, not a post-upload decision.
- Who produces the 9:16 master, and by when. If the production team’s branded master arrives within 24 hours, the blurred-fill is redundant overhead and the teaser waits for the final ID. If their turnaround is longer, the interim buys time — but both paths need naming at handover, not surfacing mid-chain.
- The teaser goes in last. The MDX should point at the final upload ID. If that ID isn’t confirmed, the teaser waits. A live teaser targeting a transient upload is a dead embed in waiting.
The format question, asked at intake, eliminates the upload chain before it opens.
Release day
2026-08-03: both premieres live. torture-dance-short.mdx and the-passage.mdx flipped from status: upcoming to status: published. premiereLabel stripped from each. The teaser cards on the videos section rendered as embed cards.
B-054’s first full execution, complete.
The target state
One upload per premiere. Aspect ratio confirmed at generation time. 9:16 master in hand before the upload goes to YouTube. Teaser pointing at the final ID.
The Passage got there via three uploads, two abandoned, two fix commits, one window of broken teaser state on a live page. None of it needed to happen. The format question, asked before the generation runs, closes the chain before it opens.
