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-W28-Mon-3kind threadweek W28date 2026-07-13campaign thread · Monpillar it_devbeat Monasset videoduration 50.4sground whitescenes 9

Checklist the per-video bar — engine/sim

98.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W28-Mon-3 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 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 · 50.4s · 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
Product management used to mean guessing what to build in a room full of opinions.
on-screen: Product meant guessing in meetings
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Product meant guessing in meetings
2s2
matches intent
shared field
signature-3d		hook5.9–11.8skinetic-buildicon·wireframe♪ node_lock
The loudest voice won the roadmap and the user feedback sat unread in a sheet.
on-screen: The loudest voice won the roadmap
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→The loudest voice won the roadmap
3s3
matches intent
NumberedList
template		teach11.8–18.4skinetic-buildicon·wireframe♪ node_lock
Now we feed every ticket and review to a model and let it cluster the real pain.
on-screen: Cluster the feedback with a model
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Cluster the feedback with a modelcurate items, nodes
4s4
matches intent
ComparisonTable
template		proof18.4–23.9sreceipts-counticon·wireframe♪ node_lock
Hundreds of messages collapse into a handful of themes you can actually act on.
on-screen: Themes surface in minutes
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Themes surface in minutescurate colA, colB, rows, statsLabels
5s5
matches intent
StackTrace
template		diff23.9–28.9scrossfade-8ficon·wireframe♪ node_lock
The difference is the roadmap follows evidence, not whoever talks the most.
on-screen: Evidence beats the loudest voice
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Evidence beats the loudest voicecurate codeLines, errMsg, errType, fix, frames
6s6
matches intent
ChecklistCard
template		teach28.9–35.199999999999996skinetic-buildicon·wireframe♪ node_lock
Tag each cluster by how often it shows up and what it costs you to ignore.
on-screen: Tag each cluster by frequency
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Tag each cluster by frequencycurate items, nodes
7s7
matches intent
KpiGrid
template		proof35.2–40.2sreceipts-counticon·wireframe♪ node_lock
Often the quiet, repeated complaint is the one worth building for first.
on-screen: The quiet complaint is the big one
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→The quiet complaint is the big onecurate kpis, statsLabels
8s8
matches intent
ListCard
template		step40.2–45.400000000000006skinetic-buildicon·wireframe♪ node_lock
Your step: paste your last hundred tickets, ask for the top five themes.
on-screen: Your step: cluster last 100 tickets
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Your step: cluster last 100 ticketscurate items, stages, steps
9s9
matches intent
shared field
signature-3d		resolve45.4–50.4scoalescenceicon·ember-fill♪ bed_out
Build what the data keeps saying, not what the room shouted today.
on-screen: Build what the data keeps saying
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Build what the data keeps saying

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)

tiktokproduct management with AI (yes, AI-assisted): stop letting the loudest voice win the roadmap. paste your last 100 tickets and reviews, let a model cluster the real pain into 5 themes. build what the data keeps saying. #productmanagement #pm #aitools
instagramStop guessing the roadmap. Cluster every ticket with a model. Find the 5 real themes. Build what the data repeats. #productmanagement #productmanager #aitools #ux #tech
linkedinTakeaway: the modern product move is to let evidence set the roadmap, not the loudest voice in the room. Feed every ticket and review to a model, let it cluster hundreds of messages into a handful of themes, and tag each by frequency and cost of ignoring. Often the quiet, repeated complaint is the one worth building first. Build what the data keeps saying.
xProduct tip: stop letting the loudest voice win the roadmap. Cluster your last 100 tickets with a model, find the 5 real themes, build what the data repeats. temerarii.com
facebookProduct management used to mean guessing what to build while the loudest voice won the roadmap. Now you can feed every ticket and review to a model and let it cluster the real pain into a few themes. Build what the data keeps saying. More at temerarii.com.
threadsStop letting the loudest voice win the roadmap. Paste your last 100 tickets and reviews, let a model cluster the real pain into 5 themes. The quiet, repeated complaint is usually the one to build first.
pinterestAI product management workflow: cluster customer tickets and reviews into themes, prioritize by frequency, build a roadmap on evidence not opinions. Product manager tips, customer feedback analysis, roadmap prioritization, AI tools for PMs.
blueskyProduct tip: stop letting the loudest voice win the roadmap. Cluster your last 100 tickets with a model, find the 5 real themes, build what the data repeats. temerarii.com
youtubeAI Product Management: Let Evidence Set The Roadmap Product management used to mean guessing what to build in a room full of opinions, where the loudest voice won and user feedback sat unread. This short shows the move we use now: feed every ticket and review to a model, let it cluster hundreds of messages into a handful of themes, and tag each by frequency and cost of ignoring. The quiet, repeated complaint is often the one worth building first. Build what the data keeps saying. AI-assisted. More 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