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-W26-Monkind longformweek W26date 2026-06-29campaign longform-youtubepillar it_devbeat asset videoduration 158.8sground blackscenes 8

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W26-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 8 scenes · 158.8s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–27.7sspatial-parallaxicon·white-knockout♪ bed_in
If it works on us, it works for you. Today, the logo. Most people think a logo is a pretty picture you commission once and frame. It is not. A logo is a set of rules: where it sits, how small it can go, what it must never touch. Today I will show you how we treat our own mark as code, so it behaves the same on a phone, a sign, and a video frame.
on-screen: A logo is a rule, not art
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→A logo is a rule, not art
2s2
matches intent
NumberedList
template
teach27.7–52.2skinetic-buildicon·ember-fill♪ node_lock
First move: save the logo as an SVG, not a flat picture. SVG is just text that describes shapes, so it stays sharp at any size and you can recolor it with one line. We keep our mark, the white lockup, as a single file every tool points to. One file, one truth. When the mark changes, it changes everywhere, because everything reads from that one path.
on-screen: Store the mark as one SVG
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Store the mark as one SVGcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach52.2–77.4skinetic-buildicon·wireframe♪ node_lock
Second move: write the placement rules in plain text next to the file. Ours says one clear rule we live by: show the mark, never spell the name typed onto the art. We enforce that with a small check we call verify-no-written-name. It scans a piece and fails it if the wordmark got typed in by hand. A rule a machine can check is a rule that actually holds.
on-screen: Write down where it can go
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write down where it can gocurate items, nodes
4s4
matches intent
JsonDiff
template
teach77.4–102.60000000000001skinetic-buildicon·white-knockout♪ node_lock
Third move: hand the SVG and the rules to the coding agent. Now when it builds a post or a video, it drops the mark in the right corner, at the right size, every time. You are not nudging a logo by hand across a hundred files. The agent reads the placement rule once and obeys it forever. That is the difference between a logo and a logo system.
on-screen: Let the agent place it for you
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let the agent place it for youcurate fileName, lines, nodes
5s5
matches intent
StackTrace
template
teach102.6–122.8skinetic-buildicon·liquid-chrome♪ node_lock
Here is the self-proof. Our mark runs through this exact pipeline on every single piece we publish. Same SVG, same rules, same check. It sits on black grounds, white grounds, and red grounds without breaking. We did not test it in a slide deck. We tested it by shipping it, in public, over and over.
on-screen: It survived our own machine
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→It survived our own machinecurate errMsg, errType, fix, frames, nodes
6s6
matches intent
ListCard
template
teach122.8–144.8skinetic-buildicon·ember-fill♪ node_lock
Your next step is small. Get your logo as an SVG. Write three placement rules in plain text. Add one check that catches misuse. Then let an agent place it for you. You can see our mark living across the whole calendar at office dot temerarii dot xyz. A logo that follows rules is a logo that keeps its promise.
on-screen: Treat your mark like ours
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Treat your mark like ourscurate items, nodes
7s7
matches intent
KpiGrid
template
proof144.8–152.5sreceipts-counticon·wireframe♪ node_lock
Chapter six. Custom apps and dashboards: own the code and the IP, so no vendor can hold your tools hostage.
on-screen: Chapter 6
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Chapter 6curate kpis, statsLabels
8s8
matches intent
shared field
signature-3d
resolve152.5–158.8scoalescenceicon·white-knockout♪ bed_out
Chapter seven is next. We tie every dollar you spend to a result you can see.
on-screen: Chapter 7
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Chapter 7

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)

youtubeA Logo Is a Rule, Not Art: Store One SVG and Let the Agent Place It This video treats the logo as a rule the machine enforces, not a piece of art someone places by feel. What you will learn: - Store the mark as one SVG: a single vector file is the truth, so every use pulls the same shape. - Write down where it can go: define the grounds and placements the mark is allowed on, as rules, so nothing is left to taste. - Let the agent place it for you: with the file and the rules written down, the agent drops the mark correctly without a person babysitting each asset. - It survived our own machine: the mark went through our full pipeline untouched and held. Then the proof: treat your mark like ours. One SVG, clear placement rules, and an agent that obeys them means the logo reads the same on every surface, because there is nothing for it to drift into. Keywords: SVG logo, brand rules, logo placement, vector source, automation, brand consistency. See the whole system run in public at temerarii.xyz.

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