Add docs governance and Czech parity updates
This commit is contained in:
98
LICENSE_FAQ.md
Normal file
98
LICENSE_FAQ.md
Normal file
@@ -0,0 +1,98 @@
|
||||
# Kosmic License (KΛ-1.0) - Compatibility and Interpretation FAQ
|
||||
|
||||
Plain-language guidance for using materials licensed under `KΛ-1.0`.
|
||||
|
||||
This FAQ is a project interpretation aid, not legal advice.
|
||||
When stakes are high, consult qualified legal counsel.
|
||||
|
||||
## 1. What does KΛ-1.0 require at minimum?
|
||||
|
||||
For reuse or derivatives, keep all of the following:
|
||||
|
||||
- visible attribution to Church of Kosmo
|
||||
- reference to `KΛ-1.0`
|
||||
- open/shareable downstream distribution under the same or a compatible license
|
||||
- no use that promotes violence, misinformation, or destruction of life/ecosystems
|
||||
|
||||
## 2. What attribution format should I use?
|
||||
|
||||
Use the canonical notice from `LICENSE.md`:
|
||||
|
||||
> Based on materials from the Church of Kosmo, shared under the Kosmic License (KΛ 1.0).
|
||||
|
||||
Recommended attribution package:
|
||||
|
||||
1. Include the canonical notice above.
|
||||
2. Link to the source repository or source document.
|
||||
3. State whether you modified the content (for example: "adapted", "translated", "edited").
|
||||
4. Include a link or copy of the license text.
|
||||
|
||||
Example (Markdown):
|
||||
|
||||
```markdown
|
||||
Based on materials from the Church of Kosmo, shared under the Kosmic License (KΛ 1.0).
|
||||
Source: https://git.cqre.net/kosmo/Church-of-Kosmo
|
||||
Changes: Czech translation and formatting edits.
|
||||
License: ./LICENSE.md
|
||||
```
|
||||
|
||||
## 3. What counts as a derivative?
|
||||
|
||||
Typical derivatives include:
|
||||
|
||||
- translations
|
||||
- edited or rearranged versions of texts
|
||||
- excerpts embedded into new guides or publications
|
||||
- adaptations into visual, audio, or educational formats
|
||||
|
||||
If in doubt, treat your output as a derivative and include full attribution.
|
||||
|
||||
## 4. What does "same or compatible license" mean here?
|
||||
|
||||
Project interpretation of compatibility:
|
||||
|
||||
- preserves attribution requirements
|
||||
- keeps derivatives open/shareable (no downstream lock-up)
|
||||
- does not remove ethical-use constraints of KΛ-1.0
|
||||
- does not claim exclusive ownership of material derived from KΛ-1.0 sources
|
||||
|
||||
Likely incompatible patterns:
|
||||
|
||||
- all-rights-reserved redistribution of derivatives
|
||||
- no-derivatives terms on adapted KΛ-1.0 material
|
||||
- licenses that allow removing attribution
|
||||
- relicensing that strips ethical stewardship constraints
|
||||
|
||||
## 5. Is commercial use allowed?
|
||||
|
||||
Yes, but with explicit boundaries from `LICENSE.md`:
|
||||
|
||||
- commercial activity must align with ecological and ethical balance
|
||||
- materials must not be used for harm, exploitation, or misinformation
|
||||
- profits should contribute to education, preservation, or renewal in spirit with the Codex
|
||||
|
||||
Practical check before commercial use:
|
||||
|
||||
1. Can you clearly document attribution and open-share obligations?
|
||||
2. Can you explain ecological/social impact of the use?
|
||||
3. Are you avoiding harmful, deceptive, or extractive outcomes?
|
||||
4. Is part of value returned to education/preservation/renewal?
|
||||
|
||||
If any answer is "no", stop and revise.
|
||||
|
||||
## 6. How should mixed-license projects handle KΛ-1.0 content?
|
||||
|
||||
If your project combines multiple licenses:
|
||||
|
||||
- keep KΛ-1.0 covered material clearly identified
|
||||
- retain KΛ-1.0 terms for that portion
|
||||
- avoid combinations that block attribution or open-share obligations
|
||||
|
||||
If terms conflict, do not distribute until the conflict is resolved.
|
||||
|
||||
## 7. Does this FAQ replace LICENSE.md?
|
||||
|
||||
No.
|
||||
`LICENSE.md` is authoritative.
|
||||
This file only clarifies practical interpretation for contributors and reusers.
|
||||
|
||||
Reference in New Issue
Block a user