engine.sim.memory review longform-W31-Tue 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–20.2s | spatial-parallax | icon·white-knockout | ♪ bed_in | Cut busywork, keep revenue. Today it is email, the channel everyone overworks and underthinks. Most teams blast everyone and call it a campaign. We are going to show you how to let a model segment your list and write to each group from real behavior. By the end you will send less and keep more. on-screen: Email that earns its send |
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→Email that earns its send | |||||||
| 2 | ![]() matches intent ChecklistCard template | teach | 20.2–40.0s | kinetic-build | icon·wireframe | ♪ node_lock | Step one. Export your list with one extra column, last purchase date. That single field splits buyers from ghosts. A model can read that export and tell you who is warm and who has been gone for a year. Sending the same note to both is the busywork that quietly burns your sender reputation. on-screen: Stop blasting the whole list |
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→Stop blasting the whole listcurate items, nodes | |||||||
| 3 | ![]() matches intent NumberedList template | teach | 40.0–57.0s | kinetic-build | icon·wireframe | ♪ node_lock | Step two. Feed that file to Claude Code and ask it to group people by behavior, recent buyers, lapsed buyers, never bought. The model does the sorting in seconds. You now have three audiences who need three different messages, instead of one message that fits nobody. on-screen: Let the model build the segments |
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→Let the model build the segmentscurate items, nodes | |||||||
| 4 | ![]() matches intent WireframeMock template | teach | 57.0–76.5s | kinetic-build | icon·wireframe | ♪ node_lock | Step three. Tell the model to write a short, honest win-back note only for the lapsed group. No discount theater, just a plain reason to come back. Then connect to your email tool, like Resend, through its API so the model can draft and queue it without you copy-pasting into a clunky editor. on-screen: Write to the lapsed, not the loyal |
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id WireframeMockvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write to the lapsed, not the loyalcurate nodes | |||||||
| 5 | ![]() matches intent StackTrace template | teach | 76.5–95.6s | kinetic-build | icon·wireframe | ♪ node_lock | Step four. Stop sending on a fixed weekly schedule out of habit. Have the model trigger the win-back only when someone crosses ninety days quiet. That is behavior, not calendar. You send when it matters and stay silent when it does not, which is how email keeps making money instead of noise. on-screen: Time it off real signals |
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Time it off real signalscurate errMsg, errType, fix, frames, nodes | |||||||
| 6 | ![]() matches intent TerminalRun template | teach | 95.6–113.3s | kinetic-build | icon·wireframe | ♪ node_lock | Step five. Ask the model to draft three subject lines for the same note, each with a different angle. Send them to small slices, keep the winner. The model writes the variants fast, so the test costs you minutes. Your gut stops deciding and your list decides instead. on-screen: Test the subject, not your gut |
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Test the subject, not your gutcurate nodes | |||||||
| 7 | ![]() matches intent StatScoreboard template | proof | 113.3–131.3s | receipts-count | icon·wireframe | ♪ node_lock | We run our own list on this exact setup. We do not have a fancy email team hiding behind the curtain, just a model reading behavior and writing to segments through an API. We send fewer emails than we used to, and the ones we send actually get opened. on-screen: We email our own people this way |
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 email our own people this waycurate pillar, stats, statsLabels | |||||||
| 8 | ![]() matches intent shared field signature-3d | resolve | 131.3–149.0s | coalescence | icon·white-knockout | ♪ bed_out | So the takeaway. Good email is not volume, it is sending the right note to the right group at the right moment, and letting a model do the sorting and drafting. Less work, more return. See the studio run it in public at office dot temerarii dot xyz. on-screen: See the whole stack live |
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→See the whole stack live | |||||||