Skip to content
AAA.win

benchmark protocol

Explainer video production benchmark protocol

A proposed protocol for testing script fidelity, scene continuity, audio and caption quality, edit burden, consent evidence, and final-review outcomes.

Preview — no resultsVerified 2026-08-113 official or primary sources

Protocol

  1. Prepare rights-cleared scripts, storyboards, assets, voices, identities, pronunciation guides, captions, and channel requirements.
  2. Freeze product surface, model or mode, template, voice, prompts, settings, export format, edit allowance, and workstation or service environment.
  3. Retain scene versions, generated media, audio, captions, manual edits, failed renders, and reviewer interventions.
  4. Have factual, language, creative, rights, and accessibility reviewers score their assigned dimensions against the same timecoded master.
  5. Publish sample counts, duration, exclusions, per-scene failures, edit burden, disagreements, and inspectable evidence before any summary claim.

Planned measurements

  • Script-meaning preservation
  • Scene continuity and visual-defect rate
  • Pronunciation and caption error rate
  • Consent and provenance completeness
  • Human edit and multimodal-review burden

Publication gate

The page remains preview and noindex until every gate is met.

  • Script, identity, voice, and source-asset rights cleared
  • Timecoded rubric locked before generation
  • Every failed and regenerated scene retained
  • Factual, locale, creative, and accessibility review recorded
  • No showcase clip substituted for the declared sample

Why results are not publishable yet

These are real missing run artifacts and external review conditions—not completed evidence.

  • No rights-cleared, reproducible script, storyboard, pronunciation, caption, and rights-cleared asset set with stable identifiers and expected-answer records has been published.
  • No candidate run has frozen the product surface, model identifier, prompt, settings, tools, region, runtime, dependency versions, and hardware or service environment.
  • No completed run log records sample size, exclusions, failures, interventions, start date, end date, and the exact configuration used for every candidate.
  • No versioned scoring rubric and scoring implementation have been published with examples that another reviewer can reproduce.
  • No blind or independent human-review record signed by factual, language, creative, rights, and accessibility reviewers has resolved disagreements and critical-failure labels.
  • No inspectable input-to-output evidence bundle exposes failed, incomplete, excluded, and successful cases rather than only selected examples.

Sources checked

Open the original pages before relying on a time-sensitive product decision.

  1. Getting started with generative videoRunway
  2. Creating AI videosSynthesia
  3. NIST Generative AI ProfileNIST
Version · v4.3.5-indexnow-proof-origin

Latest releases

IndexNow proof-origin protocol fix

Production Bing validation exposed HTTP 500 at the external root proof because TLS termination was followed by an internal rewrite using the wrong protocol. This release corrects that rewrite boundary, but remains unverified until the external proof returns HTTP 200, the automatic submission runs, a later canary returns HTTP 200, and the idempotent rerun passes.

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

IndexNow key-proof compatibility

Changed IndexNow verification to the official root-level {key}.txt convention after the first production notification returned HTTP 403; revalidation remains pending, while the website, sitemaps, and Bing sitemap processing are unaffected.

View all releases