Skip to content

Lesson 12 · ai

Code, weights and generated output

Open weights and unrestricted rights are different claims.

A model release can contain code, weights, documentation and datasets under different grants. Treat them as separate artifacts. Availability to download does not establish approval under an open-source definition or permission for every use.

Use a version-specific license. Llama 3.1 includes attribution and acceptable-use conditions and additional commercial terms tied to licensee scale at release. CreativeML OpenRAIL-M has its own use restrictions. A research-only weight grant does not become commercial merely because an inference wrapper is MIT.

Training-data provenance and the legal status of a generated output cannot be inferred from the weights' license alone. A coding agent's assertion that it generated a snippet also does not prove there is no upstream copyrighted expression.

The model exercise supplies the use review and scale facts so the remaining attribution obligation is checkable. The provenance drill uses a known upstream source and a supplied grant; it does not attempt probabilistic plagiarism detection.

Try it: Code and weights have different grants

The MIT application distributes Llama 3.1 weights. The supplied use is acceptable and the licensee had 10,000 monthly active users at release. Complete the model attribution surface.

Before inspecting the result

What does this supplied release need before its modeled requirements are met?

Prediction

Project boundary

2 components
bundleappLicenseRef-ProprietarylibraryLicenseRef-Llama-3.1
Dependency relationships
From → toConnectionSemantics
app → librarybundleintimate

Supplied facts

Distribution
binary
Network interaction
No
Intended use
internal
Evaluation date
2026-10-24
Policy
learning

These facts define the simulation. Evidence declarations stand in for actual corresponding source, relinkable objects and release materials.

Components

Declared license
LicenseRef-Proprietary
Modified files
None
Artifact
code

Third-party grants remain fixed unless this scenario supplies authority to change them.

Project artifacts

Evidence artifact format

Source offers contain “component: id” and “source: https://…” on separate lines. Covered-file offers also list the covered paths. Relinking declarations contain “replace-compatible-library” for dynamic linking or “relink-object-files” for static linking, and “reverse-engineering-permitted”. These declarations model supplied release artifacts.

License reference

permissions
commercial-use, modifications, distribution, private-use
conditions
include-copyright, include-license
limitations
liability, warranty
Read authoritative terms ↗

Expression builder

Each row is one selectable alternative. AND retains every term in a row.
AlternativeRequired licenses
1MIT AND LGPL-3.0-only
2Apache-2.0 AND LGPL-3.0-only
Results appear after submission.