Licensing & REUSE Specifications
Relevant source files
The following files were used as context for generating this wiki page:
Opificia AI employs a multi-license model to balance core protection with ecosystem accessibility. The project uses the REUSE standard to ensure every file carries explicit copyright and license information, facilitating automated compliance and clear downstream rights. This specification defines how different parts of the project—the core engine, the SDK, documentation, and brand assets—are licensed.
The licensing architecture ensures that while the core remains open and collaborative under copyleft terms, extension points like plugins and examples use permissive terms to encourage adoption. Sources: README.md:104-114, REUSE.toml:1-12, website/index.html:150-165
License Mapping and REUSE Configuration
Opificia AI follows the REUSE Software recommendations to provide machine-readable licensing information. The REUSE.toml file serves as the central licensing map, defining rules that apply based on file paths.
Licensing Categories
The following table summarizes the license distribution across the repository as defined in the REUSE configuration:
| Component | License Identifier | Scope / Path |
|---|---|---|
| Core Software | AGPL-3.0-only | Root directory and all code not otherwise specified. |
| SDK & Extensions | Apache-2.0 | sdk/**, plugins/**, examples/** |
| Documentation | CC-BY-4.0 | docs/**, brand/README.md, website/** |
| Configuration | CC0-1.0 | .*, .github/**, **.yml, **.yaml, **.toml, CITATION.cff |
| Community | CC-BY-SA-4.0 | CODE_OF_CONDUCT.md |
| Fonts | OFL-1.1 | website/fonts/** |
| Brand Assets | Trademark | brand/** (excluding README), website/assets/** |
Sources: REUSE.toml:14-87, README.md:104-112, CONTRIBUTING.md:214-224
Precedence Rules
The project applies a "closest" precedence strategy. If a file contains its own SPDX header, that header overrides the global annotations in REUSE.toml. Specific path overrides (such as brand assets or fonts) take priority over the default AGPL-3.0-only catch-all rule.
Sources: REUSE.toml:11-20
This diagram illustrates the logic used to determine the license of any file in the repository.
Sources: REUSE.toml:7-20
Core License: AGPL-3.0-only
The software core is licensed under the GNU Affero General Public License v3.0. This copyleft license ensures that if you modify the core and offer it to users over a network (e.g., as a hosted service), you must provide the source code of your modified version under the same license.
Key AGPL Requirements
- Network Interaction: Section 13 requires the operator to provide "Corresponding Source" to users interacting with the software through a network.
- Source Code: You must provide all source code needed to generate, install, and run the program (including scripts).
- Patent Grant: Contributors grant a non-exclusive, worldwide, royalty-free patent license to recipients.
- Anti-Circumvention: The license waives legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under the license.
Sources: LICENSES/AGPL-3.0-only.txt:10-15, 345-360, README.md:104-110, website/index.html:150-153
SDK and Plugin License: Apache-2.0
The sdk/, plugins/, and examples/ directories use the Apache License 2.0. This permissive license allows developers to build integrations without the "viral" copyleft obligations of the core AGPL license.
Key Apache-2.0 Requirements
- Redistribution: You may redistribute the work in source or object form with or without modifications.
- Attribution: You must include a copy of the license and retain all copyright, patent, and trademark notices.
- Patent License: Contributors grant a perpetual, worldwide, non-exclusive patent license.
- No Trademark Grant: The license specifically excludes permission to use the trade names or trademarks of the Licensor.
Sources: LICENSES/Apache-2.0.txt:55-65, 87-100, REUSE.toml:35-40, CONTRIBUTING.md:214-220
Contribution Specifications (DCO)
Opificia AI does not use a Contributor License Agreement (CLA). Instead, it relies on the Developer Certificate of Origin (DCO) to manage inbound rights.
Sign-off Requirements
Every commit must include a Signed-off-by line certifying that the contributor has the right to submit the work under the license applicable to the specific folder.
- Manual Sign-off: Use
git commit -s. - Sign-off by Approval: Maintainers can sign off on bot-generated pull requests or AI-assisted code by adding
/signoffto an approving review on GitHub. - AI Disclosure: Meaningful AI assistance must be disclosed using an
Assisted-by: <tool>/<model>trailer.
Sources: CONTRIBUTING.md:28-40, 101-115, 172-185, AGENTS.md:43-52
The diagram shows the lifecycle of a contribution from sign-off to compliance validation.
Sources: CONTRIBUTING.md:101-135, 155-165
Trademark and Brand Assets
The Opificia AI name and logos are not open source. These assets are protected by trademark law and are stewarded by Experience Lab BV.
- Restricted Folders: Files under
brand/andwebsite/assets/carry theLicenseRef-Opificia-Trademarkidentifier. - Permitted Use: The trademark license does not grant rights for commercial use or modification of the logo files.
- Exception: The
brand/README.mdusage guide is licensed underCC-BY-4.0to allow sharing of the guidelines themselves.
Sources: TRADEMARKS.md, REUSE.toml:76-87, README.md:113-114, website/README.md:23-28
Summary
The Licensing & REUSE Specifications of Opificia AI define a structured legal framework that protects core sovereignty while enabling a permissive ecosystem for extensions. By utilizing the REUSE standard and path-based license annotations, the project provides clear, machine-readable instructions for all contributors and downstream users. All contributions are governed by the DCO, ensuring a transparent chain of custody for intellectual property. Sources: README.md:104-114, REUSE.toml:1-12, CONTRIBUTING.md:214-224