The Approach With No Movement

One folder holds 3 files and nothing else, and together they weigh 8,496 bytes. There is a plan: blocking.json, 1,793 bytes, sha256 72c7ce503f8f4738. There is a receipt: manifest.json, 1,277 bytes, sha256 46bf431be10cdb36. And there is the script itself: shots.json, 5,426 bytes, sha256 66911145510d5e8d. The two older files were written 0.001 seconds apart on 2026-08-31 at 19:21:07, which is what two documents emitted by one script look like. The manifest arrived 22.97 days later, on 2026-09-23 at 18:41:09. So the file that says what was rendered is 23 days younger than the files that say what to render, and it is the smallest of the three. Read in that order - plan, dialogue, receipt - and the folder tells its own story about which document gets maintained and which one gets left behind.

blocking.json has 2 keys. One is goal and the other is shots. The goal is a single sentence of 16 words and 99 characters: Mara approaches Elias from the doorway to an intimate distance; Elias stays anchored at the window. That is the premise of the scene, and it sits inside 1,793 bytes for the whole file, which is 298.83 bytes a shot across the 6 the second key holds. Everything the piece is about is carried in that one clause: a movement, a start point, an end point, and a second character who does not take part in any of it. The sentence is doing the work of a director, a shot list and a continuity note at once. Hold the claim next to the rest of the file and the question the folder answers is not whether the scene is any good. It is which of those two clauses the file can actually express.

Break the shots key open and there are 6 shots carrying 9 character entries between them. Elias appears in all 6. Mara appears in 3. Every entry carries the same 6 keys: name, position, end_position, proxemic, movement and facing. Then read the values. Movement reads none in 9 of 9. End position equals start position in 9 of 9. Not one character is declared as arriving anywhere they were not already standing. This is worth stating precisely because it is not an omission. The column exists, it is populated, and the population is the word none. The file states stillness rather than leaving a blank where a movement would go. A renderer reading movement and position alone would receive 6 static frames and no reason to suspect anything had been lost, because nothing in those 2 columns is missing.

Now read the positions column as a set: window 6 times, doorway 1, mid-room 1, close 1. Elias is the window in 6 of 6 entries, first shot to last. Mara carries the other 3: doorway, then mid-room, then close. Then read the proxemic column: social 4 entries, personal 3, intimate 2. Sorted by shot, the bands run social on 1, 2 and 3, personal on 4 and 5, intimate on 6. That is a monotone tightening across the scene, and it is the only column in the file that changes. So the approach does exist. It is written on the axis that classifies distance, not on the axis that instructs a body, and the 2 axes disagree: the proxemic label crosses 3 bands while the movement value stays none 9 times out of 9. The probability that a reader stages these 6 shots as 6 static frames is high, and it is not certain, because a careful reader will notice that the last 2 shots say intimate.

1,277 bytes for 6 rows.

Three of the 9 entries carry a 7th key. The other 6 carry 6. The 7th is transition, and it appears on Mara's entries only: enter on shot 2, offscreen on shot 4, offscreen on shot 6. So the one character the goal sentence moves is the one character whose movement the file is willing to describe, and 2 of her 3 declarations say the movement happens off screen. Those 2 are shots 4 and 6, which are the shots where the band changes from social to personal and then from personal to intimate. The tightest moments in the scene are the 2 explicitly marked as happening outside the frame. One more column shows the same pattern. Facing runs Mara 5 times, Elias 3 and door once. Elias turns toward the door in shot 1 and never again. After that he faces her in every entry that names him, and she faces him in all 3 of hers.

manifest.json is 1,277 bytes for 6 rows and 5 fields each, 212.83 bytes a row, and the field order never varies: num, character, status, taskid, url. Status reads done in 6 of 6. The taskids are 2,904,116, 2,904,142, 2,904,175, 2,904,214, 2,904,262 and 2,904,298 - 6 distinct 7 digit numbers, ascending, 182 apart end to end, with gaps of 26, 33, 39, 48 and 36. Then the urls. All 6 point at one host, cdn1.wiro.ai, and all 6 end in the same leaf name, output.mp4, so no url carries a shot number and the only thing tying a url to a row is the row's own order. The 6 parent directories are 71 characters each, built from 8 groups of 8, and they collapse to 2 lead chains of 3 rows apiece: shots 1, 2 and 3 under one, shots 4, 5 and 6 under the other. The break in the hosting falls exactly where the proxemic band falls, between shot 3 and shot 4. Two render sessions, two distances, and one seam both documents share. Beside all of it, shots.json holds 6 lines of 6 to 15 words, 6 prompts of 105 to 116 words, and 6 output paths rooted in a home directory on a different machine, none of which resolve. The dialogue file points at files nobody has. The receipt points at files that exist. The plan points at a movement that no column carries.