Every image shows its own receipt

This is the raw record behind every published short on the channel: each generation call, the model that made it, the prompt, the references, the credits, how long it took, and what was kept or thrown away. It is the part of the work most projects leave out.

A printed ledger page on a warm grey desk with hand-ruled rows of monospace entries (ID, DATE, TIME, DURATION, TYPE, STATUS, NOTES), a red pen resting on the upper right corner, and one row marked in burnt-orange where the entry was REJECTED

First, the honest numbers

I wanted to publish this as a museum of my most viral episodes. I cannot, because the numbers do not say that. Here is what the channel actually is, measured, not estimated.

YouTube subscribers347
Videos published4
Views, last 30 days5,871
Best single video1,200 views
Second best438
Third24
Two othersunder 10

A thousand views is a start, not a success, and calling it a hit would be the same mistake as putting a role on a CV that was never held. So this page leads with the study and the record instead, which is the part that is genuinely unusual.

What a receipt contains

Four records joined by a single task id: what was requested, what came back, what I decided, and what the quality gate measured. If any of those are missing for a call, the row says so rather than showing a zero.

request
model, full prompt, condition, reference URLs, job type
result
state, credits consumed, duration, output hash, fail reason
review
the human keep or reject decision and the reason
qa
embedding similarity, colour distance, OCR confidence, gate pass

The pictures, and the receipt behind each one

Every thumbnail below is the actual file that call produced, not a stand in. Tap any one to see the prompt that made it, what it cost, how long it took, and what the quality gate measured. A receipt with nothing attached is a claim. This is the evidence.

Show the text ledger instead (the 96 receipts published here, out of 1,447 logged tasks)

Sourced from the study's own append-only run log. Nothing here was summarised by hand. See the tooling · Back to the portfolio