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-W35-Sat-2kind threadweek W35date 2026-09-05campaign thread · Satpillar strategic_relationsbeat Satasset videoduration 59.7sground whitescenes 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-W35-Sat-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 · 59.7s · 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.3sspatial-parallaxicon·color♪ bed_in
Old software builds spent six months coding before anyone found out if the thing was wanted.
on-screen: Six months to a maybe
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Six months to a maybe
2s2
matches intent
shared field
signature-3d		hook6.3–12.6skinetic-buildicon·color♪ node_lock
What is now possible is shipping the thinnest working slice first, then learning from real use.
on-screen: Ship the thinnest slice first
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Ship the thinnest slice first
3s3
matches intent
NumberedList
template		teach12.6–19.6skinetic-buildicon·color♪ node_lock
Pick the single job a user most needs done, and build only the path that gets them there.
on-screen: Find the one job that matters
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Find the one job that matterscurate items, nodes
4s4
matches intent
RankList
template		proof19.6–27.3sreceipts-counticon·color♪ node_lock
Put it in front of real users in days, because a spec cannot tell you what a person will skip.
on-screen: Real users, not a spec
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Real users, not a speccurate rows, statsLabels
5s5
matches intent
TerminalRun
template		diff27.3–33.9scrossfade-8ficon·color♪ node_lock
This is not one big bet, it is small loops, where each release teaches the next decision.
on-screen: Not a big bet, small loops
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape tetraground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Not a big bet, small loopscurate codeLines
6s6
matches intent
ChecklistCard
template		teach33.9–40.199999999999996skinetic-buildicon·color♪ node_lock
Let AI draft the boring plumbing, then a developer reviews every line before it ever ships.
on-screen: Let AI draft the boring code
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Let AI draft the boring codecurate items, nodes
7s7
matches intent
StatScoreboard
template		proof40.2–45.400000000000006sreceipts-counticon·color♪ node_lock
A faster loop means fewer months spent walking confidently in the wrong direction.
on-screen: Faster loop, fewer wrong turns
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Faster loop, fewer wrong turnscurate pillar, stats, statsLabels
8s8
matches intent
ListCard
template		step45.4–52.4skinetic-buildicon·color♪ node_lock
Step one is naming the one job to ship, before a single feature gets added to the pile.
on-screen: Define the one job first
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual pipelineshape tetraground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Define the one job firstcurate items, stages, steps
9s9
matches intent
shared field
signature-3d		resolve52.4–59.699999999999996scoalescenceicon·color♪ bed_out
Build small, learn fast, in front of real people. That is software the way The Big T-M does it.
on-screen: Learn in public, fast
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Learn in public, fast

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)

tiktokStop spending six months coding before you know it's wanted. Ship the thinnest working slice first: pick the one job a user most needs, build only the path to it, and put it in front of real users in days. AI can draft the boring plumbing; a dev reviews every line. (AI-assisted edit.)
instagramShip the thinnest slice first. Find the one job that matters. Real users in days, not a spec. Small loops, not a big bet. AI drafts, a dev reviews. #softwaredevelopment #buildinpublic #startup #coding #temerarii
linkedinTakeaway for software teams: ship the thinnest working slice first. Old builds spent six months coding before anyone found out if the thing was wanted. Instead, pick the single job a user most needs done and build only the path that gets them there. Put it in front of real users in days, because a spec can't tell you what a person will skip. This is small loops, not one big bet: each release teaches the next decision. Let AI draft the boring plumbing, but a developer reviews every line before it ships. A faster loop means fewer months walking confidently in the wrong direction.
xSoftware truth: stop coding six months before you know it's wanted. Ship the thinnest slice first, the one job a user needs, in front of real users in days. AI drafts the boring plumbing; a dev reviews every line. Small loops beat big bets. temerarii.com
facebookOld software builds spent six months coding before anyone found out if the thing was wanted. The better way: ship the thinnest working slice first. Pick the single job a user most needs, build only the path to it, and put it in front of real users in days. Let AI draft the boring plumbing, but a developer reviews every line. Small loops beat big bets. Name the one job first. More at temerarii.com.
threadsStop spending six months coding before you know it's wanted. Ship the thinnest working slice first: pick the one job a user most needs, build only the path to it, put it in front of real users in days. AI drafts the boring plumbing; a dev reviews every line. Small loops beat big bets.
pinterestSoftware development strategy: ship the thinnest working slice first, focus on the single job users need, test with real users in days, iterate in small loops, and use AI to draft boilerplate with developer review. Evergreen lean software and build-in-public guide.
blueskySoftware truth: stop coding six months before you know it's wanted. Ship the thinnest slice first, the one job a user needs, in front of real users in days. AI drafts the plumbing; a dev reviews every line. Small loops beat big bets. temerarii.com
youtubeLean Software: Ship the Thinnest Slice First Old software builds spent six months coding before anyone found out if the thing was wanted. What's now possible: ship the thinnest working slice first, then learn from real use. Pick the single job a user most needs done and build only the path that gets them there. Put it in front of real users in days, because a spec can't tell you what a person will skip. This is small loops, not one big bet. Let AI draft the boring plumbing, but a developer reviews every line before it ships. More at temerarii.com. #softwaredevelopment #buildinpublic #startup

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

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