Open weights, and who inherits the questions
Open weights means the model files themselves are available to download and run. The operator becomes whoever downloaded them, and no default, parameter or policy set later by the original team applies. As of 2026-09-12.
| What changes when weights are published | Consequence |
|---|---|
| Anybody can run the model | The operator may be unidentifiable |
| No interface sits in the middle | No default and no parameter to document |
| The terms travel with the files | The only document that could ask for anything |
| The hosted route still exists | Two populations, one model, different behaviour |
Inclusion rule. Consequences of publishing model weights for download, as repository pages and terms describe the arrangement. Order. From the defining change to the practical consequence.
1A hosted interface is where decisions can be implemented
One endpoint, one default, one change that moves everybody's output at once. Whatever anybody wants a model to do to its output, a hosted interface is somewhere it can be done and verified.
Downloaded weights have none of that. They run on other hardware, under code the publisher never sees, and the only thing that travelled with them was a licence.
2Permissive terms ask for as little as possible
Adoption is the point of publishing weights that way, and requirements are friction. So reading such a licence for an obligation about output and finding none is an expected result.
Recording it matters anyway. It is the only document in the chain that could have carried such a requirement, and its silence is a decision rather than an oversight.
3The same model name covers two different things
Statements about a hosted interface describe callers of that interface. They say nothing about output from the same weights running elsewhere, and conflating the two produces confident, wrong sentences.
A register has to keep them apart even when the product name is identical. Which route produced a file is frequently the fact nobody recorded, and it decides the answer.
4Nothing here is an argument against publishing weights
Open weights make work possible that hosted interfaces do not, including work nobody has to ask permission for. The observation is narrower: obligations attached to a builder do not follow the files.
Where they should land instead is a question for whoever writes the instruments. A register can only note that the question exists and that the documents travelling with the files do not answer it.
5Published material behind this entry
A term in this record: what it means, and what the published material says about it, each figure read on 2026-09-12. Related: Test mode, Transcode.