Define the orientation job before choosing a product

Treat “吉卜力风格ai” as a broad orientation request, not as evidence that a feature exists. The action implied by the query is to clarify the term and choose the next production decision; the working object is editorial topic. 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 delivery checklist, and ask the workflow owner to record input provenance before the fallback decision.

• Input: an authorized original, a precise change brief, protected identity and product details, and a target size or delivery condition Before approval, preserve the reference set, and ask the delivery owner to record camera logic before the fallback decision.
• Success: a reversible image revision that preserves intended identity, factual attributes, composition, and provenance while meeting the stated handoff Before approval, preserve the rights memo, and ask the delivery owner to record evidence freshness before the acceptance review.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the evidence table, and ask the continuity editor to record failure conditions before the acceptance review.

Use the category discovery method

Start by defining the term or named product in neutral language, then separate the reader's likely production job from brand recognition, spelling variants, and search popularity. Build a shortlist of questions before opening any workspace or vendor page. For this query, clarify the intended meaning and production job before choosing a process or product. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The category-discovery 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 handoff draft, and ask the accessibility reviewer to record camera logic before the acceptance review.

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. At this stage, preserve the brief version, and ask the release approver to record failure conditions before the release review.

• Preserve an untouched original At this stage, preserve the source ledger, and ask the channel editor to record evidence freshness before the release review.
• Protect identity and factual attributes At this stage, preserve the reference set, and ask the release approver to record identity consent before the controlled revision.
• Inspect edges, texture, scale, and provenance At this stage, preserve the delivery checklist, and ask the channel editor to record claim scope before the controlled revision.

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

The handoff should state what the reader now understands, which interpretation remains uncertain, and which official source would be needed before a product-specific conclusion is publishable. 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. Before delivery, preserve the evidence table, and ask the claims reviewer to record failure conditions before the rights check.