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-W23-Wed-1kind threadweek W23date 2026-06-10campaign thread · Wedpillar performancebeat Wedasset videoduration 47.7sground whitescenes 9

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W23-Wed-1 good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

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

Composition layer × scene 9 scenes · 47.7s · 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.0sspatial-parallaxicon·color♪ bed_in
Mobile apps used to get built, launched, and then quietly forgotten.
on-screen: Apps were built then forgotten
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Apps were built then forgotten
2s2
matches intent
shared field
signature-3d		hook5.0–10.0skinetic-buildicon·color♪ node_lock
Nobody could say which screen made people give up and close it.
on-screen: Nobody knew where people quit
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Nobody knew where people quit
3s3
matches intent
NumberedList
template		teach10.0–15.1skinetic-buildicon·color♪ node_lock
The move: log every screen and tap as a named event you can count.
on-screen: Track each step as an event
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Track each step as an eventcurate items, nodes
4s4
matches intent
RankList
template		proof15.1–20.5sreceipts-counticon·color♪ node_lock
Events show you the exact step where most people quietly turn around and walk away.
on-screen: Events reveal the drop-off
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape dodecaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Events reveal the drop-offcurate rows, statsLabels
5s5
matches intent
TerminalRun
template		diff20.5–25.9scrossfade-8ficon·color♪ node_lock
Old way: guess which screen is broken. We read the funnel and know.
on-screen: We don't guess the broken screen
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape dodecaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→We don't guess the broken screencurate codeLines
6s6
matches intent
ChecklistCard
template		teach25.9–30.9skinetic-buildicon·color♪ node_lock
Now a model groups the angry repeat taps that mean a button does nothing.
on-screen: AI groups the rage taps
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→AI groups the rage tapscurate items, nodes
7s7
matches intent
StatScoreboard
template		proof30.9–36.0sreceipts-counticon·color♪ node_lock
It finds the dead button in minutes, not after a month of bad reviews.
on-screen: It finds the dead button fast
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→It finds the dead button fastcurate pillar, stats, statsLabels
8s8
matches intent
PipelineMap
template		step36.0–41.7skinetic-buildicon·color♪ node_lock
Step: fix the single worst drop-off screen before you add new features.
on-screen: Fix the worst step first
expected on screen: white ground · a PipelineMap panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual pipelineshape dodecaground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Fix the worst step firstcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve41.7–47.7scoalescenceicon·color♪ bed_out
Watch where people leave, then fix that. The Big T-M maps the exits.
on-screen: Watch where people leave
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Watch where people leave

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)

tiktokBuilt an app and forgot it? You don't know WHICH screen makes people quit. Log every screen as an event, find the worst drop-off, fix that one first. (AI-assisted) #mobileapp #ux
instagramApps get built, launched, forgotten. Log every screen as an event. Find the drop-off. Fix the worst step first. #mobileapp #appdesign #ux #product #analytics
linkedinMost mobile apps get built, launched, and quietly forgotten, so nobody knows which screen makes people give up. The fix is to log every screen and tap as a named event you can count, which shows the exact step where people walk away. Instead of guessing which screen is broken, a model can group the angry repeat taps that mean a button does nothing, finding the dead button in minutes instead of after a month of bad reviews. Fix the single worst drop-off before adding new features.
xYou don't know which app screen makes people quit. Log every screen as an event, fix the worst first. temerarii.com
facebookYou built the app, but you don't know which screen makes people quit. Log every screen and tap as an event to find the exact drop-off, then let a model surface the rage taps on a dead button. Fix the worst step before adding features. Want to see your exits? Visit temerarii.com.
threadsApps get built, launched, and forgotten, and nobody knows which screen makes people quit. Log every screen as a named event to find the drop-off, let AI spot the rage taps on a dead button, and fix the worst step first. Watch where people leave.
pinterestMobile app analytics tips: log every screen and tap as a named event to find exactly where users drop off, use a model to detect rage taps that signal a broken button, and fix the single worst drop-off screen before adding features. Improve app retention and UX with funnel analysis.
blueskyYou don't know which app screen makes people quit. Log every screen as an event; fix the worst exit first. temerarii.com
youtubeFind The Screen That Makes People Quit Your App Apps get built and forgotten, and nobody knows the drop-off point. Log every screen as an event, let AI spot rage taps on dead buttons, and fix the worst step before adding features. AI-assisted production. Learn the workflow at temerarii.com.

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view