engine.sim.memory review longform-W36-Wed 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–22.0s | spatial-parallax | icon·white-knockout | ♪ bed_in | Content strategy that moves the needle only works if the needle is pointed at something real. Today is about social listening: pulling what your audience actually says instead of guessing. You will learn how to gather real signal and let it shape what you make. Guessing is cheap and usually wrong. Listening is a little work and almost always right. on-screen: Stop guessing what they want |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Stop guessing what they want | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 22.0–44.3s | kinetic-build | icon·wireframe | ♪ node_lock | Step one. Go where your customers complain, not where they perform. That usually means a forum or a comment section, not a polished feed. We point a scraper at the places our buyer gathers and pull the raw posts and replies. The goal is their words, in their order, before anyone cleaned them up. Complaints are honest. Marketing copy is not. on-screen: Listen where they complain |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Listen where they complaincurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 44.3–68.1s | kinetic-build | icon·wireframe | ♪ node_lock | Step two. Grab the text with an actual tool, not by hand. We use an Apify scraper through an MCP connection, or a Reddit reader, and tell the agent to fetch the top threads on our topic. It returns the posts and the comments as plain text. Now you have a pile of real human sentences instead of a hunch about what people care about. on-screen: Pull the threads with a tool |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Pull the threads with a toolcurate items, nodes | |||||||
| 4 | ![]() matches intent NodeGraphCard template | teach | 68.1–90.8s | kinetic-build | icon·wireframe | ♪ node_lock | Step three. Feed that pile to the model and ask one question: what problem comes up again and again, in their own phrasing. The model is good at spotting the repeat. It hands you back the five complaints that keep returning and the exact words people use. Those words are gold, because they are the words your customer will search and recognize. on-screen: Let the model find the patterns |
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the model find the patternscurate hub, nodes | |||||||
| 5 | ![]() matches intent CodeWindow template | teach | 90.8–112.1s | kinetic-build | icon·wireframe | ♪ node_lock | Step four. Take the top repeated complaint and make it your next post, answered plainly. Not your pitch, their question, answered straight. We drop the real phrasing into the post so it sounds like we were in the room. You are no longer inventing topics. You are returning the audience's own questions to them with an answer attached. on-screen: Turn complaints into topics |
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Turn complaints into topicscurate codeLines, nodes, windowTitle | |||||||
| 6 | ![]() matches intent AnnotatedDiagram template | teach | 112.1–133.4s | kinetic-build | icon·wireframe | ♪ node_lock | Step five. Listening does not stop after you post. Pull the replies your post earns and feed those back in. We collect the comments and let the model sort them into questions, agreement, and pushback. The pushback is the best fuel. It tells you the next post before you have to think of it. The loop feeds itself. on-screen: Close the loop with replies |
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Close the loop with repliescurate callouts, nodes | |||||||
| 7 | ![]() matches intent StatScoreboard template | proof | 133.4–154.70000000000002s | receipts-count | icon·wireframe | ♪ node_lock | The honest proof: before we wrote a single line for the studio, we read what people actually say about agencies that hide the work. That complaint, that you never see how it is made, shaped this whole open build. We did not decide to be transparent because it sounded nice. The audience told us to, and we listened. on-screen: We listened before we built |
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We listened before we builtcurate pillar, stats, statsLabels | |||||||
| 8 | ![]() matches intent shared field signature-3d | resolve | 154.7–178.1s | coalescence | icon·white-knockout | ♪ bed_out | So the takeaway: stop guessing and go read. Scrape where they complain, pull it with a tool, let the model find the repeat, and answer their real words. Then read the replies and do it again. Your next step: see how listening shaped our whole plan at office dot temerarii dot xyz, then go read one thread in your own corner and answer it. on-screen: Hear the audience, then build |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Hear the audience, then build | |||||||