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-W33-Wed-1kind threadweek W33date 2026-08-19campaign thread · Wedpillar multimediabeat Wedasset videoduration 64.3sground blackscenes 9

Checklist the per-video bar — engine/sim

84.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W33-Wed-1 good|bad)
⚠ 4 flag(s) — not yet ship-ready: copy_generictoo_complexdup_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 · 64.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–7.7sspatial-parallaxicon·ember-fill♪ bed_in
We are close to a point where your automations live as plain code, not boxes you drag around a screen.
on-screen: Soon your workflow is just code
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Soon your workflow is just code
2s2
matches intent
shared field
signature-3d		hook7.7–14.7skinetic-buildicon·wireframe♪ node_lock
Old way, your logic hid inside a tangle of colored boxes that only one person on earth understood.
on-screen: The old way: a maze of nodes
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→The old way: a maze of nodes
3s3
matches intent
NumberedList
template		teach14.7–22.4skinetic-buildicon·wireframe♪ node_lock
Here is the move: turn each step into a typed object, so the data shape is checked before anything runs.
on-screen: Make every step a typed object
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Make every step a typed objectcurate items, nodes
4s4
matches intent
ComparisonTable
template		proof22.4–29.4sreceipts-counticon·wireframe♪ node_lock
When the shape is wrong, it fails loudly at the door, instead of quietly poisoning your data downstream.
on-screen: Bad data fails loud, not silent
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Bad data fails loud, not silentcurate colA, colB, rows, statsLabels
5s5
matches intent
StackTrace
template		diff29.4–36.699999999999996scrossfade-8ficon·wireframe♪ node_lock
A wall of boxes hides the bugs. Code you can read, diff, and test lets you actually find them.
on-screen: Code you can read beats boxes
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape octaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Code you can read beats boxescurate codeLines, errMsg, errType, fix, frames
6s6
matches intent
ChecklistCard
template		teach36.7–44.400000000000006skinetic-buildicon·wireframe♪ node_lock
Now hand the model your data shape and let it write the typed step, validation and all, in one pass.
on-screen: Let the model write the typed step
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the model write the typed stepcurate items, nodes
7s7
matches intent
KpiGrid
template		proof44.4–50.699999999999996sreceipts-counticon·wireframe♪ node_lock
The step comes back tested and version-tracked, so you can see exactly what changed and when.
on-screen: Generated, tested, version-tracked
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape octaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Generated, tested, version-trackedcurate kpis, statsLabels
8s8
matches intent
BlueprintGrid
template		step50.7–58.0skinetic-buildicon·wireframe♪ node_lock
Three steps: define the data as a typed object, validate at every edge, keep it all in version control.
on-screen: Step: type it, validate, version
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape octaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Step: type it, validate, versioncurate rows, stages, steps
9s9
matches intent
shared field
signature-3d		resolve58.0–64.3scoalescenceicon·ember-fill♪ bed_out
Stop renting someone's canvas. Own your logic as code, and it outlives whatever tool was trendy.
on-screen: Own the logic, not the canvas
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Own the logic, not the canvas

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)

tiktokYour automations should be code, not boxes you drag around. (AI-assisted) The move: turn each step into a TYPED object so the data shape is checked before it runs. Bad data fails loud at the door, not silently downstream. Hand the model your shape, it writes the typed step.
instagramWorkflows as code, not a maze of boxes. Make each step a typed object. Validate the data shape at the door. Version everything. #python #automation #typedcode #devtools #buildinpublic
linkedinWe're close to a point where your automations live as plain code, not boxes you drag around a screen. The move: turn each step into a typed object, so the data shape is checked before anything runs. When the shape is wrong, it fails loudly at the door instead of quietly poisoning your data downstream. A wall of boxes hides bugs. Code you can read, diff, and test lets you find them. Hand the model your data shape and let it write the typed step, validation and all, returned tested and version-tracked. Stop renting someone's canvas. Own your logic as code, and it outlives whatever tool was trendy.
xAutomations should be code, not boxes you drag. Make each step a typed object so the data shape is checked before it runs. Bad data fails loud at the door, not silently downstream. Own the logic, not the canvas. temerarii.com
facebookYour automations should be code, not a maze of dragged boxes. Turn each step into a typed object so the data shape is checked before it runs, failing loud at the door instead of poisoning your data downstream. Own your logic as code and it outlives any trendy tool. temerarii.com
threadsAutomations should be code, not boxes you drag around. Make each step a typed object so the data shape is checked before it runs. Bad data fails loud at the door, not silently downstream. Own the logic, not the canvas.
pinterestMove workflows from no-code boxes to typed Python: make each step a typed object, validate the data shape before it runs, and keep everything in version control. Workflow as code, typed automation, Pydantic workflows, no-code to code migration, dev best practices.
blueskyAutomations should be code, not boxes you drag. Make each step a typed object so the data shape is checked before it runs. Bad data fails loud at the door, not silently downstream. Own the logic, not the canvas. temerarii.com
youtubeFrom No-Code Boxes to Typed Python Workflows We're close to automations that live as plain code, not boxes you drag around a screen. This short shows the move: turn each step into a typed object so the data shape is checked before anything runs. When the shape is wrong, it fails loudly at the door instead of quietly poisoning your data downstream. Hand the model your data shape and let it write the typed step, returned tested and version-tracked. Stop renting someone's canvas. Own your logic as code, and it outlives whatever tool was trendy. #python #automation #devtools

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

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