Checklist the per-video bar — engine/sim
98.9/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review topic-brand-branding good|bad)⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 14 scenes · 101.1s · 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–6.6s | spatial-parallax | icon·ember-fill | ♪ — | Branding. Not a logo, not a vibe. A set of rules a machine could follow. Here is how we write them. on-screen: Branding |
expected on screen: black ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→three-mark | |||||||
| 2 |  matches intent CodeWindow template | legacy | 6.6–13.0s | crossfade-8f | icon·wireframe | ♪ — | The old way was a ninety-page guidelines PDF that lived in a drive and nobody ever opened again. on-screen: Old way: a 90-page PDF |
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Signum leads · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CodeWindowshape icosaground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate codeLines, windowTitle | |||||||
| 3 |  matches intent NumberedList template | teach | 13.0–19.6s | kinetic-build | icon·wireframe | ♪ — | Step one, name what you stand against. A brand with no enemy has no edge. Ours is hype over proof. on-screen: Step 1: find the conflict |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes | |||||||
| 4 |  matches intent ChecklistCard template | teach | 19.6–27.900000000000002s | kinetic-build | icon·wireframe | ♪ — | Step two, lock the rails, palette, type, and voice, into a single JSON file the whole system reads, not a mood board. on-screen: Step 2: lock the rails |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes | |||||||
| 5 |  matches intent DiffCard template | teach | 27.9–34.6s | kinetic-build | icon·wireframe | ♪ — | Step three, list the words you will never say. We ban about thirty hype terms so the voice cannot drift into mush. on-screen: Step 3: name the banned words |
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate lines, nodes | |||||||
| 6 |  matches intent LogStream template | teach | 34.6–42.2s | kinetic-build | icon·wireframe | ♪ — | Step four, write the voice as a checklist a stranger or a model could pass, not as adjectives like bold or premium. on-screen: Step 4: write voice as rules |
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, rows | |||||||
| 7 |  matches intent JsonDiff template | teach | 42.2–49.900000000000006s | kinetic-build | icon·wireframe | ♪ — | Step five, decide how the brand moves. Stillness is a choice too. Motion is identity now, so design it on purpose. on-screen: Step 5: pick a motion language |
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate fileName, lines, nodes | |||||||
| 8 |  matches intent ProcessFlow template | teach | 49.9–58.3s | kinetic-build | icon·wireframe | ♪ — | Step six, turn the rules into real components, buttons, cards, lower-thirds, so on-brand is the default, not a fight. on-screen: Step 6: build the components |
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, steps | |||||||
| 9 |  matches intent CheatSheet template | teach | 58.3–66.2s | kinetic-build | icon·wireframe | ♪ — | Step seven, add automated checks that reject anything off-palette or off-voice before it ever ships. The brand defends itself. on-screen: Step 7: gate every asset |
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, points, uses | |||||||
| 10 |  matches intent SchematicCard template | teach | 66.2–74.60000000000001s | kinetic-build | icon·wireframe | ♪ — | Step eight, point every tool, the site, the reels, the emails, at that same rails file. Change it once, it changes everywhere. on-screen: Step 8: one source of truth |
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes | |||||||
| 11 |  matches intent ListCard template | teach | 74.6–80.8s | kinetic-build | icon·wireframe | ♪ — | Step nine, version the brand in git, so it can grow on purpose and you can always see why it changed. on-screen: Step 9: let it evolve in git |
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ListCardvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes | |||||||
| 12 |  matches intent RankList template | proof | 80.8–87.89999999999999s | receipts-count | icon·wireframe | ♪ — | That is a brand as a living system, not a frozen PDF. We run ours exactly this way and show the file. on-screen: Receipts, in the open |
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape icosaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels | |||||||
| 13 |  matches intent shared field signature-3d | futurist | 87.9–95.4s | spatial-parallax | icon·wireframe | ♪ — | What is next is new assets generating themselves already on-brand, because the rules are executable, not aspirational. on-screen: Next: it self-applies |
expected on screen: black ground · icosa hero in the shared Signal Field · Signum leads · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape icosaground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward | |||||||
| 14 |  matches intent shared field signature-3d | resolve | 95.4–101.10000000000001s | coalescence | icon·ember-fill | ♪ swell | Branding you can actually run, not just frame. The system is at temerarii dot com. on-screen: temerarii.com |
expected on screen: black ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→three-coalescence | |||||||
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)
tiktokBranding is not a logo or a vibe. AI-assisted. It is a set of rules a machine could follow. Step one, name what you stand against. Step two, lock palette, type, and voice into one JSON file the whole system reads. Step three, ban your hype words. Step four, write the voice as a checklist anyone could pass. Then add checks that reject off-brand work before it ships, so the brand defends itself. Version it in git so it grows on purpose. That is a brand as a living system, not a frozen PDF. The file is at temerarii.com.
instagramBranding is not a logo. It's rules a machine could follow.
Name what you stand against.
Lock palette, type, voice in one file.
Ban your hype words.
Write the voice as a checklist.
Gate every asset, so the brand defends itself.
Version it in git. A living system, not a frozen PDF.
#temerarii #branding #designsystems #aitools #buildinpublic
linkedinBranding is not a logo or a vibe. It is a set of rules a machine could follow. The old way was a ninety-page guidelines PDF nobody opened twice. Here is how we write a brand that runs.
1. Name what you stand against. A brand with no enemy has no edge. Ours is hype over proof.
2. Lock the rails, palette, type, and voice, into one JSON file the whole system reads, not a mood board.
3. List the words you will never say. We ban about thirty hype terms so the voice cannot drift into mush.
4. Write the voice as a checklist a stranger or a model could pass, not adjectives like bold or premium.
5. Decide how the brand moves. Motion is identity now, so design it on purpose.
6. Turn the rules into real components, so on-brand is the default, not a fight.
7. Add automated checks that reject anything off-palette or off-voice before it ships. The brand defends itself.
8. Point every tool at that same rails file. Change it once, it changes everywhere.
9. Version the brand in git, so it grows on purpose and you can see why it changed.
That is a brand as a living system, not a frozen PDF. We run ours exactly this way and show the file at temerarii.com.
xBranding is not a logo. It's rules a machine could follow.
Name your enemy. Lock palette, type, voice in one file. Ban your hype words. Gate every asset so off-brand work never ships.
Version it in git. A living system, not a frozen PDF.
temerarii.com
facebookBranding is not a logo or a vibe. It is a set of rules a machine could follow.
The old way was a ninety-page PDF nobody opened twice. The new way: name what you stand against, lock palette, type, and voice into one file the whole system reads, ban your hype words, write the voice as a checklist, then add checks that reject off-brand work before it ships. Point every tool at that one file and version it in git.
That is a brand as a living system, not a frozen PDF. See the file at temerarii.com
threadsBranding is not a logo or a vibe. It is a set of rules a machine could follow.
Name what you stand against. Lock palette, type, and voice into one file. Ban your hype words. Write the voice as a checklist anyone could pass. Then gate every asset so off-brand work never ships, and the brand defends itself.
Version it in git. A living system, not a frozen PDF. temerarii.com
pinterestBranding as an executable system, not a PDF: name what you stand against, lock palette, type, and voice in one JSON file, ban your hype words, write voice as a checklist, build on-brand components, and gate every asset with automated checks. Version the brand in git so it grows on purpose. Design systems, brand guidelines, AI workflow.
blueskyBranding is not a logo. It's rules a machine could follow.
Name your enemy. Lock palette, type, voice in one file. Ban your hype words. Write voice as a checklist. Gate every asset so off-brand work never ships.
Version it in git. A living system, not a frozen PDF. temerarii.com
youtubeBranding as Rules a Machine Can Follow (Not a 90-Page PDF)
Branding is not a logo or a vibe. It is a set of rules a machine could follow. The old way was a ninety-page guidelines PDF that lived in a drive and nobody ever opened again. Here is the full method, given away.
1. Name what you stand against. A brand with no enemy has no edge.
2. Lock the rails, palette, type, and voice, into a single JSON file the whole system reads.
3. List the words you will never say. We ban about thirty hype terms so the voice cannot drift.
4. Write the voice as a checklist a stranger or a model could pass, not adjectives.
5. Decide how the brand moves. Motion is identity now, so design it on purpose.
6. Turn the rules into real components, so on-brand is the default.
7. Add automated checks that reject off-palette or off-voice work before it ships.
8. Point every tool at that same rails file. Change it once, it changes everywhere.
9. Version the brand in git, so it grows on purpose and you can see why it changed.
What is next: new assets generating themselves already on-brand, because the rules are executable. That is a brand as a living system, not a frozen PDF. We run ours this way and show the file.
More at temerarii.com