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-Wed-2kind threadweek W31date 2026-08-05campaign thread · Wedpillar it_devbeat Wedasset videoduration 63.4sground 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-W31-Wed-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 · 63.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·liquid-chrome♪ bed_in
Custom tools used to live as a tangled spreadsheet only one person dared to touch.
on-screen: Tools trapped in a spreadsheet
expected on screen: red 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 redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Tools trapped in a spreadsheet
2s2
matches intent
shared field
signature-3d		hook5.9–12.9skinetic-buildicon·white-knockout♪ node_lock
Dark truth: a tool only one person can run leaves the day they get sick on your calendar.
on-screen: A tool only one person runs is
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→A tool only one person runs is a risk
3s3
matches intent
NumberedList
template		teach12.9–20.2skinetic-buildicon·liquid-chrome♪ node_lock
The old reliable move: write the tool as a small script with one clear job and a plain name.
on-screen: Write it as a small script
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Write it as a small scriptcurate items, nodes
4s4
matches intent
RankList
template		proof20.2–27.5sreceipts-counticon·white-knockout♪ node_lock
Give it one input and one output, so anyone can run it from a button without reading the guts.
on-screen: One input, one output
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→One input, one outputcurate rows, statsLabels
5s5
matches intent
DiffCard
template		diff27.5–35.2scrossfade-8ficon·liquid-chrome♪ node_lock
Old way lived in one person's head. The right way lives in a file anyone on the team can run.
on-screen: Old
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape boxground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Old: locked in a head. Right: a runnable filecurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach35.2–42.5skinetic-buildicon·white-knockout♪ node_lock
Put the how-to-run note at the top of the file, so the next person needs no meeting to start.
on-screen: Write the how-to at the top
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Write the how-to at the topcurate items, nodes
7s7
matches intent
StatScoreboard
template		proof42.5–49.8sreceipts-counticon·liquid-chrome♪ node_lock
We build these at The Big T-M, small and boring, so a tool outlives the person who made it.
on-screen: Anyone can press the button
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Anyone can press the buttoncurate pillar, stats, statsLabels
8s8
matches intent
SchematicCard
template		step49.8–56.8skinetic-buildicon·white-knockout♪ node_lock
Your move: turn the task into a script, one in one out, write the how-to at the top.
on-screen: Steps: script, simplify, document
expected on screen: red ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual pipelineshape boxground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Steps: script, simplify, documentcurate nodes, stages, steps
9s9
matches intent
shared field
signature-3d		resolve56.8–63.4scoalescenceicon·liquid-chrome♪ bed_out
Now the tool runs without you, and a sick day stops being a single point of failure.
on-screen: Tools that outlive you
expected on screen: red 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 redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Tools that outlive you

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)

tiktokIf only ONE person can run your tool, their sick day is on your calendar. Fix it: write it as a small script, one input one output, with the how-to at the top so anyone can press the button. #coding #automation #tools
instagramOne job per script. One input, one output. How-to at the top. Tools that outlive you. #coding #automation #devtips #tools #temerarii
linkedinA tool only one person can run puts the day they get sick on your calendar. Write the tool as a small script with one clear job, one input and one output, and put the how-to-run note at the top so the next person needs no meeting to start. Small and boring outlives clever and trapped.
xIf only one person can run your tool, their sick day is on your calendar. Small script, one in one out, how-to at the top. Tools that outlive you. temerarii.com
facebookStop letting tools live in one person's head. Write each as a small script with one input and one output, and put the how-to right at the top so anyone can run it. Full method free on the site.
threadsA tool only one person can run leaves the day they get sick on your calendar. Write it as a small script, one input one output, how-to at the top. Small and boring outlives clever and trapped.
pinterestCustom tools and internal apps best practices: write small single-purpose scripts, design for one input and one output, and document how to run them at the top. Maintainable runnable tools that anyone on the team can use.
blueskyIf only one person can run your tool, their sick day is on your calendar. Small script, one in one out, how-to at the top. Tools that outlive you. temerarii.com
youtubeCustom Tools That Outlive You: Small Scripts, One In One Out, Documented A tool only one person can run puts their sick day on your calendar. Write the tool as a small script with one clear job, one input and one output, and put the how-to-run note at the top so the next person needs no meeting. Small and boring beats clever and trapped. 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