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-W31-Mon-1kind threadweek W31date 2026-08-03campaign thread · Monpillar it_devbeat Monasset videoduration 56.3sground whitescenes 9

Checklist the per-video bar — engine/sim

88.1/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W31-Mon-1 good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_genericdup_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 · 56.3s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–6.6sspatial-parallaxicon·color♪ bed_in
Old product management was a roadmap that doubled as a wish list nobody could say no to.
on-screen: Roadmaps as wish lists
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Roadmaps as wish lists
2s2
matches intent
shared field
signature-3d		hook6.6–12.5skinetic-buildicon·wireframe♪ node_lock
Dark truth: a backlog with no kill rule is just a graveyard with nicer formatting.
on-screen: A backlog is graves
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→A backlog is graves
3s3
matches intent
NumberedList
template		teach12.5–18.4skinetic-buildicon·wireframe♪ node_lock
The old discipline still rules: write the problem you're solving before you name any feature.
on-screen: Write the problem, not the feature
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→Write the problem, not the featurecurate items, nodes
4s4
matches intent
RankList
template		proof18.4–25.0sreceipts-counticon·wireframe♪ node_lock
Attach one number to each bet, so you know in two weeks if it lived or died.
on-screen: One metric per bet
expected on screen: white 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 whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→One metric per betcurate rows, statsLabels
5s5
matches intent
BuildLog
template		diff25.0–30.9scrossfade-8ficon·wireframe♪ node_lock
Old way measured how much you shipped. The honest way measures whether the number moved.
on-screen: Old: ship more. Right: ship right
expected on screen: white 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 whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Old: ship more. Right: ship rightcurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach30.9–37.9skinetic-buildicon·wireframe♪ node_lock
If the metric doesn't move, you kill the feature out loud and free the team to try again.
on-screen: Kill what doesn't move it
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→Kill what doesn't move itcurate items, nodes
7s7
matches intent
StatScoreboard
template		proof37.9–44.5sreceipts-counticon·wireframe♪ node_lock
We run this at The Big T-M, and fewer, clearer bets beat a long list of maybes.
on-screen: Fewer bets, clearer wins
expected on screen: white 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 whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Fewer bets, clearer winscurate pillar, stats, statsLabels
8s8
matches intent
StepFlow
template		step44.5–50.4skinetic-buildicon·wireframe♪ node_lock
Your move: write the problem, attach one metric, set a kill date before you build.
on-screen: Steps: problem, metric, kill
expected on screen: white ground · a StepFlow panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: problem, metric, killcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve50.4–56.3scoalescenceicon·color♪ bed_out
Now the roadmap has a spine, and saying no is finally cheaper than saying maybe.
on-screen: A roadmap with a spine
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→A roadmap with a spine

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)

tiktokThe old product discipline that still beats everything: write the PROBLEM before the feature, attach ONE metric per bet, set a kill date before you build. No metric movement = kill it out loud. #productmanagement #startups
instagramWrite the problem first. One metric per bet. Set a kill date. Fewer bets, clearer wins. #productmanagement #startup #buildinpublic #strategy #temerarii
linkedinA backlog with no kill rule is a graveyard with nicer formatting. The durable product discipline: write the problem before the feature, attach one metric to each bet, and set a kill date before you build. If the number doesn't move, kill it out loud. Fewer, clearer bets win.
xWrite the problem before the feature. One metric per bet. Set a kill date before you build. No movement, no mercy. temerarii.com
facebookProduct management that works: write the problem before the feature, attach one metric to each bet, and set a kill date before you build. If the number doesn't move, kill it. Full method free on the site.
threadsA backlog with no kill rule is a graveyard with nicer formatting. Write the problem before the feature, attach one metric, set a kill date before you build. If the number doesn't move, kill it out loud.
pinterestProduct management framework: write the problem before the feature, attach one metric per bet, and set a kill date upfront. Outcome-driven roadmap discipline that prevents backlog bloat and forces clear decisions.
blueskyWrite the problem before the feature. One metric per bet. Set a kill date before you build. No movement, no mercy. temerarii.com
youtubeProduct Management With a Spine: Problem, Metric, Kill Date A backlog with no kill rule is a graveyard with nicer formatting. Write the problem before the feature, attach one metric to each bet, and set a kill date before you build. If the number doesn't move, kill it out loud. Fewer, clearer bets win. Free 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