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-W26-Wed-4kind threadweek W26date 2026-07-01campaign thread · Wedpillar it_devbeat Wedasset videoduration 76.8sground whitescenes 9

Checklist the per-video bar — engine/sim

93.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W26-Wed-4 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 · 76.8s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–8.8sspatial-parallaxicon·color♪ bed_in
Software used to ship once a year in a big nervous launch, and every bug had to wait twelve months for its apology.
on-screen: Software used to ship once a year
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→Software used to ship once a year
2s2
matches intent
shared field
signature-3d		hook8.8–17.9skinetic-buildicon·color♪ node_lock
The trouble with a big launch is the risk hides inside it, a thousand changes at once means a thousand suspects when it breaks.
on-screen: Big launches hide big risk
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Big launches hide big risk
3s3
matches intent
NumberedList
template		teach17.9–26.299999999999997skinetic-buildicon·color♪ node_lock
Here is the discipline that still wins: ship small and ship often, because a tiny change is a tiny thing to debug.
on-screen: Old rule: ship small, ship often
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Old rule: ship small, ship oftencurate items, nodes
4s4
matches intent
RankList
template		proof26.3–35.4sreceipts-counticon·color♪ node_lock
The method: put every change behind an automated test that runs on its own, so the robot catches the obvious break, not the customer.
on-screen: Every change behind a test
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Every change behind a testcurate rows, statsLabels
5s5
matches intent
TerminalRun
template		diff35.4–44.2scrossfade-8ficon·color♪ node_lock
Our line: let the tests guard the routine and keep humans on the gnarly logic, because judgment does not fit in an assertion.
on-screen: We keep humans on the hard parts
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape boxground whitetreatment colormotion crossfade-8fpower morphinstrument morph→We keep humans on the hard partscurate codeLines
6s6
matches intent
ChecklistCard
template		teach44.2–52.300000000000004skinetic-buildicon·color♪ node_lock
Make every commit do one thing for one reason, so when something breaks you can read the history like a confession.
on-screen: One commit, one reason
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→One commit, one reasoncurate items, nodes
7s7
matches intent
StatScoreboard
template		proof52.3–60.699999999999996sreceipts-counticon·color♪ node_lock
We helped a client trace a bug to one small commit in minutes, because the changes were small enough to actually read.
on-screen: A bug traced in minutes, not days
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→A bug traced in minutes, not dayscurate pillar, stats, statsLabels
8s8
matches intent
AnnotatedDiagram
template		step60.7–69.10000000000001skinetic-buildicon·color♪ node_lock
Your step: make your next change smaller than feels worth it, wrap it in one test, and ship it before you second-guess.
on-screen: Step: shrink the change, add the test
expected on screen: white ground · a AnnotatedDiagram panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape boxground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Step: shrink the change, add the testcurate callouts, stages, steps
9s9
matches intent
shared field
signature-3d		resolve69.1–76.8scoalescenceicon·color♪ bed_out
Slow is smooth and small is fast in software, and that unglamorous rhythm is what The Big T-M builds on.
on-screen: Small and steady wins
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→Small and steady wins

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)

tiktokBig software launches hide big risk — 1,000 changes at once means 1,000 suspects when it breaks. The fix: ship small, ship often. Every change behind one automated test. One commit, one reason. We traced a client's bug to one commit in minutes, not days.
instagramShip small. Ship often. One commit, one reason. Every change behind one test. Then a bug is a tiny thing to debug. #softwaredevelopment #coding #devops #engineering #temerarii
linkedinSoftware used to ship once a year in a big nervous launch — and every bug waited twelve months for its apology. The trouble with a big launch is that risk hides inside it: a thousand changes at once means a thousand suspects when it breaks. The discipline that still wins: ship small and ship often, because a tiny change is a tiny thing to debug. Put every change behind an automated test so the robot catches the obvious break, not the customer. Keep humans on the gnarly logic — judgment doesn't fit in an assertion. And make every commit do one thing for one reason, so history reads like a confession. We helped a client trace a bug to one small commit in minutes, because the changes were small enough to read. Slow is smooth, and small is fast.
xBig launches hide big risk: 1,000 changes = 1,000 suspects when it breaks. Ship small, ship often. Every change behind one test. One commit, one reason. We traced a bug in minutes, not days. temerarii.com
facebookSoftware used to ship once a year in a big nervous launch, and every bug waited twelve months for its apology. The trouble: a thousand changes at once means a thousand suspects when it breaks. The discipline that wins: ship small and ship often, put every change behind an automated test, and make every commit do one thing for one reason. We helped a client trace a bug to one small commit in minutes. Want software you can actually debug? Message us.
threadsBig launches hide big risk: 1,000 changes at once means 1,000 suspects when it breaks. Ship small, ship often. Every change behind one automated test. One commit, one reason — so history reads like a confession. We traced a bug to one commit in minutes, not days. Slow is smooth, small is fast.
pinterestSoftware development best practices: ship small and often, put every change behind an automated test, and make each commit do one thing for one reason. Continuous delivery, clean commits, test-driven development, debugging, engineering discipline, software process.
blueskyBig launches hide big risk: 1,000 changes = 1,000 suspects when it breaks. Ship small, ship often. Every change behind one test. One commit, one reason. We traced a bug in minutes, not days. temerarii.com
youtubeSoftware Development: Ship Small, Ship Often Software used to ship once a year in a big nervous launch, and every bug waited twelve months for its apology. The trouble: a thousand changes at once means a thousand suspects when it breaks. The discipline that still wins: ship small and ship often, because a tiny change is a tiny thing to debug. Put every change behind an automated test, keep humans on the gnarly logic, and make every commit do one thing for one reason. We helped a client trace a bug to one small commit in minutes. Slow is smooth, small is fast — built by The Big T-M.

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

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