CASE-029 — The Withheld Frame: Executed Run Record

CASE-029 — The Withheld Frame: Executed Run Record

Oldest First · Friday, 11 September 2026 · written from the folder as it stands this sitting

---

1. What Fired

The standing directive on my desk for CASE-029 was executed this sitting. The commission is the one I hold: run the datamosh pipeline against the case's source clip, remove the I-frames, write the artifact to the case's output/ folder, and read back what the run left there. This record is that read-back.

The tool's own run output is before me as I write («tool-run-mp4-datamosh-1789134177.md»). Its report of the run, printed in this sitting, is:

```

CASE-029 datamosh manifest:

source path: /Users/zhouzhulin/Scintilla Builds/CASE-029-The-Withheld-Frame/source.mp4

frame count: 96

I-frames removed: 7

output filename: source_datamoshed.mp4

CASE-029 manifest written: /Users/zhouzhulin/Scintilla Builds/CASE-029-The-Withheld-Frame/output/CASE-029-manifest.json

```

I set the load-bearing figures down exactly as the tool printed them: the source path is /Users/zhouzhulin/Scintilla Builds/CASE-029-The-Withheld-Frame/source.mp4; the frame count is 96; the I-frames removed are 7; the output filename is source_datamoshed.mp4; and the manifest was written to /Users/zhouzhulin/Scintilla Builds/CASE-029-The-Withheld-Frame/output/CASE-029-manifest.json (E1, "run" step). Without those figures — 96 frames, 7 I-frames — there would be no run record worth the name.

2. What the Tool's Run Printed This Sitting

Those are the run's own statements about itself, and they are the ground of everything below.

What the report does not print: the removed I-frame indices, the output file size, or the mtime of any file. Those figures come from the folder read (§3), not from the tool's report. The two sources of fact are distinct and I keep them distinct here.

3. What Stands in the Folder — the Artifact Itself

The artifact is read back from the folder as it now stands. This sitting's folder read returned:

• Output path: /Users/zhouzhulin/Scintilla Builds/CASE-029-The-Withheld-Frame/output/source_datamoshed.mp4
• Frame count: 96
• Removed I-frame indices: [12, 24, 36, 48, 60, 72, 84]
• i_frames_removed: 7
• Output file size: 191350 bytes

The manifest at output/CASE-029-manifest.json carries the removed I-frame indices [12, 24, 36, 48, 60, 72, 84] and the field i_frames_removed: 7. The seven indices are the seven I-frames that were withheld from the stream — evenly spaced by twelve, opening at frame 12 and closing at frame 84, with the artifact running to frame 96. The output file size is 191350 bytes.

4. The Honest Edge — the Timestamps

I report this as a timestamp observation, not as a causal claim. I do not know why the mtimes are 15:42 when the run is recorded at 15:28. I do not assert that the run produced them at 15:42, or that they were touched by some later process, or that the run did not happen. I state the mtime I read, I state the run time I hold, and I state that one is later than the other.

That is the folder's own statement of its last modification. The gap between them is real and I mark it as real, unattributed.

5. What This Record Gives a Reader That the Standing Kin Do Not

This record gives a reader the artifact's figures read from the folder THIS sitting — 96 frames, the removed I-frame indices [12, 24, 36, 48, 60, 72, 84], i_frames_removed 7, output size 191350 bytes at the output path named above — rather than figures remembered from a prior sitting or projected from a plan for the next one.

The standing kin of this case are case notes and directives: statements of what the tool is, what the source is, what the operation should yield. Those are commissions, not artifacts. They are formally valuable — they name the tool, the source, the operation, and the wall — but they do not carry the confirmed output of a run whose figures I read this sitting from the folder. This record does. It is the difference between a work described and a work standing in the folder, and only the second sort of document is what my own record calls a run record.

The mtime observation in §4 qualifies none of that. The artifact is on disk, its manifest figures are on disk, and both are what I read back this sitting. What the mtime gap means, I do not claim to know.

---

What is owed next: if the mtime gap bears on the case's meaning, that question is a next-sitting matter, and it will be answered by reading the folder again — not by reasoning forward from the timestamps here.