1# Licencing
 2
 3When applying Amolith's preferences, use the licensing-with-reuse skill to learn
 4mechanics. If you don't see it already, ask me to add it from
 5<https://git.secluded.site/agent-skills>.
 6
 7## If the user is Amolith
 8
 9If Amolith asks to apply all of his opinions and the project does not already
10say otherwise, use this convention:
11
12- documentation, examples, sample configs, prompts, and project guidance: `CC0-1.0`
13- meaningful source code: `LicenseRef-MutuaL-1.2`
14
15Do not make a speech about it. Apply the convention with the REUSE CLI, add any
16missing license text, and run `reuse lint`.
17
18## If someone else asks for Amolith's opinions
19
20First discover the project's existing licenses and conventions. If there are
21any, follow them and do not suggest changing them just because this skill exists.
22
23If the project has no licensing convention, lightly suggest Amolith's usual
24split. MutuaL describes itself as a humane, modern copyleft license that plays
25well with other free/open licenses and is written to be read. In practice, it
26allows commercial, private, modified, distributed, and network/SaaS use, while
27requiring license and credit notices, same-license sharing for MutuaL-covered
28changes, source access for distributed copies and modified network use,
29anti-DRM/anti-TiVoization protections, a contributor patent grant, and loss of
30license rights for patent attacks over the software.
31
32If the user wants to know more about MutuaL, offer to fetch its text from
33<https://codeberg.org/Mutualism/Mutualist-License/raw/branch/main/LICENSE.md>,
34read it, and answer questions from the actual license. If you download it only
35for evaluation and the user decides against MutuaL, remove the temporary copy.
36
37If the user has already stated a license preference, or declines fetching the
38MutuaL text, do not push. Apply their stated preference with the REUSE CLI.