Accepted
2026-07-19
ADR 0001 established Agentic Praxis Grimoire’s public-projection boundary but deferred the distribution license, contribution policy, and public repository creation. The project is preparing its first public mirror. It has not made a prior public license grant, has no prior-license baseline to preserve, and has not accepted outside contributions.
The project steward wants a recognized open-source community license that requires source availability for modified network-service deployments while retaining the ability to offer proprietary commercial terms. Future outside contributions must preserve the steward’s ability to sublicense and relicense accepted contributions as part of the Project.
AGPL-3.0-or-later).LICENSE. The or later election
is stated in the repository’s licensing notices.CLA.md. Contributors retain copyright
while granting the Project Steward and authorized successors the copyright
and patent rights needed to distribute accepted contributions under the
AGPL, commercial licenses, and future Project licenses.Pull requests must affirmatively include this exact acknowledgment, either by marking its checkbox or stating it directly:
I agree to the Agentic Praxis Grimoire contribution terms in CLA.md.
A Signed-off-by line does not replace the acknowledgment.
The aligned governance surface consists of LICENSE, README.md,
COMMERCIAL-LICENSE.md, CONTRIBUTING.md, CLA.md, NOTICE, and
.github/pull_request_template.md. The repository currently has no package
metadata license field or source-file header convention to update.
Rejected for the initial public grant. A permissive license would allow proprietary network-service forks without a corresponding source-availability obligation and would weaken the intended commercial-licensing model.
Rejected in favor of the AGPL because the GPL does not add the AGPL’s specific source-availability condition for modified versions used over a network.
Rejected. AGPL-only distribution would not provide negotiated proprietary terms, and accepting contributions without adequate grants could prevent the Project Steward from licensing the combined Project commercially.
Rejected. A custom restriction would reduce open-source clarity and ecosystem compatibility without a demonstrated need that outweighs a standard license.