Checklist the per-video bar — engine/sim
100.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review longform-W50-Tue 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 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 6 scenes · 142.6s · 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–23.8s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Today is content, social, and brand systems, and we are not here to talk about posting more. We are here to build a small machine that makes your posts look like you every time, fast. By the end your team will turn one idea into a week of content that stays on brand. Open the workspace. We start by teaching the machine who you are. on-screen: Build a content system today |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Build a content system today | |||||||
| 2 |  matches intent NumberedList template | teach | 23.8–47.6s | kinetic-build | icon·white-knockout | ♪ node_lock | First move: put your brand in a file. Your voice, your banned words, your colors, the things you always say and never say. Most teams keep this in someone's head, so the work drifts. We have your team write one short brand file and feed it to the agent. Now every draft starts from the same rules, and new hires inherit them on day one. on-screen: Write the brand down once |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Write the brand down oncecurate items, nodes | |||||||
| 3 |  matches intent ChecklistCard template | teach | 47.6–71.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Second move: turn one thing into many. We take a single idea, say a customer question you hear all the time, and have the agent spin it into a short video script, a few posts, and an email, all reading from that brand file. The team edits each by hand. This is the give-it-away part: one idea, many shapes, same voice, in one sitting. on-screen: One idea becomes nine pieces |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→One idea becomes nine piecescurate items, nodes | |||||||
| 4 |  matches intent PipelineMap template | teach | 71.0–94.4s | kinetic-build | icon·white-knockout | ♪ node_lock | Third move: social listening. We connect the agent to a search of what people are actually saying, through an MCP server or a simple scrape, and ask it to summarize the real questions and complaints in your space this week. Your team reads that, then writes the next idea from a real itch instead of a guess. Good content answers something someone actually asked. on-screen: Listen before you post |
expected on screen: red ground · a PipelineMap panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Listen before you postcurate nodes, stages | |||||||
| 5 |  matches intent StatScoreboard template | proof | 94.4–118.5s | receipts-count | icon·liquid-chrome | ♪ node_lock | Honest proof: The Big T-M runs its own brand exactly this way. Every video and post we publish is built by an agent from one brand file and one calendar file, kept on voice across hundreds of pieces. We are not showing you a trick. We are showing you the same system that keeps our own feed consistent, and it is live for anyone to inspect. on-screen: Our calendar proves the method |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our calendar proves the methodcurate pillar, stats, statsLabels | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 118.5–142.6s | coalescence | icon·liquid-chrome | ♪ bed_out | The takeaway: a content system is just your brand written down plus a fast hand to multiply it, with your team as the editor. Do that and you post on brand and on time without burning out one person. Your team has the file and the moves now. See the whole thing running at office dot temerarii dot xyz, and bring one idea to stretch tomorrow. on-screen: On brand, on time, on its own |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→On brand, on time, on its own | |||||||
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)
youtubeBuild a content system: turn one idea into a week of on-brand posts
We are not here to talk about posting more. We are here to build a small machine that makes your posts look like you every time, fast. By the end your team will turn one idea into a week of content that stays on brand.
The moves:
- Write the brand down once. Put your voice, your banned words, and your colors in one short file, the things you always say and never say. Feed it to the agent. Now every draft starts from the same rules, and new hires inherit them on day one.
- One idea becomes nine pieces. Take a single idea, like a customer question you hear all the time, and have the agent spin it into a short video script, a few posts, and an email, all reading from that brand file. The team edits each by hand. One idea, many shapes, same voice.
- Listen before you post. Connect the agent to a search of what people are actually saying, through an MCP server or a simple scrape, and ask it to summarize the real questions and complaints in your space this week. Then write the next idea from a real itch instead of a guess.
The honest proof: every video and post we publish is built by an agent from one brand file and one calendar file, kept on voice across hundreds of pieces. We are not showing you a trick; we are showing you the same system that keeps our own feed consistent, and it is live for anyone to inspect.
A content system is your brand written down plus a fast hand to multiply it, with your team as the editor.
See the whole thing running at office.temerarii.xyz
Keywords: content system, brand voice file, repurpose one idea, social listening, MCP, on-brand content at scale