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 thread-field-notes-W43-Satkind threadweek W43date 2026-10-31campaign thread · Satpillar multimediabeat Satasset videoduration 26.7sground redscenes 5

Checklist the per-video bar — engine/sim

83.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-field-notes-W43-Sat good|bad)
⚠ 5 flag(s) — not yet ship-ready: low_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template ListCard
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 5 scenes · 26.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–6.2skinetic-buildicon·liquid-chrome♪ node_lock
Field note. You hand-edited thirty near-identical videos. The computer should have done twenty-nine of them.
on-screen: Editing 30 videos by hand
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Editing 30 videos by hand
2s2
matches intent
NumberedList
template
teach6.2–11.7skinetic-buildicon·white-knockout♪ node_lock
Old way: open the editor, swap the text, export, thirty times.
on-screen: One row, one video
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→One row, one videocurate items, nodes
3s3
matches intent
StackTrace
template
diff11.7–16.7scrossfade-8ficon·liquid-chrome♪ node_lock
If your videos differ only by text, make them rows and loop the render.
on-screen: Turn variants into rows
expected on screen: red ground · a StackTrace panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Turn variants into rowscurate codeLines, errMsg, errType, fix, frames
4s4
first render · fix pending
WireframeMock
templatedead_airgeneric_scene
proof16.7–21.7sreceipts-counticon·white-knockout♪ node_lock
Field Notes
expected on screen: red ground · a WireframeMock panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual receiptsshape octaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Field Notescurate statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve21.7–26.7scoalescenceicon·white-knockout♪ bed_out
Field Notes
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Field Notes

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)

tiktokField note: you hand-edited 30 near-identical videos. The computer should have done 29 of them. If your videos differ only by text, make them rows in a sheet and loop the render. One row, one video. (AI-assisted)
instagramField note. You edited 30 near-identical videos by hand. The computer should have done 29. One row, one video. If they differ only by text, make them rows. #automation #videoediting #remotion #buildinpublic #fieldnotes
linkedinField note: you hand-edited thirty near-identical videos. The computer should have done twenty-nine of them. The old way: open the editor, swap the text, export, thirty times. That is a loop a machine should run, not a person. If your videos differ only by text, make them rows in a sheet and loop the render. One row, one video. The rule of thumb: when the work is identical except for the data, turn the data into rows and automate the rest.
xField note: you hand-edited 30 near-identical videos. The computer should have done 29. If they differ only by text, make them rows and loop the render. temerarii.xyz
facebookA quick field note: if you just hand-edited thirty near-identical videos, the computer should have done twenty-nine of them. The old way is open the editor, swap the text, export, thirty times. If your videos differ only by text, make them rows in a sheet and loop the render. More at temerarii.xyz.
threadsField note: you hand-edited thirty near-identical videos. The computer should have done twenty-nine of them. The old way was open the editor, swap the text, export, thirty times. If your videos differ only by text, make them rows in a sheet and loop the render. One row, one video.
pinterestVideo automation field note: stop hand-editing near-identical videos one at a time. If your videos differ only by text, turn the variants into rows in a spreadsheet and loop the render so one row produces one video. A practical data-driven approach to batch video production.
blueskyField note: you hand-edited 30 near-identical videos. The computer should have done 29. If they differ only by text, make them rows and loop the render.
youtubeTitle: Field Note: Stop Hand-Editing 30 Near-Identical Videos If you just hand-edited thirty near-identical videos, the computer should have done twenty-nine of them. The old way is open the editor, swap the text, export, thirty times. The fix: if the videos differ only by text, make them rows in a sheet and loop the render, one row per video. More at temerarii.xyz.

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