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-W32-Monkind longformweek W32date 2026-08-10campaign longform-youtubepillar socialbeat asset videoduration 138.6sground blackscenes 8

Checklist the per-video bar — engine/sim

93.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W32-Mon good|bad)
⚠ 4 flag(s) — not yet ship-ready: copy_genericgeneric_scenecustom_element_dup · 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 · 138.6s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–19.8sspatial-parallaxicon·ember-fill♪ bed_in
People think a logo is a picture. It is a system. One mark that has to survive a hundred sizes and stay itself. Today I am going to show you how The Big T-M builds a logo identity that holds up, using a model to do the boring, brutal checking a human eye misses.
on-screen: The logo is a system
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→The logo is a system
2s2
matches intent
NumberedList
template
teach19.8–40.7skinetic-buildicon·ember-fill♪ node_lock
Start with constraints, not sketches. I open the terminal and have the model write the rule sheet: one shape, one color minimum, readable at sixteen pixels, no thin lines that vanish when printed. These rules are the brief for the mark. If you draw before you write the rules, you fall in love with the wrong thing.
on-screen: Write the rules before the shape
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape torusground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Write the rules before the shapecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach40.7–62.7skinetic-buildicon·wireframe♪ node_lock
I do not hand-draw the mark. I describe it and let the model output it as an SVG, which is just math for a shape. Because it is code, I can change one number and re-render instantly. Ten variants in a minute. I keep the ones that read clean and delete the rest without guilt, since making another costs nothing.
on-screen: Generate the geometry as code
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Generate the geometry as codecurate items, nodes
4s4
matches intent
SchematicCard
template
teach62.7–86.1skinetic-buildicon·white-knockout♪ node_lock
Now the cruel part. I have the model render the mark at favicon size, on red, on black, on white, blurred, and in one color. This is where most logos die. If it turns to mush at sixteen pixels, it is not a logo, it is an illustration. The model shows me every failure at once so I fix the shape, not the excuse.
on-screen: Test it small and wrong
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape torusground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Test it small and wrongcurate nodes
5s5
matches intent
PipelineMap
template
teach86.1–107.69999999999999skinetic-buildicon·liquid-chrome♪ node_lock
Our mark went through exactly this. It is logo-only on purpose, we never spell the name onto an asset, because a wordmark you have to read at speed is a wordmark nobody reads. You can see it sitting on the office page, the cards, the video corners, the same shape everywhere. That consistency is the proof, not a chart.
on-screen: We use our own mark daily
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual node-graphshape torusground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→We use our own mark dailycurate nodes, stages
6s6
matches intent
DiffCard
template
teach107.7–128.6skinetic-buildicon·ember-fill♪ node_lock
A logo identity is rules, then geometry, then a beating at small sizes, then living on real surfaces. The model does the checking faster and more honestly than a tired eye at 5pm. Go see ours holding its shape across the whole site at office.temerarii.xyz, then write your rule sheet first. The shape comes easy after that.
on-screen: See the marks at office.temerarii.xyz
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape torusground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→See the marks at office.temerarii.xyzcurate lines, nodes
7s7
first render · fix pending
RankList
templategeneric_scenecustom_element_dup
proof128.6–133.6sreceipts-counticon·wireframe♪ node_lock
Social at scale: one story, nine native channels
on-screen: Chapter 6
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Chapter 6curate rows, statsLabels
8s8
first render · fix pending
shared field
signature-3dgeneric_scene
resolve133.6–138.6scoalescenceicon·ember-fill♪ bed_out
Social at scale: one story, nine native channels
on-screen: Chapter 7
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment ember-fillmotion 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)

youtubeBuild a logo that survives small sizes by writing the rules before the shape People think a logo is a picture. It is a system: one mark that has to survive a hundred sizes and stay itself. This walks through building a logo identity that holds up, using a model to do the brutal checking a tired eye misses. What you learn: - Write the rule sheet first: one shape, one color minimum, readable at sixteen pixels, no thin lines that vanish when printed. The rules are the brief. Draw before you write them and you fall in love with the wrong thing. - Describe the mark and let the model output it as an SVG, which is just math for a shape. Change one number, re-render, get ten variants in a minute, and delete the rest without guilt. - Render the mark at favicon size, on red, on black, on white, blurred, and in one color. This is where most logos die. If it turns to mush at sixteen pixels, it is an illustration, not a logo. Our own mark went through exactly this. It is logo-only on purpose: we never spell the name onto an asset, because a wordmark you read at speed is one nobody reads. See it holding its shape across the whole site at office.temerarii.xyz, then write your rule sheet first. Keywords: logo design, SVG logo, favicon test, brand identity rules, scalable mark

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