engine.sim.memory review longform-W30-Sun good|bad)| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | ![]() matches intent shared field signature-3d | open | 0–30.9s | spatial-parallax | icon·wireframe | ♪ bed_in | This week the calendar says one thing: one idea, nine outputs. Most studios start a new project from zero every single time. We do the opposite. We take a single content plan and turn it into video, photos, a live stream, a script, and more, all from one source. Today we open the plan itself. By the end you will know how to write a content strategy that a machine can read and run, instead of a deck that sits in a folder and dies. on-screen: One idea, nine outputs |
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→One idea, nine outputs | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 30.9–57.5s | kinetic-build | icon·wireframe | ♪ node_lock | Start with one file. Not a pretty document, a plain text file the model can read. We use a simple format called JSON, which is just labeled boxes. One box for the idea, one for the week, one for the audience. The whole point is that a human and a machine read the same file. No copy, no paste, no version six final final. One source, and everything else points back to it. on-screen: Write one source file |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write one source filecurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 57.5–83.8s | kinetic-build | icon·wireframe | ♪ node_lock | Before you write a word of content, write down who it is for. We put the audience right in the file: who they are, what they already know, what they want next. Then we hand that to the model with a clear instruction. Read this audience, and do not write above their head. That one rule kills most bad marketing, because most bad marketing is written to impress, not to be understood. on-screen: Name the audience first |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Name the audience firstcurate items, nodes | |||||||
| 4 | ![]() matches intent SchematicCard template | teach | 83.8–109.0s | kinetic-build | icon·wireframe | ♪ node_lock | Now the hard part. One idea, not nine. People think strategy means more ideas. It means fewer. We make the model argue with us. We say, here are five angles, pick the one a stranger would repeat to a friend, and tell me why the other four are weaker. When you force the cut, you find the idea that can carry an entire week instead of one tired post. on-screen: Pick the one idea |
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Pick the one ideacurate nodes | |||||||
| 5 | ![]() matches intent CheatSheet template | teach | 109.0–132.4s | kinetic-build | icon·wireframe | ♪ node_lock | One idea is still too big to film. So we break it into beats: the hook, the teach, the proof, the close. Each beat is one job. We store the beats in the same file, in order. The model never has to guess what comes next, because the order is written down. A beat list is the difference between a plan and a wish. on-screen: Break it into beats |
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Break it into beatscurate nodes, points, uses | |||||||
| 6 | ![]() matches intent StackTrace template | teach | 132.4–156.5s | kinetic-build | icon·wireframe | ♪ node_lock | Here is the move that gets you nine outputs. Take each beat and ask, what format does this beat want to live in. The hook wants a short vertical video. The proof wants a photo or a chart. The full teach wants the long form you are watching now. We write the format next to each beat, so the plan already knows what it will become. on-screen: Map each beat to a format |
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StackTracevisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Map each beat to a formatcurate errMsg, errType, fix, frames, nodes | |||||||
| 7 | ![]() matches intent NodeGraphCard template | teach | 156.5–181.3s | kinetic-build | icon·wireframe | ♪ node_lock | Now we let the model do the boring multiplication. One agent reads the beats and the formats, and writes a draft for each one: the caption, the script, the photo brief, the stream rundown. It is the same idea every time, said the right way for each place. You are not writing nine things. You are writing one thing and teaching a machine to translate it nine ways. on-screen: Let the model fan it out |
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the model fan it outcurate hub, nodes | |||||||
| 8 | ![]() matches intent AnnotatedDiagram template | teach | 181.3–205.8s | kinetic-build | icon·wireframe | ♪ node_lock | The trap with nine outputs is they drift apart and stop feeling like one campaign. So we keep a thread. Every output carries the same hook line and the same close. We tell the model to repeat the spine and vary the body. That way a person who sees the photo, then the video, then the stream, feels one voice, not three strangers wearing the same logo. on-screen: Keep a thread between them |
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Keep a thread between themcurate callouts, nodes | |||||||
| 9 | ![]() matches intent ComparisonTable template | proof | 205.8–232.10000000000002s | receipts-count | icon·wireframe | ♪ node_lock | Does it work? Look at this week. One brief file became this video, the short clips, the photos, and the posts you are seeing, all from a single source. We did not hire a team of nine. We wrote one plan and let the machine fan it out, in public, with nothing hidden. That is the only proof we trust: we run it on ourselves before we ever sell it to you. on-screen: We run this on us first |
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We run this on us firstcurate colA, colB, rows, statsLabels | |||||||
| 10 | ![]() matches intent shared field signature-3d | resolve | 232.1–260.1s | coalescence | icon·wireframe | ♪ bed_out | So here is the takeaway. Content strategy is not a mood board, it is a file a machine can run. Write one source, name the audience, cut to one idea, break it into beats, map each beat to a format, then let the model fan it out while you guard the thread. You can watch the whole calendar, built from one file, live at office dot temerarii dot xyz. Go read the plan, then go write yours. on-screen: See the whole plan live |
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→See the whole plan live | |||||||