Define the explanation job before choosing a product

Treat “what's next image” as a definition and explanation request, not as evidence that a feature exists. The action implied by the query is to resolve a factual or conceptual question; the working object is still image. Write the intended audience or user, authorized input, desired change, review owner, and finished handoff. Also state what the task excludes. This brief keeps search wording from turning into an unsupported promise about SEELE, a named vendor, a model, or an automatic result. Before approval, preserve the continuity note, and ask the production lead to record claim scope before the production checkpoint.

• Input: an authorized original, a precise change brief, protected identity and product details, and a target size or delivery condition Before approval, preserve the claim inventory, and ask the source custodian to record source fidelity before the production checkpoint.
• Success: a reversible image revision that preserves intended identity, factual attributes, composition, and provenance while meeting the stated handoff Before approval, preserve the authorization record, and ask the continuity editor to record human approval before the editorial approval.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the failure note, and ask the creative lead to record format readiness before the editorial approval.

Use the concept explanation method

Move from a plain-language definition to one visual or production example, one counterexample, and a small observation exercise. Explain the durable concept first; treat named software, model behavior, and trend language as separate evidence questions. For this query, define the term, contrast adjacent meanings, and test understanding with an example. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The concepts-explainers classification determines this learning sequence, while the authoritative taxonomy remains the only owner of the route. This page supplies editorial copy and cannot silently change the category, subhub, or URL. Before approval, preserve the input snapshot, and ask the production lead to record camera logic before the editorial approval.

Apply the image creation and editing boundary

Do not claim that a tool can recover detail that was never captured, guarantee realism, or preserve every factual attribute. Review altered content, rights, and disclosure at full delivery size. Work from an authorized original, a precise change brief, protected identity and product details, and a target size or delivery condition. Review toward a reversible image revision that preserves intended identity, factual attributes, composition, and provenance while meeting the stated handoff. A polished draft is not enough: the reviewer must be able to see which source supports each factual statement, who authorized each asset or identity, and which product behavior is still an unanswered test question. Topic selection alone never establishes safety, availability, quality, or permission. While evidence is current, preserve the claim inventory, and ask the workflow owner to record source fidelity before the final sign-off.

• Preserve an untouched original While evidence is current, preserve the continuity note, and ask the delivery owner to record identity consent before the final sign-off.
• Protect identity and factual attributes While evidence is current, preserve the review copy, and ask the production lead to record source fidelity before the scope confirmation.
• Inspect edges, texture, scale, and provenance While evidence is current, preserve the test fixture, and ask the accessibility reviewer to record identity consent before the scope confirmation.

Record evidence, review the handoff, and name the next check

A useful explanation lets a reader distinguish the concept from a nearby idea and apply it to a new example without depending on a vendor interface or an unsupported capability statement. Run separate passes for craft, factual accuracy, identity and source rights, safety, accessibility, and destination requirements. Record the source and verification date for any changing platform, model, price, policy, privacy, export, or compatibility statement. If primary evidence is missing, publish the item only as a question or editorial planning step. The finished handoff must name the approver and preserve a path back to the authorized original. For a controlled test, preserve the decision history, and ask the policy reviewer to record source fidelity before the rights check.