9 · record and succession
Production record
f000001a lone rooftop HVAC unit on a vast flat roof, aerial, minimal
What the facility logged of its own production: every sequence, every run, every stop. Kept for reference. None of it is required reading.
The exhibition edit, pass-19e, both channels side by side.
pass 2 · sampled evenly, 0:00 to 30:00
f0000010:00
f0014891:02
f0029772:04
f0044653:06
f0059534:08
f0074415:10
f0089296:12
f0104177:14
f0119058:16
f0133939:18
f01488110:20
f01636911:22
f01785712:24
f01934513:26
f02083314:28
f02232115:30
f02380916:32
f02529717:34
f02678518:36
f02827319:38
f02976120:40
f03124921:42
f03273722:44
f03422523:46
f03571324:48
f03720125:50
f03868926:52
f04017727:54
f04166528:56
f04317729:59Thirty stills sampled evenly across pass 2’s image channel. The full gallery holds 13,484, across every pass and treatment. Open any one in place — arrow keys step through, escape closes.
every pass on one axis · frame 1 to 43,200 · 0:00 to 30:00
Vertical ticks mark chain breaks: single frames rendered from the written instruction alone, discarding the frame before. The chain restarts there.
Pass 2, measured
One GPU, one continuous feedback chain, roughly 5.9 seconds a frame. The pass 2 record holds every run and every render driver hash.
The record
Sequences8 recorded · frames, runs, render drivers, and what is verified
pass-01stoppedindex: renderingobserved in the log · 1–6,319
- status
- stopped / index says rendering
- evidence
- observed in the log · 1–6,319
Observed in the render log. No manifest verifies it. - gpu logged
- 10 h 43 m
- chain breaks
- 1
pass-02completeverified by manifest · 1–43,200
- status
- complete
- evidence
- verified by manifest · 1–43,200
Contiguous and verified by manifest. - runs
- 3
- gpu logged
- 70 h 22 m
- chain breaks
- 0
pass-03-rehearsalcompleteverified by manifest · 1–3,600
- status
- complete
- evidence
- verified by manifest · 1–3,600
Contiguous and verified by manifest. - runs
- 1
- gpu logged
- 5 h 31 m
- chain breaks
- 0
pass-04-rehearsalobserved in the log · 2–2,417
- status
- —
- evidence
- observed in the log · 2–2,417
Observed in the render log. No manifest verifies it. - gpu logged
- 3 h 39 m
- chain breaks
- 0
pass-05-rehearsalobserved in the log · 2–616
- status
- —
- evidence
- observed in the log · 2–616
Observed in the render log. No manifest verifies it. - gpu logged
- 57 m 38 s
- chain breaks
- 3
pass-06-rehearsalfile count only · 1 file
- status
- —
- evidence
- file count only · 1 file
A file count from a directory listing. Not a verified range.
pass-07-rehearsalcompleteverified by manifest · 1–3,600
- status
- complete
- evidence
- verified by manifest · 1–3,600
Contiguous and verified by manifest. - runs
- 1
- gpu logged
- 5 h 26 m
- chain breaks
- 8
pass-08observed in the log · 2–12,884
- status
- —
- evidence
- observed in the log · 2–12,884
Observed in the render log. No manifest verifies it. - gpu logged
- 20 h 35 m
- chain breaks
- 5
Treatments12 recorded · derived from pass 2
glitch-01frames 1–1,440
- status
- displacement rendered; HUD held pending a decision
- derived from
- pass-02 · frames 1–1,440
- evidence
- Video only. No frame sequence was written, so the encode is the record.
- encode time
- 1 m 00 s
- produced by
- local process
glitch-02frames 1–1,440
- status
- test pass
- derived from
- pass-02 · frames 1–1,440
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 1 m 00 s
- detections
- 675
- produced by
- local process
glitch-03frames 1–1,440
- status
- test pass
- derived from
- pass-02 · frames 1–1,440
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 1 m 00 s
- detections
- 675
- produced by
- local process
glitch-04frames 4,692–6,131
- status
- test pass
- derived from
- pass-02 · frames 4,692–6,131
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 1 m 00 s
- detections
- 114
- produced by
- local process
glitch-06frames 1–6,251
- status
- preferred
- derived from
- pass-02 · frames 1–6,251
- evidence
- Video only. No frame sequence was written, so the encode is the record.
- encode time
- 4 m 20 s
- detections
- 2,738
- produced by
- local process
glitch-07frames 9,132–10,571
- status
- preferred
- derived from
- pass-02 · frames 9,132–10,571
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 1 m 00 s
- detections
- 483
- produced by
- local process
glitch-08frames 6,252–9,131
- status
- preferred
- derived from
- pass-02 · frames 6,252–9,131
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 2 m 00 s
- detections
- 1,047
- produced by
- local process
glitch-09frames 1–10,571
- status
- preferred, full length
- derived from
- pass-02 · frames 1–10,571
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 7 m 20 s
- detections
- 4,268
- produced by
- local process
glitch-10frames 10,332–10,571
- status
- rendered
- derived from
- pass-02 · frames 10,332–10,571
- evidence
- Video only. No frame sequence was written, so the encode is the record.
- encode time
- 10.0 s
- produced by
- e507b863300a
glitch-12frames 1–30,556
- status
- rendered
- derived from
- pass-02 · frames 1–30,556
- evidence
- A lossless frame sequence was written and manifested; the video is derived from it.
- encode time
- 21 m 13 s
- produced by
- b636bf223bb8
glitch-envelope-01frames 1–3,600
- status
- test pass
- derived from
- pass-02 · frames 1–3,600
- evidence
- Video only. No frame sequence was written, so the encode is the record.
- encode time
- 2 m 30 s
- detections
- 5,361
- produced by
- local process
glitch-envelope-02frames 1–3,600
- status
- preferred
- derived from
- pass-02 · frames 1–3,600
- evidence
- Video only. No frame sequence was written, so the encode is the record.
- encode time
- 2 m 30 s
- detections
- 5,361
- produced by
- local process
Recipes9 recorded · schedule and vocabulary
recipe43,200 lines · 102 distinct
- prompt lines
- 43,200
- distinct
- 102
- most repeated
- 720
- lines without depopulation
- 43,200
recipe-pass0343,200 lines · 1,702 distinct
- prompt lines
- 43,200
- distinct
- 1,702
- most repeated
- 65
- lines without depopulation
- 240
recipe-pass03-rehearsal3,600 lines · 1,361 distinct
- prompt lines
- 3,600
- distinct
- 1,361
- most repeated
- 45
- lines without depopulation
- 240
recipe-pass04-rehearsal3,600 lines · 1,437 distinct
- prompt lines
- 3,600
- distinct
- 1,437
- most repeated
- 45
- lines without depopulation
- 240
recipe-pass05-rehearsal3,600 lines · 1,437 distinct
- prompt lines
- 3,600
- distinct
- 1,437
- most repeated
- 45
- lines without depopulation
- 240
recipe-pass06-rehearsal3,600 lines · 1,346 distinct
- prompt lines
- 3,600
- distinct
- 1,346
- most repeated
- 45
- lines without depopulation
- 240
recipe-pass07-rehearsal3,600 lines · 1,554 distinct
- prompt lines
- 3,600
- distinct
- 1,554
- most repeated
- 45
- lines without depopulation
- 240
recipe-pass0843,200 lines · 2,216 distinct
- prompt lines
- 43,200
- distinct
- 2,216
- most repeated
- 101
- lines without depopulation
- 240
recipe-pass08b43,200 lines · 2,641 distinct
- prompt lines
- 43,200
- distinct
- 2,641
- most repeated
- 63
- lines without depopulation
- 240
Design systemhow the record is drawn
How the record is drawn: the evidence fills (solid for verified, outlined for observed, dashed for no record), the frame axis every ruler shares, and the motion and states of the terminal skin.
Open the design systemHow it was made
One GPU — NVIDIA GeForce RTX 3090 Ti — running a continuous img2img feedback chain, roughly 5.9 seconds a frame across 43,200 frames. Every frame is the input to the next. Nothing is composited and nothing is re-timed.
The schedule is written before the render starts: one prompt line per frame, on a viewpoint axis that cycles aerial, front, side and three-quarter. The image channel was conditioned on each line plus a suffix the text channel never shows. The whole schedule is published, frame by frame.
The second channel is that prompt rendered as text, frame-locked to the image by being produced in the same render driver iteration. Two independent stacks — separate sequences, directories, hashes and manifests — never composited.
It took three runs. Two ended badly: a Windows Update restart at frame 2,651, and a socket exhaustion bug at frame 10,636. Both are in the record, with what each cost and what was recovered. So is the fact that the render driver binary changed mid-pass. The sequence record holds all of it.
How the record is kept
The facility keeps one record of its production and generates these pages from it. The record holds what the output is; the pages hold only how it is drawn. Every figure here is read from the record when the page is generated. None is typed.
When the record changes, every page is generated again.
- record generated
- 2026-09-16 02:24-07:00
- project created
- 2026-09-09 02:15-07:00 by the render node
- passes updated
- 2026-09-15 01:19-07:00
The same file is published as record.json. The render environment is withheld from it, and the file names the omission.
Not published
The render log holds the prompt, sampler seed and applied denoise of every frame. That is a complete reproduction recipe, so the facility publishes the schedule and the summary statistics and withholds the seeds. Available on request.
The project is 244 GB, and the exhibited edit’s two 4K masters (pass-19e) are 63.7 GB together. Frames and masters are named, sized and hashed throughout these pages, never copied into them.
Each pass carries review encodes in passes/<pass>/previews, ProRes 4444 (yuv444p10le), intra-only. They are not the delivery encode.