FOLLOW THE ARROWS

[INTRO] A viral clip appears. Caption: A I RECOMP DID THE IMPOSSIBLE. Before believing the caption draw four boxes. [VERSE] First question. What code is running. Original binary. Translated host code. New source. Or another game still alive in the background. Second question. Who owns the state. Who decides where the player is. Who owns inventory. Physics. Combat. Authoritative state tells you which component makes the final decision. Third question. What gets translated. Instructions. Messages. Coordinates. File formats. Shaders. Maybe nothing. Fourth question. What connects the parts. Shared memory. A P I. Converter. Compatibility layer. Adapter. Glue code. [BUILD] Write four labels. CODE. RUNTIME. DATA. GLUE. Then draw arrows. Do not start with the marketing name. Start with boundaries. That is where the architecture becomes visible. [CHORUS] FOLLOW THE ARROWS IGNORE THE CAPTION WHAT CODE RUNS WHO OWNS THE STATE WHERE DID THE DATA COME FROM WHAT GETS TRANSLATED WHAT CONNECTS THE PARTS DRAW THE BOXES FOLLOW THE ARROWS THEN GIVE IT A NAME [VERSE] A renderer can own the pixels without owning gameplay. A second runtime can own physics without creating the map. Assets can be old. Engine can be new. Code can be translated. Audio can be read directly. Another process can still be running. And the integration layer can contain more engineering work than everything visible in the clip. One label often fails because the system has multiple boundaries. Inspect every boundary. [BREAK] If someone says recomp ask which code was recompiled. If someone says rewrite ask where the behavior and implementation knowledge came from. If someone says new engine ask where the maps models textures audio animations came from. If someone says A I did it ask which step. Analysis. Code. Glue. Tests. Converter. Or just the caption. [DROP] CODE RUNTIME DATA GLUE NO MYSTICISM ONLY BOUNDARIES [CHORUS] FOLLOW THE ARROWS IGNORE THE CAPTION WHAT CODE RUNS WHO OWNS THE STATE WHERE DID THE DATA COME FROM WHAT GETS TRANSLATED WHAT CONNECTS THE PARTS DRAW THE BOXES FOLLOW THE ARROWS NOW YOU KNOW WHAT TO SEARCH [OUTRO] Architecture is not what the demo calls itself. Architecture is what runs what owns what transforms and what connects.