engine.sim.memory review longform-W30-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–30.9s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | One idea, nine outputs, and today we go up. Aerial drone footage gives you a view a person on the ground can never get, and that one shot can make a small operation look like a real place. But a drone is also a fast way to get boring footage and a fine. So we are going to do it right. By the end you will know how to plan a safe aerial shot that actually serves the idea, not just spins in a circle. on-screen: The shot from above |
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→The shot from above | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 30.9–56.4s | kinetic-build | icon·white-knockout | ♪ node_lock | First, ask why you are going up at all. Height should say something: the scale of a site, the path through a space, the reveal of where you are. We write that one sentence in the same file as the rest of the week. If the only reason is that drones look cool, we cut it. Every shot has to carry the idea, even the one from two hundred feet. on-screen: Decide what the height is saying |
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→Decide what the height is sayingcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 56.4–84.1s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Before the battery goes in, check where you are allowed to fly. There are free apps and maps that show restricted airspace around airports and events. You type your spot, you read the rules, you get permission if you need it. This is not the fun part, but a model can summarize the rules for your area in plain language so you actually read them. Flying blind is how you lose the drone and the footage. on-screen: Check the airspace before you fly |
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→Check the airspace before you flycurate items, nodes | |||||||
| 4 | ![]() matches intent JsonDiff template | teach | 84.1–111.1s | kinetic-build | icon·white-knockout | ♪ node_lock | A drone that hovers is a tall tripod. The value is movement. So plan one clean move per shot: a slow push in, a reveal over a roofline, a straight pull back that opens the scene. Write the move next to the shot on your list. One deliberate move beats ten frantic ones, and it is the move, not the height, that makes the footage feel like cinema instead of a real estate listing. on-screen: Plan the move, not just the spot |
expected on screen: red ground · a JsonDiff panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Plan the move, not just the spotcurate fileName, lines, nodes | |||||||
| 5 | ![]() matches intent ComparisonTable template | proof | 111.1–133.4s | receipts-count | icon·liquid-chrome | ♪ node_lock | The aerial shots in this week's work came off a list that named the move and the reason for each one, with the airspace checked first. Nothing flown for the sake of flying. That is the proof. The footage looks intentional because it was planned in the same file as everything else, not grabbed on a whim and bolted on later. on-screen: We planned every aerial shot |
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→We planned every aerial shotcurate colA, colB, rows, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 133.4–159.70000000000002s | coalescence | icon·liquid-chrome | ♪ bed_out | So the takeaway. A drone is a view, not a toy. Decide what the height is saying, check the airspace before you fly, and plan one clean move per shot. Do that and your aerials carry the idea instead of just filling time. You can see the aerial work inside this week's case study at office dot temerarii dot xyz. Plan the move on the ground, before the drone ever leaves it. on-screen: See the aerials in the case study |
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→See the aerials in the case study | |||||||