Content pipeline
The route
From article to earnings. Eight stops. One connected journey.
- queuedQ.01
- scriptedS.02
- voicedV.03
- alignedA.04
- renderedR.05
- reviewedRV.06
- publishedPB.07
- trackingTR.08
Route overview
- SERVICE
- COBALT LINE
- ROUTE ID
- RM-2026-C1
- JOURNEY
- CONTENT PIPELINE
- STOPS
- 08
- STATUS
- OPERATIONAL
Stops and waypoints
- 01queuedArticle received and queued for production.
- 02scriptedScript written and structure locked.
- 03voicedNarration rendered offline.
- 04alignedAudio matched to visuals word by word.
- 05renderedMaster and verticals cut from one manifest.
- 06reviewedQuality gate, then human sign-off.
- 07publishedShipped to the channel with tagged links.
- 08trackingClicks and revenue read back per video.
Journey notes
Every transition is logged. Unchanged work is never redone: same script, same voice, no re-render.
Stories on schedule. Impact on arrival.
Planned like a railway. Built frame by frame. Reviewed before it leaves. Four cars on every train:
- 01
- A script is written from the article, voiced offline, and aligned word by word so every visual lands on its sentence.
- 02
- Verticals are re-composed 9:16 from the strongest scenes, never cropped out of the widescreen master.
- 03
- Machines catch loudness, sync, and missing disclosures. A person approves judgment before anything ships.
- 04
- Every description link carries the video's own tag, so earnings come back attributable to the exact cut.

Reference markrm-000123
Dollars per video, not views
Revenue is routed the way operators think: by asset, not algorithm. Every video is a line item. Every upload, an entry on the ledger.
Clear attribution, clean reporting, read straight from the retailer's own numbers.
See how it works- Uploadcreate and publish
- Attributematch to earnings
- Settleaggregate revenue
- Dispatchreport per video
Nothing publishes itself.

The process
Checks, edits, sign-off. Every step visible. Every detail considered. Nothing left to chance.
JourneyToday
- QA gate
- Human review
- Approved
- Dispatch
- DISPATCH ID
- RM-000125
- STATUS
- APPROVED
- SIGNED
- The reviewer. A person.
New on the yard
More lines. Same gate.
Next to affiliate videos, Reelmarshal now runs editorial packages, channel Shorts and long-form episodes. Renders stay on the machine, code gates run before review, and nothing goes out without a release.
Line 2 · Editorial packages
Article → video. Every number checked.
A finished, sourced article plus its evidence list becomes a narrated main video with animated charts, a natively composed vertical Short, a thumbnail and complete YouTube metadata.
Real package, published on the channel “AI Unfiltered with Thorsten Meyer”.
Two stages, one package
Charts on a clean board, or a world drawn by hand.



- 01Every number on screen is in the article.A code gate compares each chart value with the article text, same rounding, and refuses values from rejected evidence.
- 02Every frame is deterministic.Each frame is a pure function of time: no timers, no randomness. The same package renders the same video.
- 03Format, loudness and safe area are measured.Main video and Short are checked for size, frame rate, loudness and overflowing text before review.
- 04A release, then the gateway.A person or a recorded standing approval releases the package; the upload runs through the publishing gateway with the synthetic-media disclosure set.
Package
- IN
- Article + evidence list
- OUT
- Main video 16:9
- OUT
- Short 9:16
- OUT
- Thumbnail
- OUT
- Title, description, tags
- LOOK
- HORIZON or doodle
Line 3 · Channel Shorts and long-form
One Short a day. No quote unchecked.
A weekly plan becomes one Short per day: a hook question, the answer, and its reference. On the first channel, a faith channel, the reference is a Bible verse. The same yard now runs Shorts and weekly long-form episodes for a network of brand channels, each long-form episode with its own 16:9 thumbnail and a fixed release time.
- Quotes, word for wordEvery Bible quote is checked against a public-domain translation, the World English Bible. A wrong word or a wrong reference stops the Short.
- Never twiceTitles and scripts are checked against everything the channel has published, so neither can repeat.
- A weekly capEach channel has a fixed number of Shorts per week; the plan cannot exceed it.
- Measured outputLoudness, length and format are checked on every Short before review.
- A companion articleOn the faith channel, each Short gets its own short article.
- Released, then scheduledA person or a recorded standing approval releases each video; it is scheduled at least a day ahead.
- Replaced only on orderA video that is already handed off is replaced only on the owner's order, through the publishing gateway.
The first two Shorts on @JesusAnswers_org: two caption looks for the channel, published before the daily run started.
Before anything publishes
Green, or it waits.
Every package passes code gates before a person or a standing approval can release it. A red gate stops the job; a warning holds it for the owner.
- Numbers match the articleEvery value on screen must appear in the article with the same rounding, and never from a rejected source.
- Curves against their dataPoints on a chart line that carry no label are checked against a declared dataset.
- The voice against the scriptA speech-to-text check of the voice against the script runs on every narrated paragraph and on the finished video. Filler words or a drifting text send it back.
- Loudness at −14 LUFSMain video and Short are mixed to −14 LUFS with a true-peak ceiling, then measured again before release.
- Clean picturesGenerated stills are inspected at high zoom, corners included, for stray lettering and signatures before one is used.
- No internal hostsTitles, descriptions and every visible text are checked for internal addresses before upload.
Release
A standing approval only counts when every gate is green and nothing is flagged.Releases are scheduled ahead, and the owner gets an overview per package, so any video can still be stopped before it goes public.Rendering
Only what changed renders again.The main video renders as parallel segments, each cached by a hash of its content. A text fix in one scene re-renders only the segments it touches.Software for a yard that keeps moving.
Purpose-built local apps, conducted by Reelmarshal. Media never leaves the machine except as an approved upload.
- Origin
- Script
- Render
- Platform
BUILT FOR THE JOURNEY.
RUN WHERE YOU RUN.
Runs on your machine
- RM-CV01CutrovaRenders master and verticals from one scene manifest.
- RM-CH02ChannelHelmBuilds thumbnails, publish kits, and uploads.
- RM-SK03SkaldrikAligns narration word by word and writes captions.
- RM-CR04commissionrouterPicks the product and stamps the tagged link.
- RM-GF05GrimfasteSupplies the articles and reads the revenue back.
