Case study / 06

Extending a Multi-Brand Distribution Factory to YouTube

How Dark Range Holdings added YouTube as a native, human-approved distribution channel for three brands without rebuilding the shared marketing control plane.

01 / Case study

The constraint

The distribution factory already knew how to turn verified releases into channel-specific work for Bluesky, Threads, Mastodon, Instagram, and X. Adding YouTube could not become a second marketing architecture. The goal was to add a video channel while preserving the same candidate, planning, QA, human-approval, execution, ledger, recovery, and reconciliation boundaries.

02 / Case study

One adapter, three brands

Dark Range Holdings, MiniMindsLab, and Omegift each use a separate native n8n YouTube OAuth credential and a separately verified YouTube channel ID. The shared adapter routes by surface and account identity instead of inferring the destination from copy, URLs, or credential order. One adapter therefore serves all three brands without collapsing their identities together.

03 / Case study

Fail-closed channel identity

Before an upload is attempted, the adapter performs a read-only channels.list lookup using the selected OAuth credential and compares the returned UC channel ID with the expected brand channel. A mismatch stops the job before mutation. This turns the most dangerous multi-brand publishing failure—posting valid content to the wrong account—into an explicit preflight error.

04 / Case study

Video becomes a normal distribution asset

YouTube is represented as an asset-required channel whose required asset is a short MP4 video. The existing channel matcher, planner, media generation, QA, and approval machinery carries that requirement through the same control plane used by the other networks. The platform-specific behavior begins only at the adapter boundary.

05 / Case study

Publication is not the end of the transaction

After upload, the adapter reads the created video back and requires public visibility before reporting a successful publication. The result then enters the existing publish ledger, bounded recovery controller, release reconciler, and completion reporter. A YouTube upload therefore participates in the same durable execution and replay-safety model as the rest of the distribution estate.

06 / Case study

The result

A new distribution channel was added without duplicating the factory. MiniMindsLab tools, Omegift gift guides, and Dark Range Holdings case studies can all produce approved YouTube video jobs through the same shared 04.xx architecture, while each brand keeps its own credential, channel identity, content lineage, approval record, and publication receipt.