This evergreen explainer offers a way to read AI release announcements without treating the word open as a complete specification. A downloadable model, a public code repository, and a free hosted chatbot can offer very different permissions and technical access. Before deciding what a release enables, ask which components are available and which terms apply to each of them.
Model weights are learned numerical parameters used when a trained model produces an output. Access to those weights can let a developer run a model locally or modify it, subject to the actual license and the tools supplied. It does not automatically supply the training process that produced them. A release can therefore be useful and widely accessible while still falling short of a particular definition of open source.
The Open Source Initiative's Open Source AI Definition, version 1.0, sets out freedoms to use, study, modify, and share a system. For machine-learning systems, it asks for data information, code, and parameters in the preferred form for making modifications. The data-information requirement concerns sufficiently detailed documentation to enable a skilled person to build a substantially equivalent system; it is not simply a rule that every original training file must be publicly downloadable.
OSI also distinguishes open weights from the fuller access described by its AI definition. This is a standard from a particular organization, so a careful article should say when it is applying that standard. The useful question is not whether an announcement uses an attractive label. It is whether the actual release gives the intended user the access and permissions that label suggests.
Try a practical audit. Open the license and identify whether commercial use, redistribution, and modification are permitted, and whether any conditions apply. Then inspect the repository: does it contain only code for running the model, or also training code, processing steps, and configuration? Follow links to the model card and data documentation. A polished launch page cannot answer these questions on its own.
Consider a small business planning to run a model on its own server. It needs permission for that use, compatible software, sufficient hardware, and a way to maintain the deployment. A researcher trying to examine how training choices changed the result needs a different set of materials. This hypothetical example shows why the same release can be adequate for one task and inadequate for another. The label alone does not resolve either case.
Keep a short record of the license version, the files inspected, and the permissions you actually verified. Check each component rather than assuming that the repository's code license also covers weights or training data. Access does not establish accuracy, security, privacy, or suitability for a particular application. An informed assessment describes what is available, how it may be used, and what remains missing.
Go to the sources
Our editorial standards explain how sources and automated briefings are handled.