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 social-W38-Sat-3kind threadweek W38date 2026-09-26campaign thread · Satpillar socialbeat Satasset videoduration 58.3sground whitescenes 9

Checklist the per-video bar — engine/sim

83.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W38-Sat-3 good|bad)
⚠ 4 flag(s) — not yet ship-ready: copy_generictoo_complexdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 9 scenes · 58.3s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–5.9sspatial-parallaxicon·ember-fill♪ bed_in
Old way: strategic partnerships got picked on a hunch over dinner and a friendly handshake.
on-screen: Partnerships ran on gut feel
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Partnerships ran on gut feel
2s2
matches intent
shared field
signature-3d
hook5.9–13.2skinetic-buildicon·color♪ node_lock
Here is the risk: a warm handshake hides a bad fit until the deal is signed and already failing.
on-screen: A handshake is not a fit
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape torusground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→A handshake is not a fit
3s3
matches intent
NumberedList
template
teach13.2–20.2skinetic-buildicon·color♪ node_lock
New way: before any deal, compare the two audiences to see if they truly share the same people.
on-screen: Check the audience overlap first
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape torusground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Check the audience overlap firstcurate items, nodes
4s4
matches intent
ComparisonTable
template
proof20.2–26.5sreceipts-counticon·color♪ node_lock
Now you partner where the audiences actually overlap, so each side brings people the other wants.
on-screen: Shared audience, real value
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape torusground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Shared audience, real valuecurate colA, colB, rows, statsLabels
5s5
matches intent
CodeWindow
template
diff26.5–33.5scrossfade-8ficon·color♪ node_lock
A logo on a deck is not a partnership. Real value is one audience reaching the other's people.
on-screen: A logo swap vs real reach
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Nuntius leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape torusground whitetreatment colormotion crossfade-8fpower morphinstrument morph→A logo swap vs real reachcurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template
teach33.5–39.8skinetic-buildicon·color♪ node_lock
Teach the rule: write down exactly who delivers what, before the excitement fades and memory drifts.
on-screen: Define who does what, in writing
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Define who does what, in writingcurate items, nodes
7s7
matches intent
KpiGrid
template
proof39.8–45.699999999999996sreceipts-counticon·color♪ node_lock
Terms on paper outlast the honeymoon, because the goodwill always fades faster than the work.
on-screen: Written terms outlast the honeymoon
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape torusground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Written terms outlast the honeymooncurate kpis, statsLabels
8s8
matches intent
StepFlow
template
step45.7–52.0skinetic-buildicon·color♪ node_lock
Your step: take one possible partner and map where your audiences overlap before you sign anything.
on-screen: Map two audiences before signing
expected on screen: white ground · a StepFlow panel over a dimmed Signal Field · Nuntius leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual pipelineshape torusground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Map two audiences before signingcurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve52.0–58.3scoalescenceicon·ember-fill♪ bed_out
Now partnerships start with fit, not vibes. The Big T-M checks the overlap before the handshake.
on-screen: Partnerships built on fit
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Partnerships built on fit

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)

tiktokStrategic partnerships are not a handshake over dinner. Check whether your audiences actually overlap before you sign anything. (AI-assisted) #partnerships #businessdevelopment #strategy
instagramA handshake hides a bad fit. Check the audience overlap first. Write down who does what. #partnerships #strategicpartnerships #businessdevelopment #strategy #marketing
linkedinStrategic partnerships too often get picked on a hunch over dinner, and a warm handshake hides a bad fit until the deal is already failing. The discipline: before any deal, compare the two audiences to see if they truly share the same people. Real value is one audience reaching the other's people, not a logo swap on a deck. Then write down exactly who delivers what, because written terms outlast the honeymoon and goodwill fades faster than the work. Map where your audiences overlap before you sign anything.
xStrategic partnerships are not a handshake over dinner. Check whether the audiences actually overlap, then put who-does-what in writing. Method:
facebookStrategic partnerships often get picked on a hunch, and a handshake hides a bad fit until it is too late. Check whether your audiences actually overlap first, then write down who does what. Comment for the fit checklist.
threadsStrategic partnerships are not a handshake over dinner. Before any deal, compare the two audiences to see if they truly share the same people. A logo swap is not a partnership. And write down who delivers what, because written terms outlast the honeymoon and goodwill fades faster than the work.
pinterestStrategic partnerships guide: how to evaluate a partner by checking real audience overlap before signing, and why writing down who delivers what outlasts the honeymoon. Strategic partnerships, business development, strategy, marketing.
blueskyStrategic partnerships are not a handshake over dinner. Check whether the audiences actually overlap, then put who-does-what in writing. Method:
youtubeStrategic Partnerships on Fit, Not Vibes: Check the Overlap, Write the Terms Partnerships too often get picked on a hunch, and a handshake hides a bad fit. This covers comparing the two audiences for real overlap before any deal, why a logo swap is not value, and why writing down who delivers what outlasts the honeymoon. Strategic partnerships, business development, strategy. AI-assisted production.

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