engine.sim.memory review longform-W37-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–23.0s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | This one is about event coordination, the live end of strategic relations. Most events fail because someone guessed at the topic. We are going to do it backward. You will learn how to read your audience first, find the gathering they already wish existed, and only then plan it. Listening picks the room so you do not pay to fill an empty one. on-screen: Build the room they want |
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 the room they want | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 23.0–42.5s | kinetic-build | icon·white-knockout | ♪ node_lock | First move. In your listening file, have Claude search for posts where people ask if anything exists, or wish there were a place to talk about your topic. Those sentences are unmet demand. When a dozen people independently wish for the same room, you do not need a survey. You need a date. on-screen: Search for the missing meetup |
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→Search for the missing meetupcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 42.5–62.3s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Second move. Pull the questions people keep asking and never getting answered. Group them with the model into three or four themes. That is your agenda, written by the room before the room exists. An event built from real unanswered questions fills itself, because people show up for the answer they have been chasing. on-screen: Let the questions write the agenda |
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→Let the questions write the agendacurate items, nodes | |||||||
| 4 | ![]() matches intent StepFlow template | teach | 62.3–81.1s | kinetic-build | icon·white-knockout | ♪ node_lock | Third move. Ask the model to count location words in your mentions. If one place keeps coming up, start there. Online works too, but a real city signal tells you where a small in-person gathering would not echo in an empty hall. Let the data pick the dot on the map. on-screen: Find the city in the noise |
expected on screen: red ground · a StepFlow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id StepFlowvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Find the city in the noisecurate nodes, steps | |||||||
| 5 | ![]() matches intent RankList template | proof | 81.1–101.3s | receipts-count | icon·liquid-chrome | ♪ node_lock | Honest proof: we do not invent topics for our own events. We read what people keep asking and hand them the session. The whole public calendar you are watching was built from a source file the same way, by listening first and deciding second. We are running the studio in the open, this move included. on-screen: We plan the calendar the same way |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We plan the calendar the same waycurate rows, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 101.3–121.5s | coalescence | icon·liquid-chrome | ♪ bed_out | The takeaway: never plan an event in a vacuum. Read the wish, steal the agenda from real questions, follow the location signal, then send one invite. Your next step is small. Search your mentions for the words I wish there were, and read what people answer. See the rest at office dot temerarii dot xyz. on-screen: Pick a date at office.temerarii.xyz |
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→Pick a date at office.temerarii.xyz | |||||||