Define the verification job before choosing a product

Treat “is wan 2.6 open source” as a yes-or-no verification 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 named model or platform. 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 creative lead to record control availability before the dated decision.

• Input: the exact product, provider, version, region, account surface, production job, and verification date Before approval, preserve the claim inventory, and ask the model evaluator to record disclosure clarity before the dated decision.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps Before approval, preserve the authorization record, and ask the rights reviewer to record temporal order before the dated decision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the failure note, and ask the channel editor to record revision intent before the dated 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, identify the claim, the authoritative source, the date, and the conditions that could change the answer. 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. Before approval, preserve the input snapshot, and ask the creative lead to record reversal cost before the reversible handoff.

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. Before revision, preserve the claim inventory, and ask the channel editor to record format readiness before the release review.

• Confirm exact provider and version Before revision, preserve the continuity note, and ask the release approver to record human approval before the release review.
• Date every changing fact Before revision, preserve the review copy, and ask the workflow owner to record format readiness before the production checkpoint.
• Keep observations separate from documentation Before revision, preserve the test fixture, and ask the delivery owner to record reversal cost 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. While evidence is current, preserve the decision history, and ask the accessibility reviewer to record format readiness before the reversible handoff.