Operating sequence
Compare the ambiguous Wan 2.0 label with the officially documented Wan 2.1 release using identity, task families, repository evidence, access path, and matched production tests.
- 01
Compare identity and evidence
For each side, record the provider, exact identifier, official page, repository, release date, license, interface, and region. Missing evidence is a decision risk, not a feature difference.
- 02
Use one matched creative brief
If both paths can be verified and accessed lawfully, run the same text-led and image-led jobs with the same inputs, frame, attempt budget, and acceptance rubric.
- 03
Separate capability from operating fit
Document output observations, infrastructure, access, integration effort, moderation, rights process, editorial repair, support, and delivery compatibility. Do not turn repository claims into measured production results.