Attribution and license scope
DINO110k
The DINO110k checkpoint contains the full EMA student inference parameters, including the backbone and adapter. It is derived from Meta's DINOv3. Source: facebookresearch/dinov3. The recorded DINOv3 source revision is 6876159a11b4df116f30f667f8c9888617df0751.
DINOv3 and derivative DINO Materials are distributed under the DINOv3 License, last updated August 19, 2025. The complete license is included as required by Section 1.b.i. The DINO110k derivative remains subject to those terms; it is not relicensed under the Phoenix-MWA code license. DINOv3 is acknowledged as required for research performed using DINO Materials.
Release preparation selected the complete EMA student at step 110000 and removed training-only state. It preserved the selected inference tensors. This is a derived checkpoint and is not an official Meta checkpoint.
CSVAE
The CSVAE checkpoint contains the FP32 1024-to-48 encoder at step 150000. The saved teacher SHA-256 ec83a00d2e65fab98a7f5c15a56700386dbf672dcde275ed7d99f16940650c0c identifies the original full training checkpoint. The accompanying dino110k.pt is its EMA inference export, with a different container SHA-256 81a0082487879332968b5ec458a8d493bf30da601b855cfbaf0e09e250619053; these two file hashes must not be compared as if they described the same container. The CSVAE format migration retained all 118 FP32 tensors exactly and preserves the original teacher provenance. The encoder implementation credits the FastWAM and StarVLA projects, whose code notices remain in Phoenix-MWA.
The available provenance does not establish a separate license grant for Phoenix-owned CSVAE weight contributions. This notice therefore does not infer an MIT or Apache license for those weights from implementation code, nor does it expand any applicable upstream rights.
Scope
These two encoder files are distributed separately from the policies. Wan VAE, T5 and tokenizer weights are not included and retain their own upstream terms. Third-party attribution is retained without implying sponsorship or endorsement. Each component remains subject to its applicable terms; there is no blanket license covering all files merely because the accompanying source code has a software license.