How to read AI video examples: an evidence audit of four fixed records

This audit fixes four records: the late-night laundromat example, the telescope fashion example, our reflective-bottle practice, and the task-resume recipe. The first two are source demonstrations, the third is an original teaching method, and the fourth is a local interface fixture. We deliberately chose different evidence levels. Four purposive records are neither a random sample nor a model leaderboard.

We ask six separate questions: can the source be traced, can inputs be inspected, is the prompt visible, is the submitted request disclosed, can an output be tied to that request, and are all attempts recorded? “Not disclosed” means absent from the selected record we inspected. It does not mean the author never retained it, and unknown failures cannot become zero failures.

An attractive clip answers what one displayed result looks like. A connected input and execution record starts to answer whether someone else can inspect how it was produced. Both are useful questions, but they require different evidence.

In the built-in browser, the laundromat player reported 15.104 seconds and 1280×720 pixels. The visible prompt requests 15 seconds and 16:9, while the parameter panel labels the aspect ratio unspecified. These values come from different layers: the player describes a file, the prompt expresses an instruction, and accepted generation settings require a request record. Approximate agreement between the first two does not supply the missing third layer.

The telescope page lists four reference inputs, and its player also reported 15.104 seconds and 1280×720. Linked inputs make the disclosed materials easier to inspect. The selected public record did not disclose a request ID, accepted parameters, all candidate outputs, or an editing log. Four linked images do not establish how the underlying system encoded, ordered, or reused those images.

The bottle practice provides an illustration, a reusable prompt and review criteria. Its page explicitly says model output has not been independently tested. Complete teaching materials help a reader begin; they do not prove that reflections, trademarks or real photos will remain faithful. Calling a downloadable method a verified effect would cross that boundary.

The task-resume recipe did execute 24 local interface scenarios. Its receipt also says the download fixture is only 64 synthetic bytes with an MP4 header: it was not decoded as a real video, and no provider generation task was submitted. That supports particular status branches, file protections and download checks. It does not establish model speed, visual quality or production delivery success.

Nor does a polished source demo supply a success rate. If only a chosen output is shown, we do not know the number of attempts, abandoned inputs or subsequent edits. A percentage without its denominator is speculation. We make no assertion about the sample authors’ actual private workflows and no ranking between models.

For a future production, retain versions and hashes for input files, the prompt, accepted parameters and final output, then connect them with a request or task ID. Remove keys and privileged download links from public records. A hash establishes file identity, not visual correctness; it does not replace watching and reviewing the result.

A reproduction claim needs an actual rerun of the same inputs and settings, with differences recorded. A stability claim needs predefined acceptance criteria, every attempt recorded and the sample selection described. Cropping, composited text and result selection belong in the delivery history instead of being attributed silently to the model.

This article does not reproduce the templates’ operating instructions. The downloadable audit JSON and CSV identify our selected records, known fields and remaining unknowns. Follow the technical recipes or delivery workflow for execution steps, keeping evidence analysis and task execution clear in their respective roles.