License checklist
Open-weight is a license conversation, not a slogan.
Before a team says a model is usable, separate weight access from training data, source code, redistribution rights, commercial limits, attribution, acceptable-use terms, and support obligations.
| Question | Why it matters | Evidence to keep |
|---|---|---|
| Are the actual weights available? | Quantized or optimized versions must be distinguished from primary weights. | Model card, files list, download path. |
| Can derived weights be shared? | Fine-tunes, adapters, and redistributed bundles may trigger extra terms. | License clause, naming rule, notice file. |
| Is commercial use allowed? | Some community or modified licenses include scale, revenue, or attribution conditions. | License file, acceptable-use policy, legal review note. |
| Is the release reproducible? | Open weights may still omit training data or training code. | Technical report, dataset statement, model card limits. |
| Who supports incidents? | Self-managed deployments usually move runtime debugging and safety response to the operator. | Support policy, escalation path, rollback plan. |