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-W36-Sat-3kind threadweek W36date 2026-09-12campaign thread · Satpillar performancebeat Satasset videoduration 51.2sground blackscenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W36-Sat-3 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_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 · 51.2s · 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·white-knockout♪ bed_in
Software launches used to be build it for a year and pray someone shows up.
on-screen: SaaS launches were build-it-and-pray
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→SaaS launches were build-it-and-pray
2s2
matches intent
shared field
signature-3d
hook5.9–11.100000000000001skinetic-buildicon·wireframe♪ node_lock
You only learned if anyone wanted it the day you finally launched it.
on-screen: You learned the truth at launch
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→You learned the truth at launch
3s3
matches intent
NumberedList
template
teach11.1–17.0skinetic-buildicon·wireframe♪ node_lock
First move: sell the promise with a simple landing page before you build a thing.
on-screen: Sell the promise before you build
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Sell the promise before you buildcurate items, nodes
4s4
matches intent
ComparisonTable
template
proof17.0–22.9sreceipts-counticon·wireframe♪ node_lock
Count how many people sign up to be told when it is ready, then decide.
on-screen: Count who actually signs up
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Count who actually signs upcurate colA, colB, rows, statsLabels
5s5
matches intent
DiffCard
template
diff22.9–28.799999999999997scrossfade-8ficon·wireframe♪ node_lock
But a waitlist alone is just a number until you ask why they signed up.
on-screen: A waitlist alone is just a number
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→A waitlist alone is just a numbercurate codeLines, lines
6s6
matches intent
ChecklistCard
template
teach28.8–34.3skinetic-buildicon·wireframe♪ node_lock
So you read every reason they gave and look for the same pain repeated.
on-screen: Read the sign-up reasons closely
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Read the sign-up reasons closelycurate items, nodes
7s7
matches intent
KpiGrid
template
proof34.3–39.8sreceipts-counticon·wireframe♪ node_lock
Now you build the thing people already told you they would actually pay for.
on-screen: Build what they already asked for
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Build what they already asked forcurate kpis, statsLabels
8s8
matches intent
NodeGraphCard
template
step39.8–45.699999999999996skinetic-buildicon·wireframe♪ node_lock
Try it: put up a one-page promise and a sign-up before you write any code.
on-screen: Launch the page before the product
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape dodecaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Launch the page before the productcurate hub, nodes, stages, steps
9s9
matches intent
shared field
signature-3d
resolve45.7–51.2scoalescenceicon·white-knockout♪ bed_out
Prove the demand first, write the code second, and skip the year of guessing.
on-screen: Demand first, code second
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Demand first, code second

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)

tiktokStop building software for a year and praying. Here is the move: put up a one-page promise and a sign-up BEFORE you write code, count who signs up, then read WHY they signed up. Build what they already asked to pay for. #saas #startups #productmarketing
instagramBuild-it-and-pray is over. Sell the promise first. Launch a landing page. Count who signs up. Read why, then build it. #saas #startups #productmarket #buildinpublic #founders
linkedinSoftware launches used to be build it for a year and pray someone shows up. The method: sell the promise with a simple landing page before you build, count who signs up, and read every reason they gave for the same repeated pain. The takeaway: prove demand first, write code second, and skip the year of guessing. Receipts over hype.
xSaaS move: put up a one-page promise and sign-up before you write code, count who signs up, read why. Build what they already asked to pay for. temerarii.com
facebookSoftware launches used to be build it for a year and pray. The method: sell the promise with a landing page first, count who signs up, and read why. Build what people already asked to pay for. See it at temerarii.com.
threadsStop building software for a year and praying. Put up a one-page promise and sign-up before you write code, count who signs up, then read why. Build what they already asked for.
pinterestSaaS launch strategy: how to validate before you build. Sell the promise with a landing page first, count sign-ups, and read why people signed up. Evergreen guide to SaaS, product validation, and lean startup methods.
blueskySaaS move: put up a one-page promise and sign-up before you write code, count who signs up, read why. Build what they already asked to pay for. temerarii.com
youtubeSaaS Launch: Prove Demand Before You Write Code Software launches used to be build it for a year and pray someone shows up, learning the truth only on launch day. The real method: sell the promise with a simple landing page before you build anything, count how many people sign up to be told when it is ready, then read every reason they gave and look for the same pain repeated. Prove demand first, write code second. More at temerarii.com.

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