home/ atoms/ livecoding-code-provenance-license

Only MIT/BSD/Apache/CC0/CC-BY non-NC code may be emitted verbatim into committed jam files; gray-licensed snippets are local-reference only

Committed jam files are in git, making licensing real exposure. Gray-licensed, AGPL, -NC (non-commercial), or unknown-licensed code snippets may be used as local reference but must never be emitted verbatim into a committed jam file. Only MIT, BSD, Apache-2.0, CC0, CC-BY (non-NC variants), or public-domain material may be inlined. When the license is uncertain, write the idea in your own idiom rather than paste the source.

Examples

A CC-BY-NC sample bank can be studied locally but a snippet from its documentation cannot be committed. An MIT-licensed Tidal example can be inlined.

Assessment

State which license categories may be emitted verbatim into a committed jam file, and describe the correct action when a useful snippet’s license is unknown.

“gray / `AGPL` / any `-NC` / unknown-licensed snippets may be used as **local reference** but are **never emitted verbatim** into a committed jam file.”
context/ · L6-craft/ethos.md · chunk 1