engine.sim.memory review longform-W24-Sun 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–29.5s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | This week the calendar says one thing: one machine, eight pillars. Today is the first pillar, branding, and we are going to build a brand the way we build everything here, with rules a machine can follow. A brand is not a feeling. It is a small set of decisions, written down, that you make once and then never argue about again. By the end you will know how to write those decisions so a model can keep them for you. on-screen: Branding is a set of rules |
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape coneground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Branding is a set of rules | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 29.5–56.8s | kinetic-build | icon·wireframe | ♪ node_lock | Step one. Open a plain text file and call it the brand. Not a slide, not a folder of images, a file. Inside it you put the few things that never change: who you serve, what you say no to, and the three words you want stuck in their head. Everything else, every post and ad, gets generated from this file. When the source is one file, the agent always knows where the truth lives. on-screen: Start with one source file |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Start with one source filecurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 56.8–83.4s | kinetic-build | icon·wireframe | ♪ node_lock | Step two. Write your colors as named tokens, not random hex codes scattered around. Red is one value. Black is one value. White is one value. You give each a name and a job. Then in your terminal you feed that list to Claude Code and tell it to use only those three, ever. A model will never accidentally pick a fourth color if a fourth color does not exist in the file. on-screen: Name your colors as tokens |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Name your colors as tokenscurate items, nodes | |||||||
| 4 | ![]() matches intent DiffCard template | teach | 83.4–105.0s | kinetic-build | icon·wireframe | ♪ node_lock | Step three. Pick one typeface and put its name in the file. We use Tahoma, because it is plain and a child can read it. The point is not the font, the point is that it is decided. When the rule is written, the agent sets every headline in it without asking. You stop choosing fonts and start shipping. on-screen: Lock one font, write it down |
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Lock one font, write it downcurate lines, nodes | |||||||
| 5 | ![]() matches intent AnnotatedDiagram template | teach | 105.0–129.1s | kinetic-build | icon·wireframe | ♪ node_lock | Step four, the one most people skip. Make a list of words your brand will never say. Ours bans the empty hype words everyone reaches for, the ones that sound big and say nothing. You hand that banned list to the model as a rule. Now every line it writes gets checked against the list before it ever reaches you. The brand polices its own voice. on-screen: List the words you ban |
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→List the words you bancurate callouts, nodes | |||||||
| 6 | ![]() matches intent SchematicCard template | teach | 129.1–151.79999999999998s | kinetic-build | icon·wireframe | ♪ node_lock | Step five. Describe your voice as if it were one person at a table. We tell the model ours is brash but calm, dry, a little dark, and it explains instead of selling. That short description sits in the file too. When you ask for a caption, the agent writes in that voice, not in the flat tone every other brand shares. on-screen: Write the voice as a person |
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the voice as a personcurate nodes | |||||||
| 7 | ![]() matches intent CheatSheet template | teach | 151.8–174.5s | kinetic-build | icon·wireframe | ♪ node_lock | Step six. Decide how the mark behaves and never bend it. Our rule is simple: the logo stands alone, and we never type the name across an image. We wrote that rule as a check the machine runs, so any asset that breaks it gets flagged before it goes out. One sentence in the file protects the mark on every single post. on-screen: Set the logo rule once |
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Set the logo rule oncecurate nodes, points, uses | |||||||
| 8 | ![]() matches intent TerminalRun template | teach | 174.5–198.3s | kinetic-build | icon·wireframe | ♪ node_lock | Step seven, where it pays off. Point the agent at that one file and ask it to build a week of posts. It reads the colors, the font, the banned words, the voice, the logo rule, and produces work that already obeys all of them. You are no longer briefing a brand every time. You wrote it down once, and the machine applies it forever. on-screen: Make the file generate the work |
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual node-graphshape coneground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Make the file generate the workcurate nodes | |||||||
| 9 | ![]() matches intent StatScoreboard template | proof | 198.3–220.60000000000002s | receipts-count | icon·wireframe | ♪ node_lock | Here is our honest proof. We did not write a brand bible nobody opens. We wrote one source file and pointed the studio at it, and the whole public calendar you are watching came out of it. Same three colors, same plain font, same banned words, every day. You are looking at the output of the exact file we just described. on-screen: We built ours the same way |
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape coneground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We built ours the same waycurate pillar, stats, statsLabels | |||||||
| 10 | ![]() matches intent shared field signature-3d | resolve | 220.6–246.1s | coalescence | icon·liquid-chrome | ♪ bed_out | So that is branding the studio way. Not a mood, a file, with rules a model can hold. Write your source file, name your tokens, ban your words, set your logo rule, then let the agent generate. Your next step is small: open one text file today and write down three colors and one font. You can watch ours run, live and in public, at office dot temerarii dot xyz. on-screen: See the file run at the office |
expected on screen: black ground · cone hero in the shared Signal Field · Augur leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape coneground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→See the file run at the office | |||||||