Define the procedure job before choosing a product

Treat “how old is a picture” as a step-by-step learning 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. For this checkpoint, preserve the failure note, and ask the delivery owner to record source fidelity before the bounded test.

• Input: an authorized original, a precise change brief, protected identity and product details, and a target size or delivery condition For this checkpoint, preserve the authorization record, and ask the claims reviewer to record claim scope before the bounded test.
• Success: a reversible image revision that preserves intended identity, factual attributes, composition, and provenance while meeting the stated handoff For this checkpoint, preserve the claim inventory, and ask the channel editor to record visible continuity before the bounded test.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For this checkpoint, preserve the continuity note, and ask the release approver to record input provenance before the bounded test.

Use the how-to method method

Translate the request into an input, a reversible action, a checkpoint, and a finished handoff. Practice on a duplicate or non-sensitive sample, preserve the original, and stop when authorization, account access, safety, or factual uncertainty appears. For this query, sequence the work into reversible decisions and observable review points. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The how-to-guides 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. For this checkpoint, preserve the brief version, and ask the factual editor to record identity consent before the dated decision.

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. Before delivery, preserve the continuity note, and ask the creative lead to record claim scope before the editorial approval.

• Preserve an untouched original Before delivery, preserve the claim inventory, and ask the model evaluator to record reversal cost before the bounded test.
• Protect identity and factual attributes Before delivery, preserve the test fixture, and ask the channel editor to record claim scope before the bounded test.
• Inspect edges, texture, scale, and provenance Before delivery, preserve the review copy, and ask the claims reviewer to record reversal cost before the dated decision.

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

The result should be reproducible from the written decisions while leaving product-specific buttons, limits, and account behavior to current official documentation rather than invented steps. 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 this checkpoint, preserve the continuity note, and ask the accessibility reviewer to record input provenance before the controlled revision.