engine.sim.memory review longform-W38-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–19.8s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Today is email, the cheapest line you own and the most wasted. Stop guessing, start printing applies hard here. By the end you will know how to let a model write, segment, and time your emails from your own data, so each send has a reason instead of going out because it is Tuesday. on-screen: Email that earns its send |
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→Email that earns its send | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 19.8–41.1s | kinetic-build | icon·white-knockout | ♪ node_lock | First, split your list by behavior, not by hope. Pull your contacts and their actions from your tool, something like Resend or your shop's API, then have the model sort them: bought once, never bought, abandoned a cart. Three plain buckets. A model is fast at this. Now every email can speak to people where they actually are. on-screen: Group by what they did |
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→Group by what they didcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 41.1–63.400000000000006s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Hand the agent your past winners and your product facts, then ask it to draft the next email for one bucket. The trick is to feed it your own voice and real details, not a blank prompt. It writes the subject, the body, and three subject-line options. You edit for ten minutes instead of staring at a cursor for an hour. on-screen: Let it draft from real lines |
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 it draft from real linescurate items, nodes | |||||||
| 4 | ![]() matches intent NodeGraphCard template | teach | 63.4–85.4s | kinetic-build | icon·white-knockout | ♪ node_lock | Now stop sending by calendar and start sending by action. Set a simple trigger: cart abandoned, wait an hour, the agent sends the matching draft. Booking finished, send the follow-up. The model watches the event stream and fires the right note at the right minute. That is the email that pays, the one tied to something the person just did. on-screen: Trigger on the action |
expected on screen: red ground · a NodeGraphCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Trigger on the actioncurate hub, nodes | |||||||
| 5 | ![]() matches intent ComparisonTable template | proof | 85.4–104.5s | receipts-count | icon·liquid-chrome | ♪ node_lock | We run our own list this way. The studio's updates fire off the same source file the whole calendar comes from, so when a piece ships, the note about it writes and sends itself. No intern remembering on Friday. You can watch the studio run in public at office.temerarii.xyz, emails and all. on-screen: Our calendar emails itself |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our calendar emails itselfcurate colA, colB, rows, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 104.5–121.1s | coalescence | icon·liquid-chrome | ♪ bed_out | So: split by behavior, draft in your own voice with a model, and trigger on the action instead of the calendar. Each send earns its place. The full loop is live at office.temerarii.xyz. Set one trigger this week, the abandoned cart, and let it run. on-screen: Send by reason, not date |
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→Send by reason, not date | |||||||