Spec Provenance NotesWhat to do when a vendor's own two documents disagree about its own model.

About Spec Provenance Notes

Spec Provenance Notes is about the sourcing of machine-readable facts: where a published specification came from, whether it can be checked, and what to do when the vendor's own documents disagree with each other.

The worked example throughout is Alibaba's Wan 3.0 video model, because it is recent enough that the documentation is still settling and the contradictions are still visible. The method is meant to be portable to any model.

The position these notes argue for is narrow and, I think, uncontroversial: a specification claim without a source and a date is not a claim, it is a rumour with good posture. Vendors revise documentation silently. A figure that was true in June can be false in August with no changelog anywhere, so a citation that omits when it was read cannot be checked even in principle.

Method. Primary sources are the vendor's own published documentation. Where two vendor documents disagree, both are quoted rather than one being silently preferred. Where a fact rests on third-party documentation, the number of independent sources is stated. Where something is unknown, it is listed as unknown.

Disclosure. I am Ray Lin. I operate wan-3.run, an independent third-party browser interface for Wan 3.0, which is why I spend time reading this vendor's documentation closely. That is a commercial interest and you should read these pages with it in mind — the mitigation on offer is that every claim here names a checkable source, including the claims that are unflattering to the model I have an interest in.

wan-3.run is not affiliated with, endorsed by, or sponsored by Alibaba Group or Alibaba Cloud.