Production validation: results and next tests

Updated 22 September 2026. Preparation is separate from execution.

Local project workspace — implemented

My projects keeps projects, eight-stage progress, writing, shot/asset/attempt records and revision checks in this browser. Checklist JSON contains checks only; full ZIP includes writing and attached files. Use backups outside the browser. No cloud account or paid generator is connected.

Generator benchmark — Veo / Kling pilot recorded

View six actual baseline clips: Veo 3.1 Fast and Kling 3.0 standard. Three tests each, with sources and recorded platform credits. Sampled visual findings include a failed camera-lock instruction. Audio and human playback approval remain unverified. We have not established a best model. Sora, Luma, Pika and Firefly remain untested candidate families. Exact versions, access, settings and cost must be checked when running.

Three-shot test protocol · Blank results ledger

Test identity, physical contact and the next-shot join with the same cleared references. Retain failures and record actual cost. Do not present vendor marketing or three cherry-picked clips as a comprehensive comparison.

From-zero tutorial — review cut and source packet available

Last Parcel now has a 29-second Flow review cut, the reference, all three attempts, shot cards, costs, editable assembly script and QC record. It is not yet a fully approved film: human full-speed picture and sound sign-off are pending. The Agentic revision case study contains real exports and production records, but is not a newly generated three-shot narrative tutorial. The Flow pilot distinguishes quoted costs from the observed total debit, and visual candidates from final approval.

Audience screen — awaiting participants

Download the short, non-leading questionnaire. No viewer responses are claimed. Collect unaided responses before explaining the film; preserve permission before naming a participant.

Content Credentials — production signing pending

Read-only inspection found C2PA manifests in the original Flow reference and three clips, with valid signature/hash results but an untrusted signer flag under the configured anchors. The two edited exports have no detected manifest. Inspection evidence. The provenance ledger and checksums identify sources and exact files. They are not signed Content Credentials. Signing needs a supported implementation and an approved signing credential; a development test certificate must not be presented as trusted production identity.

Verify the signed derivative and hosted download, keeping the original master unchanged. Check signer trust separately from file integrity; do not assume a social platform preserves credentials. See the C2PA FAQ and official trust-list guidance.