Licenses Ekklesia under the GNU Affero General Public License, version 3 or (at your option) any later version (AGPL-3.0-or-later). Module Package v1 (#66) bundles Ekklesia's SDK and contracts into distributable module packages, so the platform needs an explicit license first.
No runtime, ADR, package-format, Signage, or instance change; nothing is published or tagged.
Changes
LICENSE: the AGPL v3 text, verbatim from https://www.gnu.org/licenses/agpl-3.0.txt (SHA-256 0d96a4ff68ad6d4b6f1f30f713b18d5184912ba8dd389f86aa7710db079abcb0, 661 lines).
"license": "AGPL-3.0-or-later" in the root package.json and every Ekklesia workspace package. One added line per manifest and nothing else changed:
Visibility and publishing flags are unchanged. The vendored Apache-2.0 notice material in packages/module-pack/licenses/ is third-party and untouched.
README: a License section replacing the placeholder ("No open-source license has been selected yet…"). It states:
AGPL v3 or any later version, with SPDX id and link;
the FSF's standard grant ("either version 3 of the License, or (at your option) any later version"), with its warranty disclaimer;
that source is available under its terms;
section 13's network-use source obligation for modified versions;
that official Ekklesia modules use AGPL-3.0-or-later.
Module template README and module development guide: the template declares the license, so modules started from it begin with it. They also state, factually, that Module Package v1 doesn't yet record a module's own license.
Why AGPL-3.0-or-later
The project decision, revised in review, is AGPL version 3 or any later version. LICENSE stays the canonical AGPLv3 text; the grant to later versions is stated where the project's licensing terms are established: the README's notice and every manifest's SPDX identifier.
Module Package v1: no change, and why
Bundled Ekklesia code is represented. The SDK, contracts, and UI packages appear in ekklesia.package.json under incorporates. THIRD_PARTY_NOTICES stays third-party only.
The package carries no license declaration of its own, by contract. ADR 0049 fixes the runtime package.json fields, makes ekklesia.package.json strict, and says the package "contains nothing else". Adding a license field, or a LICENSE file with the AGPL text for the bundled Ekklesia code, would change that accepted contract. This PR therefore leaves it alone, as instructed, and the packaged template is byte-identical before and after this PR (9a2fc626…, same recorded revision).
Recommended follow-up: an ADR amendment that adds the module's license to the package metadata and ships the license text with each package. That should land before SDK-bundling packages are distributed.
Verification
pnpm verify: passed (contracts 232, core 1059, api 510, module-pack 39; boundaries, module and migration validation, identity schema, build).
Template package byte-identical on main and on this branch.
All 133 links in the changed docs resolve.
Final tree search: every license declaration is AGPL-3.0-or-later, and no AGPL-3.0-only remains anywhere. The vendored third-party Apache text is the only other license. No stale or conflicting declarations.
Licenses Ekklesia under the **GNU Affero General Public License, version 3 or (at your option) any later version** (`AGPL-3.0-or-later`). Module Package v1 (#66) bundles Ekklesia's SDK and contracts into distributable module packages, so the platform needs an explicit license first.
No runtime, ADR, package-format, Signage, or instance change; nothing is published or tagged.
## Changes
- **`LICENSE`:** the AGPL v3 text, verbatim from https://www.gnu.org/licenses/agpl-3.0.txt (SHA-256 `0d96a4ff68ad6d4b6f1f30f713b18d5184912ba8dd389f86aa7710db079abcb0`, 661 lines).
- **`"license": "AGPL-3.0-or-later"`** in the root `package.json` and every Ekklesia workspace package. One added line per manifest and nothing else changed:
- `@ekklesia/api`, `@ekklesia/core`, `@ekklesia/shell`;
- `@ekklesia/contracts`, `@ekklesia/design-tokens`, `@ekklesia/module-pack`, `@ekklesia/module-sdk`, `@ekklesia/module-ui-build`, `@ekklesia/module-ui-host`, `@ekklesia/module-ui-sdk`, `@ekklesia/typescript-config`, `@ekklesia/ui`;
- `@ekklesia/module-template`.
Visibility and publishing flags are unchanged. The vendored Apache-2.0 notice material in `packages/module-pack/licenses/` is third-party and untouched.
- **README:** a License section replacing the placeholder ("No open-source license has been selected yet…"). It states:
- AGPL v3 or any later version, with SPDX id and link;
- the FSF's standard grant ("either version 3 of the License, or (at your option) any later version"), with its warranty disclaimer;
- that source is available under its terms;
- section 13's network-use source obligation for modified versions;
- that official Ekklesia modules use `AGPL-3.0-or-later`.
- **Module template README and module development guide:** the template declares the license, so modules started from it begin with it. They also state, factually, that Module Package v1 doesn't yet record a module's own license.
## Why `AGPL-3.0-or-later`
The project decision, revised in review, is AGPL version 3 or any later version. `LICENSE` stays the canonical AGPLv3 text; the grant to later versions is stated where the project's licensing terms are established: the README's notice and every manifest's SPDX identifier.
## Module Package v1: no change, and why
- **Bundled Ekklesia code is represented.** The SDK, contracts, and UI packages appear in `ekklesia.package.json` under `incorporates`. `THIRD_PARTY_NOTICES` stays third-party only.
- **The package carries no license declaration of its own, by contract.** ADR 0049 fixes the runtime `package.json` fields, makes `ekklesia.package.json` strict, and says the package "contains nothing else". Adding a `license` field, or a LICENSE file with the AGPL text for the bundled Ekklesia code, would change that accepted contract. This PR therefore leaves it alone, as instructed, and the packaged template is **byte-identical** before and after this PR (`9a2fc626…`, same recorded revision).
- **Recommended follow-up:** an ADR amendment that adds the module's license to the package metadata and ships the license text with each package. That should land before SDK-bundling packages are distributed.
## Verification
- `pnpm verify`: passed (contracts 232, core 1059, api 510, module-pack 39; boundaries, module and migration validation, identity schema, build).
- Template package byte-identical on `main` and on this branch.
- All 133 links in the changed docs resolve.
- Final tree search: every license declaration is `AGPL-3.0-or-later`, and no `AGPL-3.0-only` remains anywhere. The vendored third-party Apache text is the only other license. No stale or conflicting declarations.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Ekklesia is open source under the GNU Affero General Public License, version 3
only. Module Package v1 (#66) bundles Ekklesia's SDK and contracts into
distributable module packages, so the platform needs an explicit license
before such artifacts are distributed.
- LICENSE: the GNU AGPL v3 text, verbatim from
https://www.gnu.org/licenses/agpl-3.0.txt
(sha256 0d96a4ff68ad6d4b6f1f30f713b18d5184912ba8dd389f86aa7710db079abcb0).
- "license": "AGPL-3.0-only" in the root package.json and every Ekklesia
workspace package (13 packages), the module template included. Nothing else in
any manifest changed.
- README: a License section replacing the "no license selected yet" placeholder:
AGPL v3 only, source available under its terms, section 13's network-use
obligation, and the policy that official Ekklesia modules use AGPL-3.0-only.
- Module template README and module development guide: the template declares
the license; Module Package v1 does not yet record a module's own license,
which needs a format change under ADR 0049.
AGPL-3.0-only, not -or-later: the decision is AGPL-3.0, and nothing in the
repository grants later versions. No runtime, ADR, package-format, Signage, or
instance change. The packaged template is byte-identical before and after.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The project decision is the GNU Affero General Public License, version 3 or
(at your option) any later version.
- "license": "AGPL-3.0-or-later" in all 14 Ekklesia-owned package.json files.
- README: the License section states AGPL v3 or any later version (SPDX
AGPL-3.0-or-later) and carries the FSF's standard grant: "either version 3 of
the License, or (at your option) any later version", with its warranty
disclaimer and pointer to the license.
- Module template README and module development guide: AGPL-3.0-or-later for
Ekklesia and official modules.
LICENSE is unchanged: it remains the canonical AGPLv3 text.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
ekklesia-bot
changed title from chore: license Ekklesia under AGPL-3.0-only to chore: license Ekklesia under AGPL-3.0-or-later2026-10-07 18:54:09 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Licenses Ekklesia under the GNU Affero General Public License, version 3 or (at your option) any later version (
AGPL-3.0-or-later). Module Package v1 (#66) bundles Ekklesia's SDK and contracts into distributable module packages, so the platform needs an explicit license first.No runtime, ADR, package-format, Signage, or instance change; nothing is published or tagged.
Changes
LICENSE: the AGPL v3 text, verbatim from https://www.gnu.org/licenses/agpl-3.0.txt (SHA-2560d96a4ff68ad6d4b6f1f30f713b18d5184912ba8dd389f86aa7710db079abcb0, 661 lines)."license": "AGPL-3.0-or-later"in the rootpackage.jsonand every Ekklesia workspace package. One added line per manifest and nothing else changed:@ekklesia/api,@ekklesia/core,@ekklesia/shell;@ekklesia/contracts,@ekklesia/design-tokens,@ekklesia/module-pack,@ekklesia/module-sdk,@ekklesia/module-ui-build,@ekklesia/module-ui-host,@ekklesia/module-ui-sdk,@ekklesia/typescript-config,@ekklesia/ui;@ekklesia/module-template.Visibility and publishing flags are unchanged. The vendored Apache-2.0 notice material in
packages/module-pack/licenses/is third-party and untouched.README: a License section replacing the placeholder ("No open-source license has been selected yet…"). It states:
AGPL-3.0-or-later.Module template README and module development guide: the template declares the license, so modules started from it begin with it. They also state, factually, that Module Package v1 doesn't yet record a module's own license.
Why
AGPL-3.0-or-laterThe project decision, revised in review, is AGPL version 3 or any later version.
LICENSEstays the canonical AGPLv3 text; the grant to later versions is stated where the project's licensing terms are established: the README's notice and every manifest's SPDX identifier.Module Package v1: no change, and why
ekklesia.package.jsonunderincorporates.THIRD_PARTY_NOTICESstays third-party only.package.jsonfields, makesekklesia.package.jsonstrict, and says the package "contains nothing else". Adding alicensefield, or a LICENSE file with the AGPL text for the bundled Ekklesia code, would change that accepted contract. This PR therefore leaves it alone, as instructed, and the packaged template is byte-identical before and after this PR (9a2fc626…, same recorded revision).Verification
pnpm verify: passed (contracts 232, core 1059, api 510, module-pack 39; boundaries, module and migration validation, identity schema, build).mainand on this branch.AGPL-3.0-or-later, and noAGPL-3.0-onlyremains anywhere. The vendored third-party Apache text is the only other license. No stale or conflicting declarations.🤖 Generated with Claude Code
chore: license Ekklesia under AGPL-3.0-onlyto chore: license Ekklesia under AGPL-3.0-or-later