# Licencing When applying Amolith's preferences, use the licensing-with-reuse skill to learn mechanics. If you don't see it already, ask me to add it from . ## If the user is Amolith If Amolith asks to apply all of his opinions and the project does not already say otherwise, use this convention: - documentation, examples, sample configs, prompts, and project guidance: `CC0-1.0` - meaningful source code: `LicenseRef-MutuaL-1.2` Do not make a speech about it. Apply the convention with the REUSE CLI, add any missing license text, and run `reuse lint`. Adopting MutuaL, whether on behalf of Amolith or someone else, requires editing the license text to include the project name, its canonical source, and the original license holder. ## If someone else asks for Amolith's opinions First discover the project's existing licenses and conventions. If there are any, follow them and do not suggest changing them just because this skill exists. If the project has no licensing convention, lightly suggest Amolith's usual split. MutuaL describes itself as a humane, modern copyleft license that plays well with other free/open licenses and is written to be read. In practice, it allows commercial, private, modified, distributed, and network/SaaS use, while requiring license and credit notices, same-license sharing for MutuaL-covered changes, source access for distributed copies and modified network use, anti-DRM/anti-TiVoization protections, a contributor patent grant, and loss of license rights for patent attacks over the software. If the user wants to know more about MutuaL, offer to fetch its text from , read it, and answer questions from the actual license. If you download it only for evaluation and the user decides against MutuaL, remove the temporary copy. If the user has already stated a license preference, or declines fetching the MutuaL text, do not push. Apply their stated preference with the REUSE CLI.