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-Frikind longformweek W26date 2026-07-03campaign longform-youtubepillar brandbeat asset videoduration 119.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-W26-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 · 119.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–23.4sspatial-parallaxicon·white-knockout♪ bed_in
If it works on us, it works for you. Today, print. People think print is the old, dead part of branding. It is not. It is the strict part. A screen forgives a wrong color. Paper does not. Today I will show you how we treat print as a precise version of the same code system, so what you design is what gets pressed.
on-screen: Print is just precise rules
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Print is just precise rules
2s2
matches intent
NumberedList
template
teach23.4–43.599999999999994skinetic-buildicon·white-knockout♪ node_lock
First move: build the piece at the real print size and resolution from the start, not a screen guess blown up later. Because we lay out in code, we set the exact dimensions once. A card is the card's true size. The agent works at that scale, so nothing gets soft when it hits paper.
on-screen: Build at the size it prints
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Build at the size it printscurate items, nodes
3s3
matches intent
ChecklistCard
template
teach43.6–64.5skinetic-buildicon·liquid-chrome♪ node_lock
Second move: pin the color so it does not shift. Our brand red is one value in the token file, and print pulls from that same value. You are not picking red twice and hoping they match. One source feeds the screen and the press, so the red on the flyer is the red on the site.
on-screen: Keep the color honest
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Keep the color honestcurate items, nodes
4s4
matches intent
BlueprintGrid
template
teach64.5–85.0skinetic-buildicon·white-knockout♪ node_lock
Third move: export the final as a clean, press-ready file straight from the build. The agent lays out the type, places the SVG mark, applies the tokens, and outputs the file. No round-trip through three apps where a setting gets lost. The same machine that makes the post makes the printable, from one set of rules.
on-screen: Render print-ready files in code
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Render print-ready files in codecurate nodes, rows
5s5
matches intent
RankList
template
proof85.0–102.7sreceipts-counticon·liquid-chrome♪ node_lock
The proof: our print pieces and our screen pieces come from the same token file and the same mark, in public. They match because they share a source, not because someone checked them side by side. You can see both living together at office dot temerarii dot xyz.
on-screen: Same rules, screen and paper
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Same rules, screen and papercurate rows, statsLabels
6s6
matches intent
shared field
signature-3d
resolve102.7–119.30000000000001scoalescenceicon·white-knockout♪ bed_out
Your next step: set the true print size up front, pull color from one shared value, and export press-ready straight from the build. See it at office dot temerarii dot xyz. Print stops being scary when it reads from the same brain as everything else.
on-screen: Make print share your source
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Make print share your 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)

youtubePrint Is Just Precise Rules: Build at Real Size, Keep Color Honest Print scares people because it feels final. This video reframes it: print is just precise rules, and once you write them down a machine can hit them every time. What you will learn: - Build at the size it prints: set the layout to the real paper dimensions from the start, so nothing has to be rescaled and broken later. - Keep the color honest: account for the gap between a glowing screen and ink on paper, so what you approve is what comes back. - Render print-ready files in code: produce the final file the same way you build a page, so it is repeatable and editable, not locked in one app. Then the proof: same rules, screen and paper. Because the print piece and the web page share one source, the brand reads identically across both. Make print share your source and the two stop drifting. Keywords: print design, print-ready files, color management, design source, brand consistency. See the whole system run in public at temerarii.xyz.

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