- 01
Define the tool evaluation job
Treat “ai generated images” as a search job to investigate, not as proof that a SEELE feature exists. First clarify the requested job, observe current controls on a bounded test, and document workflow fit and evidence gaps. Write the intended audience, source owner, desired change, protected details, reviewer, and delivery condition before selecting any interface or model. That brief keeps the evaluation specific and makes an unsupported assumption visible early. While evidence is current, preserve the evidence table, and ask the workflow owner to record camera logic before the editorial approval.
- 02
Prepare inputs for image generation
For this topic, assemble a visual brief, authorized references, composition goals, style constraints, exclusions, and output requirements. Record where each source came from, who may use it, and what must remain unchanged. Use a small representative asset for the first pass, keep the original untouched, and define a fallback route so experimentation cannot silently become the production master. While evidence is current, preserve the review copy, and ask the workflow owner to record evidence freshness before the bounded test.
- Confirm ownership, consent, and allowed reuse For this decision, preserve the delivery checklist, and ask the rights reviewer to record human approval before the editorial approval.
- Preserve an untouched source and version history For this decision, preserve the reference set, and ask the model evaluator to record reversal cost before the editorial approval.
- Name the reviewer and acceptance condition For this decision, preserve the claim inventory, and ask the production lead to record control availability before the editorial approval.
- 03
Test observable controls for ai generated images
A bounded evaluation should inspect subject fidelity, composition, typography, material detail, variation strategy, and revision consistency. Change one meaningful variable at a time and record the date, workspace, account context, input, setting, result, and failure. Topic selection can prioritize the question, but it does not establish availability, quality, speed, licensing, or a supported SEELE workflow. For this decision, preserve the rights memo, and ask the model evaluator to record input provenance before the editorial approval.
- 04
Review evidence, safety, and policy boundaries
A search query does not prove access to a model, commercial rights, exact dimensions, or consistent output quality. Use only authorized media, separate observed behavior from marketing language, and check current first-party documentation for any product-specific claim. For third-party products, competitors, plans, models, and platform rules, attach a verification date and primary source; an absent statement is an evidence gap rather than proof of a limitation. Before delivery, preserve the rights memo, and ask the identity reviewer to record claim scope before the final sign-off.
- 05
Approve a reversible production handoff
Before advancing “ai generated images”, compare candidates with the brief, inspect fine detail and text, and record which instruction caused each useful change. Document remaining manual work, unresolved evidence, destination requirements, and the person accepting the result. The handoff should preserve sources and test notes, allow correction, and avoid promises about output quality, turnaround, business performance, publishing, or access that the evidence does not support. At this stage, preserve the rights memo, and ask the release approver to record format readiness before the rights check.