Checklist the per-video bar — engine/sim
98.5/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W27-Mon-4 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 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 · 63.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–7.3s | spatial-parallax | icon·white-knockout | ♪ bed_in | For most teams, the brand lives in one person's head, and chaos starts the day they go on holiday. on-screen: Brand lived in one person's head |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Brand lived in one person's head | |||||||
| 2 |  matches intent shared field signature-3d | hook | 7.3–14.6s | kinetic-build | icon·white-knockout | ♪ node_lock | The fix is not a stronger hero. It is a written system anyone on the team can actually follow. on-screen: A system beats a hero |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→A system beats a hero | |||||||
| 3 |  matches intent NumberedList template | teach | 14.6–21.6s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Put your voice, your banned words, your colors in a plain file, not a tribe of unspoken habits. on-screen: Write the rules in a file |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Write the rules in a filecurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 21.6–28.6s | receipts-count | icon·white-knockout | ♪ node_lock | Hand that file to a model as its system prompt, so every draft starts already sounding like you. on-screen: Feed that file to the model |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Feed that file to the modelcurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 28.6–35.2s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | People fear templates kill the voice. A good system frees the voice by removing the boring decisions. on-screen: Templates aren't the enemy |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape knotground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Templates aren't the enemycurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 35.2–41.800000000000004s | kinetic-build | icon·white-knockout | ♪ node_lock | Run finished posts back through the model with one job, flag anything that breaks the brand rules. on-screen: Let it check, not just write |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let it check, not just writecurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 41.8–49.9s | receipts-count | icon·liquid-chrome | ♪ node_lock | Now a new hire ships on-brand work on day one, because the rules are in the tool, not in the air. on-screen: New hire sounds on-brand day one |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape knotground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→New hire sounds on-brand day onecurate kpis, statsLabels | |||||||
| 8 |  matches intent NodeGraphCard template | step | 49.9–57.6s | kinetic-build | icon·white-knockout | ♪ node_lock | So the move is write the rules down, make them the system prompt, then use the model as the checker. on-screen: Step: write rules, prompt, check |
expected on screen: red ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual pipelineshape knotground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Step: write rules, prompt, checkcurate hub, nodes, stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 57.6–63.9s | coalescence | icon·white-knockout | ♪ bed_out | A brand that survives a vacation. The Big T-M turns the founder's head into a system. on-screen: Brand that survives a vacation |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Brand that survives a vacation | |||||||
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)
tiktokBuild a brand system that survives a vacation (AI-assisted). Right now your brand probably lives in one person's head. Write the rules down: voice, banned words, colors, in a plain file. Feed that file to a model as its system prompt so every draft starts sounding like you. Then use the model to CHECK posts for rule breaks, not just write them.
instagramYour brand shouldn't live in one head.
Write the rules in a file.
Make it the model's system prompt.
Use AI to check, not just write.
New hires ship on-brand day one.
#brandsystems #contentstrategy #brandguidelines #marketingops #aimarketing
linkedinFor most teams, the brand lives in one person's head, and chaos begins the day they take a holiday. The fix isn't a stronger hero; it's a written system anyone can follow.
How to build it:
1. Write the rules down. Voice, banned words, colors, examples, in a plain file, not unspoken habits.
2. Make that file the model's system prompt, so every draft starts already sounding like you.
3. Use the model as a checker. Run finished posts back through it with one job: flag anything that breaks the brand rules.
The fear is that templates kill voice. In practice, a good system frees the voice by removing the boring decisions, and a new hire can ship on-brand work on day one. A brand that survives a vacation. AI-assisted and disclosed.
xYour brand shouldn't live in one person's head. Write the rules in a file, make it the model's system prompt, and use AI to CHECK posts for rule breaks, not just write them. Now new hires ship on-brand day one. temerarii.com
facebookFor most teams, the brand lives in one person's head, and chaos starts the day they go on holiday. Fix it with a system: write your voice, banned words, and colors in a plain file, feed that file to a model as its system prompt so every draft sounds like you, then use the model to check posts for rule breaks. Now a new hire ships on-brand on day one. Learn more at temerarii.com.
threadsYour brand shouldn't live in one head. Write the rules in a plain file, make it the model's system prompt, and use AI to CHECK posts for rule breaks, not just write them. Now new hires ship on-brand day one.
pinterestBuild a brand system that survives a vacation: write your voice, banned words, and colors into a file, use it as an AI system prompt, and let the model check posts for rule breaks. An evergreen guide to scalable brand and content systems.
blueskyYour brand shouldn't live in one head. Write the rules in a file, make it the model's system prompt, and use AI to CHECK posts for rule breaks, not just write them. New hires ship on-brand day one. temerarii.com
youtubeBrand Systems That Survive a Vacation: Written Rules, System Prompts & AI Checks
For most teams, the brand lives in one person's head, and chaos starts the day they take a holiday. This shows how to build a system instead: write your voice, banned words, and colors into a plain file, make that file a model's system prompt so every draft sounds like you, and use the model as a checker to flag anything that breaks the rules. A good system frees the voice by removing boring decisions, and a new hire can ship on-brand work on day one. AI-assisted and disclosed. More at temerarii.com.