Print — social-W26-Tue-3 — Temerarii Media Back Office

post social-W26-Tue-3kind threadweek W26date 2026-06-30campaign thread · Tuepillar brandbeat Tueasset videoduration 76.5sground redscenes 9

Checklist the per-video bar — engine/sim

93.2/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

quantitative quality · weights learn from your reviews (engine.sim.memory review social-W26-Tue-3 good|bad)

⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel

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 9 scenes · 76.5s · comp_id + rendered still + tier + the script

#	Layer (comp_id · still · tier)	Beat	Timecode	Motion	Logo	Audio	VO / on-screen / caption
1	still pending matches intent shared field signature-3d	open	0–8.4s	spatial-parallax	icon·liquid-chrome	♪ bed_in	Print used to be a one-shot gamble: you sent the file, crossed your fingers, and learned about the typo at the warehouse. on-screen: Print used to be a one-shot gamble
	expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Print used to be a one-shot gamble
2	still pending matches intent shared field signature-3d	hook	8.4–16.1s	kinetic-build	icon·white-knockout	♪ node_lock	The expensive mistakes always hid in the details, a color that shifts, a bleed that clips, a font nobody embedded. on-screen: The expensive mistakes hid in the details
	expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape icosaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→The expensive mistakes hid in the details
3	still pending matches intent NumberedList template	teach	16.1–24.5s	kinetic-build	icon·liquid-chrome	♪ node_lock	Now we let AI proof the file before the press ever sees it, scanning for low resolution, missing bleeds, and odd colors. on-screen: Now: AI proofs before the press does
	expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Now: AI proofs before the press doescurate items, nodes
4	still pending matches intent RankList template	proof	24.5–33.3s	receipts-count	icon·white-knockout	♪ node_lock	The method: build in the print color space from the start, not the screen one, so what you approve is what actually prints. on-screen: Design in the print color space
	expected on screen: red ground · a RankList panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape icosaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Design in the print color spacecurate rows, statsLabels
5	still pending matches intent StackTrace template	diff	33.3–41.4s	crossfade-8f	icon·liquid-chrome	♪ node_lock	Our rule survives the AI: always order one physical proof, because a screen lies about paper and ink every single time. on-screen: We still order a real proof
	expected on screen: red ground · a StackTrace panel over a dimmed Signal Field · Signum leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StackTracevisual codeshape icosaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We still order a real proofcurate codeLines, errMsg, errType, fix, frames
6	still pending matches intent ChecklistCard template	teach	41.4–50.9s	kinetic-build	icon·white-knockout	♪ node_lock	Hold that proof under the light it will live in, a store, a desk, a window, because color is a liar in the wrong room. on-screen: Check the proof under real light
	expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Check the proof under real lightcurate items, nodes
7	still pending matches intent StatScoreboard template	proof	50.9–60.0s	receipts-count	icon·liquid-chrome	♪ node_lock	We caught a color shift on a client proof before the full run, which saved a reprint that nobody would have enjoyed paying for. on-screen: A run saved before it cost money
	expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→A run saved before it cost moneycurate pillar, stats, statsLabels
8	still pending matches intent CheatSheet template	step	60.0–68.8s	kinetic-build	icon·white-knockout	♪ node_lock	Your step: let AI proof the file, then order one physical proof and judge it in real light before you commit the run. on-screen: Step: proof the file, then the paper
	expected on screen: red ground · a CheatSheet panel over a dimmed Signal Field · Signum leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual pipelineshape icosaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Step: proof the file, then the papercurate points, stages, steps, uses
9	still pending matches intent shared field signature-3d	resolve	68.8–76.5s	coalescence	icon·liquid-chrome	♪ bed_out	Soon bad files will get caught before they cost a cent, and The Big T-M is already printing that way. on-screen: Futurist: no bad file reaches the press
	expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Futurist: no bad file reaches the press

Format stack 3 aspects · same scenes[], re-cropped

9:16

1080×1920

Stories · TikTok · YouTube Shorts · Reels

1:1

1080×1080

LinkedIn · Facebook · Instagram

16:9

1920×1080

X/Twitter · YouTube · LinkedIn video

Channels 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

Social captions supplemental published copy · per channel (comp_id level)

tiktokPrint is a one-shot gamble — and the typo always hides at the warehouse. AI-assisted fix: proof the file for low-res, missing bleeds, and odd colors BEFORE the press. Design in print color space. Then still order a physical proof. We caught a color shift before a full run.

instagramPrint is a one-shot gamble. AI proofs the file first. Design in print color space. Then still order ONE physical proof. Judge it in real light. #printdesign #graphicdesign #prepress #branding #temerarii

linkedinPrint used to be a one-shot gamble: send the file, cross your fingers, and learn about the typo at the warehouse. The expensive mistakes hide in the details — a color that shifts, a bleed that clips, a font nobody embedded. The method: let AI proof the file before the press sees it, scanning for low resolution, missing bleeds, and odd colors. Design in the print color space from the start, not the screen one. And keep the rule AI can't replace — always order one physical proof and judge it under the light it will live in, because a screen lies about paper and ink. We caught a color shift on a client proof before the full run, saving a reprint nobody wanted to pay for.

xPrint is a one-shot gamble, and the typo always shows up at the warehouse. AI proofs the file. Design in print color space. Then still order one physical proof. We caught a color shift before the run. temerarii.com

facebookPrint used to be a one-shot gamble — you sent the file, crossed your fingers, and learned about the typo at the warehouse. The expensive mistakes hide in the details. The method: let AI proof the file first for low resolution, missing bleeds, and odd colors, design in the print color space, and still order one physical proof judged under real light. We caught a color shift on a client proof before the full run. Got a print job coming up? Message us.

threadsPrint is a one-shot gamble, and the typo always hides at the warehouse. AI proofs the file for low-res, missing bleeds, odd colors. Design in print color space. Then STILL order one physical proof and judge it in real light. We caught a color shift before a full run. A screen lies about paper.

pinterestPrint production checklist: proof your file for resolution, bleed, and color before the press, design in the print color space, and always order a physical proof judged in real light. Print design tips, prepress, CMYK setup, graphic design, packaging proof, color accuracy.

blueskyPrint is a one-shot gamble, and the typo always shows up at the warehouse. AI proofs the file. Design in print color space. Then still order one physical proof. We caught a color shift before the run. temerarii.com

youtubePrint Without the Gamble: Proof the File, Then the Paper Print used to be a one-shot gamble — send the file, cross your fingers, learn about the typo at the warehouse. The expensive mistakes hide in the details: a color that shifts, a bleed that clips, a font nobody embedded. The method: let AI proof the file first for low resolution, missing bleeds, and odd colors, design in the print color space from the start, and still order one physical proof judged under the light it'll live in. We caught a color shift on a client proof before the full run. Built by The Big T-M.

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

→ Wireframe · scenes → Calendar week → Media (audience preview)→ Storyboard hub → Day view → Channel view