Licensing overview
Aeonite uses permissive, artifact-appropriate licensing so specifications and test suites can be implemented without permission, registration, or commercial agreement.
Artifact-specific licensing
- Specifications are published under permissive documentation licenses such as CC-BY or CC0.
- Test suites are published under permissive software licenses such as MIT or Apache-2.0.
- Documentation is published under permissive documentation licenses.
No approval layer
No Aeonite artifact requires:
- permission,
- registration,
- commercial agreement.
License properties
- irrevocable,
- implementation-friendly,
- vendor-neutral.
Why this posture exists
The license posture keeps the specification neutral, durable, and easy to adopt. Correctness is established by published artifacts and test execution, not by permission.
Use of Aeonite specifications and test suites does not create partnership, support, or contractual obligations between Aeonite and implementers.
Practical effect
No permission, registration, or agreement is required to implement Aeonite specifications.