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-W37-Sat-2kind threadweek W37date 2026-09-19campaign thread · Satpillar performancebeat Satasset videoduration 52.7sground redscenes 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-W37-Sat-2 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 · 52.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.5sspatial-parallaxicon·white-knockout♪ bed_in
Mobile apps used to try to do everything, and ended up doing nothing well.
on-screen: Apps tried to do everything
expected on screen: red 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 redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Apps tried to do everything
2s2
matches intent
shared field
signature-3d		hook5.5–12.1skinetic-buildicon·white-knockout♪ node_lock
The quiet death: an app that does too much gets confusing, and a confused user deletes it.
on-screen: A bloated app gets deleted fast
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→A bloated app gets deleted fast
3s3
matches intent
NumberedList
template		teach12.1–18.4skinetic-buildicon·liquid-chrome♪ node_lock
Here is the lesson that holds: nail one core job perfectly before you add a second.
on-screen: Nail one job before adding more
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Nail one job before adding morecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof18.4–24.7sreceipts-counticon·white-knockout♪ node_lock
People keep the app that solves one real problem fast, not the one with forty buttons.
on-screen: People keep the app that solves one
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→People keep the app that solves onecurate colA, colB, rows, statsLabels
5s5
matches intent
CodeWindow
template		diff24.7–29.7scrossfade-8ficon·liquid-chrome♪ node_lock
The old way crammed in every feature a meeting could imagine.
on-screen: Old way: cram in every feature
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape dodecaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Old way: cram in every featurecurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template		teach29.7–36.3skinetic-buildicon·white-knockout♪ node_lock
Now AI can read where people tap and give up, so you cut the parts nobody uses.
on-screen: Now AI shows where users get stuck
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Now AI shows where users get stuckcurate items, nodes
7s7
matches intent
KpiGrid
template		proof36.3–41.3sreceipts-counticon·liquid-chrome♪ node_lock
Cutting the dead weight makes the one good thing feel even faster.
on-screen: Cut the dead weight, keep the keep
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Cut the dead weight, keep the keepcurate kpis, statsLabels
8s8
matches intent
PipelineMap
template		step41.3–47.199999999999996skinetic-buildicon·white-knockout♪ node_lock
Your move: pick one job, watch where users stall, cut the rest, polish what stays.
on-screen: Steps: one job, watch taps, cut, polish
expected on screen: red ground · a PipelineMap panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual pipelineshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Steps: one job, watch taps, cut, polishcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve47.2–52.7scoalescenceicon·white-knockout♪ bed_out
That is how The Big T-M builds apps people keep on the home screen.
on-screen: Apps people keep on the home screen
expected on screen: red 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 redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Apps people keep on the home screen

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)

tiktokMobile app truth: an app that does everything does nothing well, and a confused user deletes it. Nail ONE core job before adding a second. AI shows where people tap and give up so you can cut the dead weight. AI-assisted. #mobileapp #appdev #UX #product #tech
instagramDo one thing. Do it fast. A confused user deletes you. #mobileapp #appdesign #ux #product #appdev
linkedinMost mobile apps die from doing too much. An app that tries to do everything becomes confusing, and a confused user deletes it. The lesson that holds: nail one core job perfectly before adding a second, because people keep the app that solves one real problem fast, not the one with forty buttons. AI can now read where users tap and give up, so you cut what nobody uses. Trimming the dead weight makes the one good thing feel even faster.
xAn app that does everything does nothing well. Nail one core job before adding a second. AI shows where users give up so you cut the dead weight. temerarii.com
facebookMobile apps used to try to do everything and ended up doing nothing well. Nail one core job before adding a second. AI can show where people tap and give up so you can cut the dead weight. More at temerarii.com.
threadsMobile app truth: an app that does everything does nothing well, and a confused user deletes it. Nail one core job before a second. AI shows where people tap and give up, so you cut the dead weight and the one good thing feels faster.
pinterestMobile app strategy: nail one core job before adding features, and use AI to find where users get stuck so you can cut dead weight. App design tips, mobile UX, product focus.
blueskyAn app that does everything does nothing well. Nail one core job first. AI shows where users give up so you cut the dead weight. temerarii.com
youtubeMobile Apps: Do One Job Well Before Adding a Second An app that does everything gets deleted. We cover nailing one core job, using AI to find where users tap and give up, and cutting dead weight so the one good thing feels faster. More at temerarii.com. #MobileApp #AppDev #UX

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

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