engine.sim.memory review longform-W46-Thu 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.5s | spatial-parallax | icon·wireframe | ♪ bed_in | Event coordination is where most money quietly leaks. You spend on a booth or a dinner and never know if it worked. Today I show you how an AI agent plans an event around a real goal and tracks who showed up, so this week's idea, access into advantage, has numbers behind it instead of vibes. on-screen: Events that pay for themselves |
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Events that pay for themselves | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 20.5–41.4s | kinetic-build | icon·wireframe | ♪ node_lock | First. Before you book a room, tell the agent who you want in it. Have it scrape the local companies and roles you are targeting and build the guest list in Airtable first. The event exists to get those specific people together. The model builds the list, the list shapes the event, not the other way around. on-screen: Plan backward from the guest list |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Plan backward from the guest listcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 41.4–60.2s | kinetic-build | icon·wireframe | ♪ node_lock | Second. Wire the agent into Gmail and Google Calendar through their MCP servers. It drafts a personal invite for each name, sends the calendar hold, and schedules two reminders so nobody forgets. You approve the wording once. The agent runs the chase so you are not copy pasting invites at midnight. on-screen: Automate the invite and the reminder |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Automate the invite and the remindercurate items, nodes | |||||||
| 4 | ![]() matches intent ProcessFlow template | teach | 60.2–79.0s | kinetic-build | icon·wireframe | ♪ node_lock | Third. The day after, have the model turn your attendee notes into a follow-up for each person that mentions what you actually talked about. A real detail, not dear valued guest. The agent reads your notes and drafts twenty warm follow-ups in the time it took you to find your car. on-screen: Capture the room, then follow up |
expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Capture the room, then follow upcurate nodes, steps | |||||||
| 5 | ![]() matches intent FlowSchematic template | teach | 79.0–97.4s | kinetic-build | icon·wireframe | ♪ node_lock | Honest proof. We plan our own gatherings with this loop, guest list first, follow-ups automated, all logged in the same Airtable that the source file behind this video reads from. No fabricated turnout. Just the method, run on The Big T-M, in the open, so you can lift it whole. on-screen: We run our own events this way |
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→We run our own events this waycurate nodes, stages | |||||||
| 6 | ![]() first render · fix pending KpiGrid templatecustom_element_dup | proof | 97.4–121.5s | receipts-count | icon·wireframe | ♪ node_lock | Wait, that was the proof, here is the takeaway. Plan backward from the guest list. Automate the invites and reminders. Capture the room and follow up with real detail. Let the agent carry the logistics while you carry the conversation. The studio is live at office dot temerarii dot xyz. Pick the ten people you want in a room and let the model build the list. on-screen: Plan it at office.temerarii.xyz |
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape octaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Plan it at office.temerarii.xyzcurate kpis, statsLabels | |||||||
| 7 | ![]() matches intent shared field signature-3d | resolve | 121.5–126.5s | coalescence | icon·wireframe | ♪ bed_out | Creative workflows: the give-it-away method, end to end on-screen: Chapter 6 |
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Chapter 6 | |||||||