Checklist the per-video bar — engine/sim
100.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review W26-studio-launch-beat-4 good|bad)✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarerendered16:9 Widerendered9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 3/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 6 scenes · 43.9s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | open | 0–8.1s | spatial-parallax | icon·wireframe | ♪ bed in | Before we take on any client, The Big T-M turns the whole content machine on our own brand and lets it run. on-screen: We test it on ourselves |
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→We test it on ourselves | |||||||
| 2 |  matches intent shared field signature-3d | hook | 8.1–14.7s | kinetic-build | icon·color | ♪ — | The promise is plain: only what holds up on our own launch is what we hand a client. on-screen: If it works on us, it works |
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape icosaground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→If it works on us, it works | |||||||
| 3 |  matches intent StatScoreboard template | proof | 14.7–23.0s | receipts-count | icon·color | ♪ — | We ran one launch script through ElevenLabs voice, a Remotion render, and Blotato posting, all from the terminal. on-screen: One idea, nine platforms |
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape icosaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate pillar, stats, statsLabels | |||||||
| 4 |  matches intent ComparisonTable template | receipt | 23.0–30.5s | receipts-count | icon·color | ♪ — | That one source turned into nine finished posts in an afternoon, and we kept the receipts so you can check them. on-screen: 9 posts from 1 source |
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape icosaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→9 posts from 1 sourcecurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent shared field signature-3d | coalescence | 30.5–38.9s | coalescence | icon·wireframe | ♪ swell | The pipeline does not care whose logo it carries. Swap the brand file and the same machine tells your story. on-screen: Same engine, your brand next |
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Same engine, your brand next | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 38.9–43.9s | coalescence | icon·wireframe | ♪ bed out | Watch us prove it in the open, then bring us the brand you want tested next. on-screen: See the receipts at temerarii.xyz |
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→See the receipts at temerarii.xyz | |||||||
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 12 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog
Social captions supplemental published copy · per channel (comp_id level)
tiktokWe point our own content machine at ourselves before any client sees it. One launch script became nine posts in an afternoon, all from the terminal. If it survives on us, you get it. Receipts are public. (AI-assisted)
instagramOne script.
Nine finished posts.
One afternoon.
We test the whole pipeline on our own brand first. Whatever holds up on us is the only thing a client gets. Swap the brand file, same machine runs your story.
Receipts are public at temerarii.xyz
#contentops #aiworkflow #buildinpublic #smallstudio #marketingsystems
linkedinBefore we take on a client, we run our entire content pipeline on our own brand. The rule is plain: only what holds up on our own launch is what we hand you.
One launch script went through ElevenLabs voice, a Remotion render, and Blotato posting, all from the terminal. That one source turned into nine finished posts in an afternoon, and we kept the receipts.
The pipeline does not care whose logo it carries. Swap the brand file and the same machine tells your story. You can check the proof in the open at temerarii.xyz.
xWe run our whole content machine on our own brand first. Only what survives gets handed to a client. One script became nine posts in an afternoon, all from the terminal. Receipts public: temerarii.xyz
facebookWe test our content pipeline on ourselves before any client sees it. One launch script became nine finished posts in an afternoon, all run from the terminal. Whatever holds up on us is the only thing we hand a client. Want to watch it work and check the receipts? See it at temerarii.xyz
threadsWe point the whole content machine at our own brand before any client sees it.
One launch script. Nine finished posts. One afternoon. All from the terminal.
The rule: only what survives on us gets handed to you. Swap the brand file and the same machine runs your story. Receipts are public.
pinterestHow a small studio turns one launch script into nine finished social posts in an afternoon: a terminal-run content pipeline using voice generation, programmatic video, and multi-platform posting. We test it on our own brand first, then swap the brand file to run yours. Self-proof content workflow for marketing teams.
blueskyWe run our whole content pipeline on our own brand before any client sees it. One script became nine posts in an afternoon, from the terminal. Only what survives gets handed over. Receipts public.
youtubeTitle: We Test Our Content Machine On Ourselves First (1 Script, 9 Posts)
Before we take on a client, we point our entire content pipeline at our own brand and let it run. One launch script goes through voice generation, a programmatic video render, and multi-platform posting, all from the terminal, and becomes nine finished posts in an afternoon. The rule is simple: only what holds up on our own launch is what we hand a client. Swap the brand file and the same machine runs your story. Watch it work and check the receipts at temerarii.xyz.