engine.sim.memory review longform-W26-Mon 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–27.7s | spatial-parallax | icon·white-knockout | ♪ bed_in | If it works on us, it works for you. Today, the logo. Most people think a logo is a pretty picture you commission once and frame. It is not. A logo is a set of rules: where it sits, how small it can go, what it must never touch. Today I will show you how we treat our own mark as code, so it behaves the same on a phone, a sign, and a video frame. on-screen: A logo is a rule, not art |
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→A logo is a rule, not art | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 27.7–52.2s | kinetic-build | icon·ember-fill | ♪ node_lock | First move: save the logo as an SVG, not a flat picture. SVG is just text that describes shapes, so it stays sharp at any size and you can recolor it with one line. We keep our mark, the white lockup, as a single file every tool points to. One file, one truth. When the mark changes, it changes everywhere, because everything reads from that one path. on-screen: Store the mark as one SVG |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Store the mark as one SVGcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 52.2–77.4s | kinetic-build | icon·wireframe | ♪ node_lock | Second move: write the placement rules in plain text next to the file. Ours says one clear rule we live by: show the mark, never spell the name typed onto the art. We enforce that with a small check we call verify-no-written-name. It scans a piece and fails it if the wordmark got typed in by hand. A rule a machine can check is a rule that actually holds. on-screen: Write down where it can go |
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→Write down where it can gocurate items, nodes | |||||||
| 4 | ![]() matches intent JsonDiff template | teach | 77.4–102.60000000000001s | kinetic-build | icon·white-knockout | ♪ node_lock | Third move: hand the SVG and the rules to the coding agent. Now when it builds a post or a video, it drops the mark in the right corner, at the right size, every time. You are not nudging a logo by hand across a hundred files. The agent reads the placement rule once and obeys it forever. That is the difference between a logo and a logo system. on-screen: Let the agent place it for you |
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let the agent place it for youcurate fileName, lines, nodes | |||||||
| 5 | ![]() matches intent StackTrace template | teach | 102.6–122.8s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Here is the self-proof. Our mark runs through this exact pipeline on every single piece we publish. Same SVG, same rules, same check. It sits on black grounds, white grounds, and red grounds without breaking. We did not test it in a slide deck. We tested it by shipping it, in public, over and over. on-screen: It survived our own machine |
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→It survived our own machinecurate errMsg, errType, fix, frames, nodes | |||||||
| 6 | ![]() matches intent ListCard template | teach | 122.8–144.8s | kinetic-build | icon·ember-fill | ♪ node_lock | Your next step is small. Get your logo as an SVG. Write three placement rules in plain text. Add one check that catches misuse. Then let an agent place it for you. You can see our mark living across the whole calendar at office dot temerarii dot xyz. A logo that follows rules is a logo that keeps its promise. on-screen: Treat your mark like ours |
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id ListCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Treat your mark like ourscurate items, nodes | |||||||
| 7 | ![]() matches intent KpiGrid template | proof | 144.8–152.5s | receipts-count | icon·wireframe | ♪ node_lock | Chapter six. Custom apps and dashboards: own the code and the IP, so no vendor can hold your tools hostage. on-screen: Chapter 6 |
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→Chapter 6curate kpis, statsLabels | |||||||
| 8 | ![]() matches intent shared field signature-3d | resolve | 152.5–158.8s | coalescence | icon·white-knockout | ♪ bed_out | Chapter seven is next. We tie every dollar you spend to a result you can see. 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 | |||||||