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-W24-Sat-2kind threadweek W24date 2026-06-20campaign thread · Satpillar it_devbeat Satasset videoduration 59.1sground blackscenes 9

Checklist the per-video bar — engine/sim

96.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W24-Sat-2 good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · 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 · 59.1s · 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·liquid-chrome♪ bed_in
Most product roadmaps are a tidy list of confident guesses.
on-screen: A roadmap full of guesses
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→A roadmap full of guesses
2s2
matches intent
shared field
signature-3d		hook5.0–12.0skinetic-buildicon·wireframe♪ node_lock
Here is how The Big T-M uses AI to decide what to build next from evidence, not opinions.
on-screen: How AI grounds what to build next
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→How AI grounds what to build next
3s3
matches intent
NumberedList
template		teach12.0–19.7skinetic-buildicon·wireframe♪ node_lock
Pour every support ticket and review into a model and let it cluster the complaints into a few real themes.
on-screen: Cluster the feedback, find the theme
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Cluster the feedback, find the themecurate items, nodes
4s4
matches intent
RankList
template		proof19.7–26.299999999999997sreceipts-counticon·wireframe♪ node_lock
The proof: the loudest request is often small, while the quiet, repeated one is the real problem.
on-screen: The loud one is rarely the big
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→The loud one is rarely the big onecurate rows, statsLabels
5s5
matches intent
BuildLog
template		diff26.3–31.8scrossfade-8ficon·wireframe♪ node_lock
The old way built whatever the loudest person in the room happened to want.
on-screen: Old way: build what the boss likes
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Old way: build what the boss likescurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach31.8–39.9skinetic-buildicon·wireframe♪ node_lock
Now you score each idea by how many it touches times how much it hurts, so the math picks the order.
on-screen: Score by reach times pain
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Score by reach times paincurate items, nodes
7s7
matches intent
StatScoreboard
template		proof39.9–46.9sreceipts-counticon·wireframe♪ node_lock
The receipt is focus: a real roadmap is the list of things you bravely chose not to build.
on-screen: Say no on purpose
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Say no on purposecurate pillar, stats, statsLabels
8s8
matches intent
FlowSchematic
template		step46.9–53.9skinetic-buildicon·wireframe♪ node_lock
Ship the smallest useful slice, then go back to the data to see if the pain actually dropped.
on-screen: Ship a slice, then ask again
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual pipelineshape boxground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Ship a slice, then ask againcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve53.9–59.1scoalescenceicon·liquid-chrome♪ bed_out
Let the evidence pick the order, and the arguments get a lot shorter.
on-screen: Let evidence pick the order
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Let evidence pick the order

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)

tiktokMost roadmaps are a tidy list of confident guesses. AI-assisted: pour every ticket and review into a model, cluster the complaints into real themes, then score by reach times pain so the MATH picks the order. The loud request is rarely the big one. Method below.
instagramRoadmaps ≠ confident guesses. Cluster the feedback. Find the quiet, repeated pain. Score by reach × pain. Say no on purpose. #productmanagement #product #strategy #saas #temerarii
linkedinMost product roadmaps are a tidy list of confident guesses. How we decide what to build next from evidence: pour every support ticket and review into a model to cluster the complaints into a few real themes, then score each idea by reach times pain so the math picks the order, not the loudest person in the room. Ship the smallest useful slice and check the data again to see if the pain dropped. Takeaway: a real roadmap is the list of things you bravely chose not to build.
xMost roadmaps are confident guesses. Cluster the feedback → find the quiet repeated pain → score by reach × pain → ship a slice, check again. Say no on purpose. temerarii.com
facebookMost product roadmaps are a tidy list of confident guesses. Here's the move: pour every ticket and review into a model to cluster complaints into a few real themes, then score each idea by reach times pain so the math picks the order. The loudest request is rarely the biggest one. Ship a small slice and check if the pain dropped. Want the method? It's on the site.
threadsMost roadmaps are confident guesses. Cluster the feedback into real themes, find the quiet repeated pain, score by reach times pain, ship a slice, check again. Say no on purpose.
pinterestProduct management with AI: how to cluster customer feedback into themes, prioritize by reach times pain, ship small slices, and validate with data. Plain-language product roadmap and prioritization guide for teams.
blueskyMost roadmaps are confident guesses. Cluster the feedback, find the quiet repeated pain, score by reach × pain, ship a slice, check again. Say no on purpose. temerarii.com
youtubeProduct Management: Build From Evidence, Not Opinions Most product roadmaps are a tidy list of confident guesses. This walkthrough shows how we decide what to build next: pour every support ticket and review into a model to cluster complaints into a few real themes, score each idea by reach times pain so the math picks the order, and ship the smallest useful slice before checking the data again. The loudest request is rarely the biggest one. AI-assisted production. Give-it-away method from The Big T-M. Chapters: confident guesses · cluster the feedback · quiet pain · reach times pain · say no on purpose.

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

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