Operating ProcedureExecution layer

Generated Asset Provenance and Rights Check (QA)

A checklist with 7 steps: Require a model and tool manifest for every asset before it enters a client folder.

By InnovaAI ResearchPublished

What are the steps?

checklist

Generated Asset Provenance and Rights Check (QA)

  1. 01

    Require a model and tool manifest for every asset before it enters a client folder

    Record which service produced the file (for example Recraft for vector output, Krea for upscaled renders, PicLumen for photoreal passes) plus the model version and generation date, so a later rights question has a paper trail.

  2. 02

    Confirm the commercial terms of the generating account, not the tool's marketing page

    Check whether the seat is on a paid commercial tier and whether the client's industry is excluded; free tiers and personal plans often carry different usage grants than the enterprise contract the agency signed.

  3. 03

    Screen every prompt and reference upload for third-party marks and likeness

    Reject inputs containing client competitor logos, recognizable faces without a release, or licensed characters; the output inherits the risk even when the model renders something unrecognizable.

  4. 04

    Run a reverse image search on hero assets before client delivery

    Flag any output that returns a near-match to an existing photograph or illustration, then regenerate with a different seed or style reference rather than shipping a possible derivative.

  5. 05

    Log the human edit trail separately from the generation trail

    Note compositing, retouching, and color work applied after generation, since a heavily edited asset may need different disclosure language than a raw render.

  6. 06

    Attach a disclosure line to any asset depicting real people, places, or products

    Draft the wording with the client's legal contact and store it beside the file so downstream channel owners do not improvise their own caption.

  7. 07

    Re-check provenance when a model or vendor is swapped mid-campaign

    A vendor change resets the terms; rerun this checklist on the first batch from any new service before scaling volume across the retainer.