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-W39-Mon-3kind threadweek W39date 2026-09-28campaign thread · Monpillar strategic_relationsbeat Monasset videoduration 46.1sground 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-W39-Mon-3 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 · 46.1s · 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.0sspatial-parallaxicon·white-knockout♪ bed_in
Soon you will describe a tool and watch the software build itself.
on-screen: Soon you describe, it builds
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Soon you describe, it builds
2s2
matches intent
shared field
signature-3d		hook5.0–10.2skinetic-buildicon·white-knockout♪ node_lock
The hard part stops being syntax and becomes knowing what to ask for.
on-screen: The hard part moves up
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→The hard part moves up
3s3
matches intent
NumberedList
template		teach10.2–15.2skinetic-buildicon·liquid-chrome♪ node_lock
The old way meant typing every line and hunting every missing comma.
on-screen: Old way: type every line
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Old way: type every linecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof15.2–20.2sreceipts-counticon·white-knockout♪ node_lock
Now an AI writes the first pass while you steer the design.
on-screen: Now: AI writes the first pass
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Now: AI writes the first passcurate colA, colB, rows, statsLabels
5s5
matches intent
BuildLog
template		diff20.2–25.2scrossfade-8ficon·liquid-chrome♪ node_lock
Your real job shifts to reviewing, testing, and catching the lies.
on-screen: You become the reviewer
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→You become the reviewercurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach25.2–30.7skinetic-buildicon·white-knockout♪ node_lock
Soon you describe the test you want, and the code shapes itself to pass.
on-screen: Describe the test, not the code
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Describe the test, not the codecurate items, nodes
7s7
matches intent
KpiGrid
template		proof30.7–35.7sreceipts-counticon·liquid-chrome♪ node_lock
The plain-English spec becomes the thing that actually runs the build.
on-screen: Specs become the source
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Specs become the sourcecurate kpis, statsLabels
8s8
matches intent
SchematicCard
template		step35.7–40.900000000000006skinetic-buildicon·white-knockout♪ node_lock
So practice writing a crisp spec now. That skill is the real moat.
on-screen: Step: write a clear spec first
expected on screen: red ground · a SchematicCard panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual pipelineshape tetraground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Step: write a clear spec firstcurate nodes, stages, steps
9s9
matches intent
shared field
signature-3d		resolve40.9–46.1scoalescenceicon·white-knockout♪ bed_out
In this future, clear thinking is the most valuable code you can write.
on-screen: Clear thinking is the new code
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Clear thinking is the new code

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)

tiktokSoon you describe a tool and the software builds itself. The new skill is not syntax, it is the spec. Here is why. (AI-assisted)
instagramDescribe the test, not the code. The spec becomes the source. You become the reviewer. Clear thinking is the new code. #softwaredevelopment #coding #ai #developers #temerarii
linkedinThe future of software development moves the hard part up a level: away from syntax and toward knowing what to ask for. AI writes the first pass, your job shifts to reviewing, testing, and catching the lies, and the plain-English spec becomes the thing that runs the build. Practice writing a crisp spec now. That skill is the real moat.
xSoon you describe the test and code shapes itself to pass. The spec becomes the source. Clear thinking is the new code. tmstudio.link/software
facebookSoon you will describe a tool and watch software build itself. The hard part stops being syntax and becomes knowing exactly what to ask for. AI writes the first pass, you review and catch the lies, and your plain-English spec runs the build. Start practicing crisp specs now. Curious? Comment BUILD.
threadsSoon you describe the test you want and the code shapes itself to pass. The hard part moves from syntax to the spec. Practice writing a crisp spec now, because clear thinking is the new code.
pinterestFuture of software development: AI writes the first pass and the plain-English spec becomes the source. Learn to write crisp specs, review and test the output. AI coding, developer skills, software engineering, spec-driven development.
blueskySoon you describe the test and code shapes itself to pass. The spec becomes the source. Clear thinking is the new code. tmstudio.link/software
youtubeThe New Coding Skill Is Not Syntax, It Is The Spec The future of software development moves the hard part up a level: away from typing every line and toward knowing what to ask for. In this short we show how AI writes the first pass while you steer the design, your job shifts to reviewing and testing, and the plain-English spec becomes the thing that runs the build. Practice writing a crisp spec now. AI-assisted production. Chapters: describe and it builds, hard part moves up, you become the reviewer, the spec is the source. #softwaredevelopment #aicoding #developers

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

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