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 longform-W50-Satkind longformweek W50date 2026-12-19campaign longform-youtubepillar multimediabeat asset videoduration 164.5sground whitescenes 7

Checklist the per-video bar — engine/sim

98.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W50-Sat good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
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 7 scenes · 164.5s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–25.2sspatial-parallaxicon·color♪ bed_in
Today closes the week with brand systems, the part that makes everything else stay consistent. We are building a small kit so your brand looks like itself no matter who is making the work or what tool they use. By the end your team will have templates and rules that any person, or any agent, can follow. Open the workspace. We start with the pieces you repeat the most.
on-screen: Package the brand to travel
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Package the brand to travel
2s2
matches intent
NumberedList
template
teach25.2–48.2skinetic-buildicon·color♪ node_lock
First move: spot the repeats. Look at last month's work and find the shapes you rebuild over and over. The social post frame, the email header, the one-slide pitch. Those are your templates waiting to be born. We have your team list five things they remake from scratch each week. Anything you build twice the same way should be built once and reused.
on-screen: Find what you remake every time
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Find what you remake every timecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach48.2–73.4skinetic-buildicon·color♪ node_lock
Second move: build the templates. We take those five shapes and make a clean reusable version of each, with your colors, fonts, and spacing locked in. The team fills the template with words, not with design decisions. We also write the small rules in plain English, like always use the logo alone, never type the brand name onto an image. Rules a person and a model can both follow.
on-screen: Turn rules into reusable templates
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Turn rules into reusable templatescurate items, nodes
4s4
matches intent
DiffCard
template
teach73.4–97.2skinetic-buildicon·color♪ node_lock
Third move: hook the templates to the agent. We feed your brand rules and templates to the model, then ask it to fill one out for a real post. It stays inside the lines because the lines are written down. Your team edits the words and ships. New work now starts on brand by default, instead of someone trying to remember the rules from memory.
on-screen: Let the agent fill the template
expected on screen: white ground · a DiffCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Let the agent fill the templatecurate lines, nodes
5s5
matches intent
LogStream
template
teach97.2–121.0skinetic-buildicon·color♪ node_lock
Honest proof: The Big T-M builds every asset from one locked brand system. Hundreds of pieces across the calendar, each one held to the same voice, colors, and logo rule, all from one source. We do not police consistency by hand. We wrote the rules down once and let the system carry them. That is what your kit does for you, at your own scale.
on-screen: Hundreds of assets, one voice
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Hundreds of assets, one voicecurate nodes, rows
6s6
matches intent
StatScoreboard
template
proof121.0–141.5sreceipts-counticon·color♪ node_lock
The takeaway: a brand system is your rules and your shapes written down, so consistency stops depending on one person's memory. Do that and you can grow the work without losing the look. Your team now has the kit and the rules to keep it alive. See ours in full at office dot temerarii dot xyz.
on-screen: Write it down so it scales
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape octaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Write it down so it scalescurate pillar, stats, statsLabels
7s7
matches intent
shared field
signature-3d
resolve141.5–164.5scoalescenceicon·color♪ bed_out
That is the week. Growth, content, data, automation, and the brand kit that ties it together, all taught by doing, all left in your hands. The point was never to watch us work. It was to leave your team shipping real value on their own. Come see the whole system running in public at office dot temerarii dot xyz, then go run yours.
on-screen: You can run this now
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→You can run this now

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

Social captions supplemental published copy · per channel (comp_id level)

youtubeBrand systems: build a kit so your work looks like itself every time Brand systems make everything else stay consistent. This video builds a small kit so your brand looks like itself no matter who is making the work or what tool they use. The moves: - Find what you remake every time. Look at last month's work and spot the shapes you rebuild over and over: the social post frame, the email header, the one-slide pitch. Those are your templates waiting to be born. Anything you build twice the same way should be built once and reused. - Turn rules into reusable templates. Make a clean version of each shape, with your colors, fonts, and spacing locked in. The team fills the template with words, not design decisions. Write the small rules in plain English, like always use the logo alone, never type the brand name onto an image. Rules a person and a model can both follow. - Let the agent fill the template. Feed your brand rules and templates to the model, then ask it to fill one out for a real post. It stays inside the lines because the lines are written down. New work starts on brand by default, instead of someone trying to remember the rules from memory. The honest proof: every asset we make comes from one locked brand system. Hundreds of pieces across the calendar, each held to the same voice, colors, and logo rule, all from one source. We do not police consistency by hand; we wrote the rules down once and let the system carry them. A brand system is your rules and shapes written down, so consistency stops depending on one person's memory. See ours in full at office.temerarii.xyz Keywords: brand system, reusable templates, design tokens, brand rules, logo usage, consistent content at scale

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