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-Frikind longformweek W24date 2026-06-19campaign longform-youtubepillar it_devbeat asset videoduration 170.5sground whitescenes 7

Checklist the per-video bar — engine/sim

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

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–24.1sspatial-parallaxicon·ember-fill♪ bed_in
One machine, eight pillars, almost through the brand. Today is print, the physical stuff, business cards, flyers, posters. People think print means opening a heavy design app and nudging boxes for an afternoon. We build print the same way we build web: from code and data. By the end you will know how to make a hundred print pieces from one template without redesigning a thing.
on-screen: Print that builds itself
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Print that builds itself
2s2
matches intent
NumberedList
template
teach24.1–51.400000000000006skinetic-buildicon·wireframe♪ node_lock
Step one. Build your print piece as a web page, in HTML and CSS, the same code that makes a website. A flyer is just a box with a headline, some text, and your logo, which is exactly what a web page is. Lay it out once in code. Now your print design lives as text you can edit, version, and hand to a model, instead of a locked file only one app can open.
on-screen: Lay it out in HTML and CSS
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Lay it out in HTML and CSScurate items, nodes
3s3
matches intent
ChecklistCard
template
teach51.4–77.3skinetic-buildicon·wireframe♪ node_lock
Step two. Tell CSS the real-world size with the print rules. You set the page to your paper size, like five by seven inches, and add a small bleed margin so the color runs to the edge when it is cut. These are a few lines at the top of your file. The same code that looked right on screen now knows it is a physical card, ready for a printer.
on-screen: Set real print sizes in CSS
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Set real print sizes in CSScurate items, nodes
4s4
matches intent
NodeGraphCard
template
teach77.3–99.6skinetic-buildicon·wireframe♪ node_lock
Step three. Turn the page into a print-ready PDF with a headless browser, Chrome running with no window, driven from your terminal. One command loads your HTML and prints it to PDF at full quality. No design app, no manual export. The machine opens the page, freezes it as a PDF, and hands you a file the print shop can use.
on-screen: Export to PDF from the terminal
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Export to PDF from the terminalcurate hub, nodes
5s5
matches intent
FlowSchematic
template
teach99.6–123.0skinetic-buildicon·wireframe♪ node_lock
Step four. Keep the words and names in a small data file, separate from the layout. Then loop: for each row, fill the template and print a PDF. One name tag design becomes the whole team's name tags. One flyer becomes one per location. You designed the piece once, and the agent stamped out the batch from your list while the layout stayed identical.
on-screen: Swap data to make a hundred
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Swap data to make a hundredcurate nodes, stages
6s6
matches intent
ComparisonTable
template
proof123.0–145.0sreceipts-counticon·wireframe♪ node_lock
Our proof is that the office you can visit and the print-style pages behind it come from the same HTML and the same color tokens. We did not keep a separate world for print and a separate world for screen. It is one codebase, one set of rules, exported two ways. The card and the webpage are siblings, not strangers.
on-screen: Our pages and print share one code
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Our pages and print share one codecurate colA, colB, rows, statsLabels
7s7
matches intent
shared field
signature-3d
resolve145.0–170.5scoalescenceicon·ember-fill♪ bed_out
So print is just a web page that knows its real size and exports to PDF. Lay it out in HTML, set the print size, render with headless Chrome, loop your data. Your next step: build one business card as an HTML page and print it to PDF. You will never miss the heavy app. See how our screen and print share one code at office dot temerarii dot xyz.
on-screen: Build a print page at the office
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Build a print page 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)

youtubeMake Print-Ready PDFs From HTML and CSS, No Design App People think print means opening a heavy design app and nudging boxes for an afternoon. This video shows how to build print the same way you build web: from code and data. What you will learn: - Lay it out in HTML and CSS: a flyer is just a box with a headline, some text, and a logo, which is exactly what a web page is. Now the design is text you can edit, version, and hand to a model. - Set real print sizes in CSS: a few lines at the top set the paper size and a bleed margin so color runs to the edge when it is cut. - Export to PDF from the terminal: drive headless Chrome with one command to load your HTML and print it to PDF at full quality. - Swap data to make a hundred: keep names and copy in a small data file, loop over each row, and stamp out the whole batch while the layout stays identical. Then the proof: the office you can visit and the print-style pages behind it come from the same HTML and the same color tokens. One codebase, exported two ways. Keywords: HTML to PDF, print design, CSS print, headless Chrome, batch print, design automation. See the whole system run in public at temerarii.xyz.

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