engine.sim.memory review longform-W24-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–23.8s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | One machine, eight pillars, still rolling. Today is illustration, the drawn look of a brand. The trap with AI images is that every one comes out in a different style, so your brand ends up a mess of mismatched pictures. We are going to teach you to lock one look and reproduce it, so your illustrations all feel like they came from the same hand. on-screen: Illustration with one locked style |
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→Illustration with one locked style | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 23.8–46.8s | kinetic-build | icon·white-knockout | ♪ node_lock | Step one. Before generating anything, write your illustration style as a short paragraph: flat shapes, thick lines, your three brand colors, no gradients, plain backgrounds. This is your style sheet in plain English. Every image you ask for will start with this exact paragraph, so the model knows the look before it knows the subject. The words come first; the picture obeys them. on-screen: Write a style sheet in words |
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→Write a style sheet in wordscurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 46.8–71.3s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Step two. Run your prompts through an image model on Replicate or fal, services that let you call a model from a single API request, right from the terminal. You paste your style paragraph, add the subject, and get an image back. Because it is an API call, you can script it, repeat it, and keep every setting identical instead of clicking around a website each time. on-screen: Generate through Replicate or fal |
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→Generate through Replicate or falcurate items, nodes | |||||||
| 4 | ![]() matches intent CodeWindow template | teach | 71.3–95.1s | kinetic-build | icon·white-knockout | ♪ node_lock | Step three. The real trick is the seed, a number that controls the randomness. Use the same seed and the same style paragraph, and the model draws in a steady, matching look across different subjects. Change the subject, keep the seed. Write that seed down in your brand file next to your colors. Now your illustration style is a saved setting, not a happy accident. on-screen: Reuse one seed to stay consistent |
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Reuse one seed to stay consistentcurate codeLines, nodes, windowTitle | |||||||
| 5 | ![]() matches intent StatScoreboard template | proof | 95.1–118.89999999999999s | receipts-count | icon·liquid-chrome | ♪ node_lock | Our proof is the cast of characters across the studio. We built them in one code-native style and kept it locked, so they read as one family no matter the scene. We did not redraw them per video and hope they matched. We wrote the look down, pinned the settings, and reused them, which is why they feel like one brand and not eight strangers. on-screen: Our characters hold one look |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our characters hold one lookcurate pillar, stats, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 118.9–142.3s | coalescence | icon·liquid-chrome | ♪ bed_out | So consistent illustration is a written style plus a locked seed, not luck. Write the look in words, generate through an API, pin the seed, save it. Your next step: write three sentences describing how your brand should draw, before you generate a single image. You can see our locked cast holding one look across the whole calendar at office dot temerarii dot xyz. on-screen: Build your style sheet at the office |
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→Build your style sheet at the office | |||||||