Licensing
A preference a reasonable engineer might hold the other way, so it is a switch, not a rule. Set stances.licensing in
config.json, or override one session with HARNESS_STANCE_LICENSING.
Licensing stance: off
No standing licensing policy is in force. Still read the licence of anything you incorporate, record it where the project keeps such records, and say so when it is unclear.
An off variant still links a one-line file, so /context shows the stance is set and silent rather than missing.
Licensing stance: open-source project
Invoke the licensing-review skill before incorporating or upgrading any third-party material —
code, models, fonts, audio, images and datasets alike. It must permit use, modification and
redistribution under a licence compatible with the project’s own; copyleft qualifies only when that
holds and the obligations are recorded in the manifest. Noncommercial, no-derivatives, field-of-use,
time-limited, revocable and paid proprietary licences are excluded, as is anything with suspect
rights. A marketplace tag is not proof, and no licence clears trademark risk. docs/preferences.md.
Licensing stance: permissive, commercial-safe
Invoke the licensing-review skill before incorporating or upgrading any third-party material —
code, models, fonts, audio, images and datasets alike. Use only material permitting commercial use,
modification and redistribution in a closed-source paid product with no fee, royalty or future
payment; copyleft, share-alike, noncommercial, no-derivatives, field-of-use, time-limited and
revocable licences are excluded without exception. A marketplace tag is not proof, unresolved
material stays out, and no licence clears trademark risk. Lists: docs/preferences.md.
Other dimensions: autonomy · build-vs-buy · commits · cost · delegation · plan-ceremony · testing · voice