engine.sim.memory review longform-W37-Sat 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 | Today closes the week on partnership outreach: actually reaching the people your listening surfaced. Finding the right partner is half the job. The other half is the note that gets a reply. You will learn how to use your own data to write outreach that does not feel cold, because it is built from something the other side already said. on-screen: Outreach without the cold |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Outreach without the cold | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 22.0–41.8s | kinetic-build | icon·white-knockout | ♪ node_lock | First move. For each partner candidate, have Claude pull one real, specific thing they posted recently, and open the note with it. Not flattery. A fact. People can smell a template in one line. A first sentence that proves you actually saw their work is the difference between a reply and the trash folder. on-screen: Open with a true detail |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Open with a true detailcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 41.8–61.599999999999994s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Second move. Have the model frame the ask as a tiny first step, not a marriage. A single shared post. One swapped mention. A short call. Small asks get yes because saying yes is cheap. You can grow it later. Leading with a big proposal to a stranger is how outreach dies on arrival. on-screen: Ask for one small test |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Ask for one small testcurate items, nodes | |||||||
| 4 | ![]() matches intent BlueprintGrid template | teach | 61.6–83.2s | kinetic-build | icon·white-knockout | ♪ node_lock | Third move. Log who you contacted, when, and what they said in one file the model can read. Then have it tell you who to follow up with and who to drop. Most replies come on the second touch, not the first. Without a record you forget to follow up, and the follow-up is where the deals actually live. on-screen: Track every send in one file |
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Track every send in one filecurate nodes, rows | |||||||
| 5 | ![]() matches intent KpiGrid template | proof | 83.2–103.7s | receipts-count | icon·liquid-chrome | ♪ node_lock | Honest proof: our own outreach starts from a real detail in someone's feed, logged in a file, followed up on schedule. No bought list, no spray. When we say small asks get answered, it is because the small ones are the ones that come back to us. We are running our own playbook in the open. on-screen: We send ours from data too |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We send ours from data toocurate kpis, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 103.7–124.2s | coalescence | icon·white-knockout | ♪ bed_out | The takeaway: warm outreach is just a true opening, a small ask, and a kept record. That is the whole game. Your next step is small. Take the one partner your data ranked first, find one real thing they posted, and write three honest sentences. The full flow is live at office dot temerarii dot xyz. on-screen: Send one at office.temerarii.xyz |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Send one at office.temerarii.xyz | |||||||