engine.sim.memory review longform-W43-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–23.8s | spatial-parallax | icon·white-knockout | ♪ bed_in | Today is photography, and we are not talking about owning a nicer camera. We are talking about making brand images you can repeat, on demand, that all look like they belong to the same company. The week is the plan behind the proof, and a photo is proof. So here is how The Big T-M plans an image instead of hoping for a good one. on-screen: Photography you can repeat |
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→Photography you can repeat | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 23.8–45.1s | kinetic-build | icon·wireframe | ♪ node_lock | The first move is to describe the shot in words before anything else exists. Subject, setting, light, mood, framing, in one plain sentence. We store that sentence in the plan. A photo that starts as a written brief can be remade, handed off, or generated, because the intent is on paper instead of locked in one person's head. on-screen: Write the shot as a sentence |
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→Write the shot as a sentencecurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 45.1–66.7s | kinetic-build | icon·wireframe | ♪ node_lock | Next, pull your brand colors and fonts into a small set of tokens, real values in a file. Red, black, white, the typeface, the spacing. Every image references the same tokens. When two photos sit side by side, they match, because they are both reading the same numbers. The brand look stops being a guess and becomes a setting. on-screen: Lock the look in tokens |
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→Lock the look in tokenscurate items, nodes | |||||||
| 4 | ![]() matches intent SchematicCard template | teach | 66.7–88.30000000000001s | kinetic-build | icon·wireframe | ♪ node_lock | Here is the concrete tool move. Use an image model with a locked reference, so the same character or product shows up the same way every time. You feed it the reference plus your written shot, and it returns a frame that fits the brand. You are not rolling dice. You are filling in a template you already designed. on-screen: Generate from a reference sheet |
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Generate from a reference sheetcurate nodes | |||||||
| 5 | ![]() matches intent LogStream template | teach | 88.3–110.3s | kinetic-build | icon·wireframe | ♪ node_lock | Then check the output before you ship it. We run a quick visual pass that asks: do the colors match the tokens, is the brand mark used correctly, is the framing right. The model flags its own bad frames. You only look at the ones that passed, which is how you keep quality high without staring at every single image. on-screen: Make the machine grade the frame |
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Make the machine grade the framecurate nodes, rows | |||||||
| 6 | ![]() matches intent ProcessFlow template | teach | 110.3–130.8s | kinetic-build | icon·wireframe | ♪ node_lock | The proof is on our own office page. Every asset there shows a rendered still that was planned exactly this way, written first, locked to tokens, generated, then checked. Nothing was shot in a studio we are hiding. The images are built from the same file as the words, and you can inspect any of them. on-screen: These stills came from the plan |
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→These stills came from the plancurate nodes, steps | |||||||
| 7 | ![]() matches intent KpiGrid template | proof | 130.8–152.8s | receipts-count | icon·wireframe | ♪ node_lock | So photography as a system is four steps: write the shot, lock the look in tokens, generate from a reference, and let the machine grade the frame. Do that and your images stop being lucky and start being repeatable. See the whole set, planned in public, at office dot temerarii dot xyz, and copy the parts that fit your brand. on-screen: Plan the photo, then make it |
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Plan the photo, then make itcurate kpis, statsLabels | |||||||
| 8 | ![]() matches intent shared field signature-3d | resolve | 152.8–161.60000000000002s | coalescence | icon·white-knockout | ♪ bed_out | Chapter seven. Custom apps and dashboards: own the code and the IP. You keep the source, so the tool is yours to change. on-screen: Chapter 7 |
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→Chapter 7 | |||||||