Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post thread-the-stack-W42-Tuekind threadweek W42date 2026-10-20campaign thread · Tuepillar socialbeat Tueasset videoduration 35.8sground whitescenes 6

Checklist the per-video bar — engine/sim

72.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-the-stack-W42-Tue good|bad)
⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedup_set_across_assetsdead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SchematicCard
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 6 scenes · 35.8s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–5.0skinetic-buildicon·wireframe♪ node_lock
The tool is LinkedIn, where your buyers already are. The catch: the posting login is locked down tight.
on-screen: LinkedIn API is locked tight
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape torusground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→LinkedIn API is locked tight
2s2
matches intent
ChecklistCard
template
teach5.0–12.4skinetic-buildicon·wireframe♪ node_lock
So we route through a posting layer that handles the messy login, and run it from one script.
on-screen: Route through a posting layer
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Route through a posting layercurate items, nodes
3s3
matches intent
TerminalRun
template
build12.4–20.2stype-onicon·wireframe♪ node_lock
Now one post goes out to LinkedIn, X, TikTok and the rest from a single command, sized for each one.
on-screen: One script, nine platforms
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Nuntius leads · code · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape torusground whitetreatment wireframemotion type-onpower summoninstrument draw-on→One script, nine platformscurate codeLines
4s4
matches intent
ProcessFlow
template
proof20.2–25.799999999999997sreceipts-counticon·wireframe♪ node_lock
So pick a posting layer, connect two accounts, and schedule one cross-post from a script.
on-screen: Schedule one cross-post
expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual receiptsshape torusground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Schedule one cross-postcurate statsLabels, steps
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
futurist25.8–30.8sspatial-parallaxicon·wireframe♪ bed
The Stack
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape torusground whitetreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→The Stack
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve30.8–35.8scoalescenceicon·wireframe♪ bed_out
The Stack
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→The Stack

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

Social captions supplemental published copy · per channel (comp_id level)

tiktokThe tool is LinkedIn, where your buyers already are. The catch: the posting login is locked down tight. So we route through a posting layer that handles the auth and run it from one script across every channel. (AI-assisted)
instagramThe stack: LinkedIn, where your buyers are. The catch: the posting login is locked tight. Route through a posting layer. Drive every channel from one script. One post, nine platforms. #socialmedia #automation #linkedin #builtnotbought #contentops
linkedinThe tool is LinkedIn, where your buyers actually are. The catch: the posting login is locked down tight, so a direct script is painful. So we route through a multi-platform posting layer that handles the messy auth, and drive it from one script. One piece of content fans out to LinkedIn, X, TikTok and the rest from a single command, sized for each platform. The takeaway: pick a posting layer, connect two accounts, and schedule one cross-post from a script. That is the whole move.
xLinkedIn is where your buyers are, but its posting login is locked tight. Route through a posting layer that handles the auth, then run every channel from one script. Start here:
facebookThe tool is LinkedIn, because that is where your buyers actually are. The catch is that the posting login is locked down tight. So we route through a posting layer that handles the messy auth, then drive every channel from one script. Pick a posting layer, connect two accounts, and schedule one cross-post to start.
threadsThe tool is LinkedIn, where your buyers actually are. The catch: the posting login is locked down tight. So we route through a posting layer that handles the auth, then fan one post out to nine platforms from a single script. Pick a layer, connect two accounts, schedule one cross-post.
pinterestHow to post to nine platforms from one script: route through a multi-platform posting layer that handles the messy auth, then fan one piece of content out to LinkedIn, X, TikTok and more. Social media automation and cross-posting method.
blueskyLinkedIn is where your buyers are, but its posting login is locked tight. Route through a posting layer that handles the auth, then run every channel from one script.
youtubeTitle: Post to 9 Platforms From One Script (Around the Locked API) LinkedIn is where your buyers actually are, but its posting login is locked down tight. So we route through a multi-platform posting layer that handles the messy auth and drive it from one script. One post fans out to LinkedIn, X, TikTok and the rest, sized per platform. This short shows the move: pick a layer, connect two accounts, schedule one cross-post. (AI-assisted)

Cross-links every lens is a view on this one record