NodeValid

Published video-model weights, licences and hardware notes

Output rights, and why licences skip them

Output rights are about the video, not the weights. Most people open a licence file wanting to know whether they can sell what the model generates, and in this register that question is frequently not addressed there at all. As of 2026-09-22.

Three layers a release can license separatelyCode, weights and generated output are three different things, and a release can treat them differently or leave one of them unmentioned.Usually covered by a standard licenceCodeThe repository files, under a licence anyone can recognise.WeightsOften under terms of their own, beside the code.OutputFrequently not addressed anywhere in the release.Silence is neither yes nor no
Fig. 1 The layer most readers care about is the layer most often unaddressed.
Where an answer about generated output might actually live. Recorded 2026-09-22.
PlaceHow often it answers
The weights licenceSometimes
A separate policy fileSometimes
The model cardRarely, and then as guidance
A hosted service agreementOnly for that service

Inclusion rule. Documents a reader might consult about output. A hosted agreement is listed because it is routinely mistaken for terms that cover local use. Order. From the document shipped with the weights outward.

1Silence is the common case and not a permission

Some releases address output explicitly, some are silent, and silence is neither permission nor refusal. Reading it as either is how a production discovers a problem after publishing.

Where material is to be sold or published, the answer usually depends on more than the licence: the jurisdiction, any agreement signed with a service, and what was fed into the model.

2The three layers get collapsed into one

A reader sees a recognised badge at the top of a repository and treats it as the answer for code, weights and output at once. In this register those three are governed by different text more often than not.

Nothing here is a reading of anyone's obligations. The register keeps the factual layer straight: which version, which file, which date, which page.

3What the licence column does and does not carry

The column holds the name in the licence field. Whether that document addresses generated output is not recorded as a separate value, because it would require the register to read the terms rather than quote the field.

One card in the register answers the commercial question in its own text, which is rare enough to be worth a page of its own. Everywhere else the answer lives in a document a reader has to open.

A reading note, not an entry: no vendor value appears on this page. Where the register records this term for a particular release, it is on the licence column and on that family's own page. Nearby terms: Licence tag, Parameter count.