Contributor Licence Agreement (CLA)

The project uses the Harmony Agreements contributor licence framework (https://harmonyagreements.org) to keep the option of future dual-licensing open without needing to re-obtain rights from every past contributor.

Why a CLA

The project is licensed AGPL-3.0-or-later (decision 12). If in future the project's governance body (decision 14, pending) decides to offer a commercial-friendly dual licence to fund external ISO 14071 critical reviews or expanded seed-EPD ingestion, that path requires the copyright holder to have the right to relicense. Without a CLA, that right does not exist and cannot be recovered.

Which Harmony variant

• HA-CLA-I-LIST (Individual, with licence choice list) for individual contributors.
• HA-CLA-E-LIST (Entity, with licence choice list) for organisational contributors.
• Options selected: inbound = AGPL-3.0-or-later; outbound = AGPL-3.0-or-later plus any OSI-approved licence at the maintainer's discretion. This preserves both community and commercial-relicensing paths.

Status

TODO — Phase 0. The instantiated CLA text (generated via https://harmonyagreements.org/agreements.html with the options above) is to be committed to docs/contributing/cla-text.md before any external contributor commits. A CLA-assistant bot integration (e.g. https://cla-assistant.io) is to be wired into the CI in the same phase.

Until this is complete, external contributions are not accepted. Founders' commits pre-CLA are treated as inbound = AGPL-3.0-or-later under the repository licence.