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-W24-Monkind longformweek W24date 2026-06-15campaign longform-youtubepillar performancebeat asset videoduration 149.3sground redscenes 6

Checklist the per-video bar — engine/sim

98.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W24-Mon 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 6 scenes · 149.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–25.9sspatial-parallaxicon·white-knockout♪ bed_in
One machine, eight pillars, that is the week. Yesterday we built the brand rules. Today we zoom into one piece of them, the logo, and treat it as something a machine can draw exactly the same way every time. Most people save a logo as a flat picture and then it gets blurry, recolored, and stretched. We are going to teach you to keep yours as code so it never breaks.
on-screen: A logo is code, not art
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→A logo is code, not art
2s2
matches intent
NumberedList
template
teach25.9–52.9skinetic-buildicon·white-knockout♪ node_lock
Step one. Keep your logo as an SVG file, not a JPG. An SVG is just text, a list of lines and curves a computer reads. Open it and you can actually see the shapes spelled out. Because it is text, it stays sharp at any size, from a phone icon to a wall. The first move to a logo that never degrades is choosing the format that is made of instructions, not pixels.
on-screen: Save the mark as an SVG
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Save the mark as an SVGcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach52.9–79.9skinetic-buildicon·liquid-chrome♪ node_lock
Step two. To turn a drawing into clean code, run it through a tracer like vtrace, which reads the image and writes out the exact paths. We did this with our astronaut mark, then locked the result. The rule we learned the hard way: trace once, fix it by hand, and never let a tool re-read it again, because each reparse adds junk. You clean the code one time and treat it as final.
on-screen: Trace it once, then never reparse
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Trace it once, then never reparsecurate items, nodes
4s4
matches intent
ProcessFlow
template
teach79.9–102.9skinetic-buildicon·white-knockout♪ node_lock
Step three. Inside that SVG text, swap any color value for your named brand tokens from yesterday's file. Now the logo is wired to the same red, black, and white as everything else. Change the token, the logo changes with the brand, automatically. The mark stops being a separate asset somebody has to remember to update, and becomes part of the one system.
on-screen: Color it with your tokens
expected on screen: red ground · a ProcessFlow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Color it with your tokenscurate nodes, steps
5s5
matches intent
ComparisonTable
template
proof102.9–124.5sreceipts-counticon·liquid-chrome♪ node_lock
Our proof is the astronaut you see across our work. We traced it, cleaned the paths by hand, deleted only the parts we did not want, and signed it off as final. Since then it has gone into videos and pages untouched, and it looks identical everywhere. No redraws, no drift, no blurry copy floating around someone's downloads folder.
on-screen: Our astronaut, locked and signed off
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our astronaut, locked and signed offcurate colA, colB, rows, statsLabels
6s6
matches intent
shared field
signature-3d
resolve124.5–149.3scoalescenceicon·white-knockout♪ bed_out
So a logo is not a picture you protect, it is code you write once and stop touching. Save it as SVG, trace it clean, wire it to your color tokens, then lock it. Your next step: find your logo file, and if it is a JPG, get a real SVG made. You can see our locked mark living across the studio at office dot temerarii dot xyz.
on-screen: Lock yours at the office
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Lock yours at the office

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)

youtubeKeep Your Logo as Code So It Never Goes Blurry or Drifts Most people save a logo as a flat picture, then it gets blurry, recolored, and stretched. This video teaches you to keep yours as code so it never breaks. What you will learn: - Save the mark as an SVG: an SVG is just text, a list of lines and curves, so it stays sharp at any size from a phone icon to a wall. - Trace it once, then never reparse: run the drawing through a tracer like vtrace, clean the paths by hand one time, and treat the result as final. Each reparse adds junk. - Color it with your tokens: swap the color values inside the SVG for your named brand tokens, so changing the token changes the logo with the rest of the brand. Then the proof: our astronaut mark was traced, hand-cleaned, and signed off as final. Since then it has gone into videos and pages untouched and looks identical everywhere, with no redraws and no blurry copies in a downloads folder. Keywords: SVG logo, vector tracing, vtrace, design tokens, logo consistency, brand assets. See the whole system run in public at temerarii.xyz.

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