Define the orientation job before choosing a product

Treat “wan2.5 preview” 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. For a reversible workflow, preserve the failure note, and ask the channel editor to record claim scope before the fallback decision.

• Input: the exact product, provider, version, region, account surface, production job, and verification date For a reversible workflow, preserve the authorization record, and ask the rights reviewer to record visible continuity before the fallback decision.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps For a reversible workflow, preserve the claim inventory, and ask the model evaluator to record input provenance before the fallback decision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For a reversible workflow, preserve the continuity note, and ask the creative lead to record camera logic before the fallback decision.

Use the dated model guide method

Record the exact provider and version named by the query, the access surface being evaluated, the verification date, and the production job. Turn inputs, controls, limits, pricing, privacy, and output behavior into evidence questions until primary sources are attached. 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 model-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 a reversible workflow, preserve the brief version, and ask the identity reviewer to record visible continuity before the acceptance review.

Apply the named platform or model facts boundary

Do not infer SEELE support, model access, quality, legitimacy, censorship, ownership, API behavior, or compatibility from the query. Verify first-party documentation and direct observations on the use date. Work from the exact product, provider, version, region, account surface, production job, and verification date. Review toward a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps. 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 continuity note, and ask the factual editor to record identity consent before the release review.

• Confirm exact provider and version At this stage, preserve the claim inventory, and ask the brand reviewer to record source fidelity before the release review.
• Date every changing fact At this stage, preserve the test fixture, and ask the source custodian to record identity consent before the production checkpoint.
• Keep observations separate from documentation At this stage, preserve the review copy, and ask the continuity editor to record source fidelity before the production checkpoint.

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

The record must distinguish documented facts, direct observations, and open questions. A similar name, search result, or third-party demonstration is not enough to establish current availability in SEELE or elsewhere. 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 continuity note, and ask the channel editor to record revision intent before the evidence refresh.