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-W41-Frikind longformweek W41date 2026-10-16campaign longform-youtubepillar strategic_relationsbeat asset videoduration 136.1sground 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-W41-Fri 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 · 136.1s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–22.0sspatial-parallaxicon·liquid-chrome♪ bed_in
One system across surfaces, and today the surface that does not glow. Print. Screens forgive a lot. Paper forgives nothing. Once it is printed, it is wrong forever. So I will show you how to take the same brand file you use on screen and turn it into a print-ready file the right way, with the model doing the setup.
on-screen: The brand on paper
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→The brand on paper
2s2
matches intent
NumberedList
template
teach22.0–43.6skinetic-buildicon·white-knockout♪ node_lock
First, do not rebuild the brand for print. Generate the print piece from the same tokens that drive your website. The colors, the fonts, the spacing all come from one source. The only thing that changes is the output format. If your card and your homepage disagree on the red, it is because someone made two sources. Keep one.
on-screen: Build print from the same file
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Build print from the same filecurate items, nodes
3s3
matches intent
ChecklistCard
template
teach43.6–69.9skinetic-buildicon·liquid-chrome♪ node_lock
Second, learn two print words and bake them in. Bleed is extra art past the cut line so a tiny slip in the cutting machine does not leave a white edge. Safe margin is keeping your text away from that edge so it never gets trimmed off. We set both as numbers in the layout code, so every print file the model builds already has them. The printer stops sending things back.
on-screen: Set bleed and safe margins
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Set bleed and safe marginscurate items, nodes
4s4
matches intent
BlueprintGrid
template
teach69.9–95.4skinetic-buildicon·white-knockout♪ node_lock
Third, fix the color before it ships. Screens mix light. Printers mix ink, and ink uses a different color recipe called CMYK. A red that sings on a screen can come out muddy on paper. We convert to the print color profile as a step in the build, so what comes off the press matches the brand instead of surprising you. You handle this once in code, not by hoping.
on-screen: Convert color for ink
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Convert color for inkcurate nodes, rows
5s5
matches intent
LegacyCard
template
proof95.4–113.80000000000001sreceipts-counticon·liquid-chrome♪ node_lock
Proof, honestly. The same brand file that renders our screens is the file our print pieces come from. No separate print brand, no second set of colors that slowly drifts. One source survives the jump from glowing screen to inked paper, and that is the only proof that matters here.
on-screen: Our brand survives the press
expected on screen: red ground · a LegacyCard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our brand survives the presscurate statsLabels
6s6
matches intent
shared field
signature-3d
resolve113.8–136.1scoalescenceicon·liquid-chrome♪ bed_out
So print is the same brand, prepared for ink. Build it from the same tokens, set your bleed and safe margins as numbers, and convert the color for the press before it ships. You can see how we keep one brand across screen and paper at office.temerarii.xyz. That is The Big T-M, the same on the page as on the wire.
on-screen: See print done from one source
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→See print done from one source

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)

youtubeHow to take one brand file from screen to print without it breaking Screens forgive a lot. Paper forgives nothing. Once it is printed, it is wrong forever. This video shows how to take the same brand file you use on screen and turn it into a print ready file the right way, with the model doing the setup. The method: Do not rebuild the brand for print. Generate the print piece from the same tokens that drive your website, the colors, the fonts, the spacing. The only thing that changes is the output format. If your card and your homepage disagree on the red, someone made two sources. Keep one. Learn two print words and bake them in. Bleed is extra art past the cut line so a small slip in the cutting machine does not leave a white edge. Safe margin keeps your text away from that edge so it never gets trimmed off. Set both as numbers in the layout code, so every print file already has them and the printer stops sending things back. Convert the color for ink. Screens mix light. Printers mix ink with a recipe called CMYK. A red that sings on screen can come out muddy on paper. Convert to the print color profile as a step in the build, so what comes off the press matches the brand instead of surprising you. The same brand file that renders our screens is the file our print pieces come from. No separate print brand, no second set of colors that drifts. See how we keep one brand across screen and paper at office.temerarii.xyz. Keywords: print design, CMYK, bleed and safe margin, brand tokens, design to print, prepress.

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