The rights status of a generated artefact must be stated
Aliases: output rights · generated-work copyright · licence of synthesis
What it is
A download button sits under the image; nothing says who may use it, whether it may be altered, whether it may be relicensed. Users read “download” by personal-computing convention as “this is mine.” Rights-status disclosure requires that before someone takes the artefact away, the interface states what rights currently sit on it — the user’s, the platform’s, none because no copyright exists, or undetermined — rather than letting the download act stand in for a legal conclusion.
Whether commercial use needs an extra warning is a later split by consequence. The first problem is being taken as already licensed.
Why it happens
Download, export, save-to-camera-roll have long meant “obtain a disposable copy” in personal computing. Copyright status is a different institution and does not ride along with the file. Generated artefacts also sit where most jurisdictions are still unsettled: some refuse copyright in purely generated works, some vest it in the operator, some in the service. If the interface does not write that uncertainty as a visible state, users fill with download convention, and download convention fills with “I own this.”
Silence is not neutral. Silence is read as implied permission.
Studying it
After generation, offer download. One condition: no rights statement. Another: status shown before download (no copyright / user owns / platform reserves / undetermined). Ask: do you believe you may sell, alter, relicense. Independent variables: presence of a statement, how specific the wording is. Dependent variables: ownership belief, whether planned use exceeds the statement, whether people still read the terms.
A click on “I agree to the terms” is not understanding. Measure rights belief at the moment of download.
Where it stops holding
If the artefact stays in the session and is never taken as a file, the rights question is deferred — but as soon as it is copyable, the statement still has to appear before copy. Inside a firm whose contract already allocates rights, the interface should still point at that contract in one sentence, not assume everyone has read it. An open model running on the user’s own machine makes the product not a party to the rights; say “this interface neither grants nor withdraws rights.” Whether a style resembles a living artist is a different boundary, not solved inside this one status sentence.
Applying it
- Before the first take-away action (download, copy, share), show rights status in a short sentence: who may use, whether alteration is allowed, whether relicensing is allowed, whether status is undetermined.
- If undetermined, write undetermined. Do not use phrases such as “for you to use” that sound like a grant.
- When status varies by plan or region, the statement must follow the current account, not a frozen help-centre page.
- Check: before download, ask “may you sell this image.” The share of answers that disagree with the actual status is the share of decisions the statement never entered.