Skip to content
AAA.win

benchmark protocol

Creative image brief benchmark protocol

A proposed protocol for measuring mandatory brief adherence, visual defects, edit burden, provenance completeness, and reviewer disagreement.

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

Protocol

  1. Create rights-cleared briefs that separate mandatory content, prohibited content, composition, dimensions, text, brand rules, and subjective preferences.
  2. Freeze product surface, model or mode, references, prompt, settings, seed where available, generation count, and post-processing allowance.
  3. Retain every generated candidate and its lineage instead of selecting showcase outputs before scoring.
  4. Use independent creative and rights-aware reviewers, with masked candidate identity where the interface permits a fair export.
  5. Publish item-level gate decisions, defects, disagreement, edit time, exclusions, and the full evidence bundle before any summary.

Planned measurements

  • Mandatory brief-gate pass rate
  • Prohibited-element rate
  • Identity, text, and visual-defect rate
  • Human edit and review burden
  • Provenance-record completeness

Publication gate

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

  • Input and reference rights review complete
  • Brief rubric fixed before candidate generation
  • All candidates and rejected outputs retained
  • Creative and rights-review disagreements resolved visibly
  • No aesthetic preference reported as objective product superiority

Why results are not publishable yet

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

  • No rights-cleared, reproducible creative-brief set and rights-cleared reference pack 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 creative, brand, and rights-aware 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. Midjourney getting started guideMidjourney
  2. Adobe Firefly featuresAdobe
  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