303e8c6306
All 117 inter-node links now use [[file:node-name.org][title]] format which renders as clickable hyperlinks in both Emacs (C-c C-o) and web-based org renderers (Gitea, GitHub). Each node retains its :ID: UUID property for Emacs org-roam database features (backlinks, capturing, node-find). Prev format: [[id:uuid][title]] — Emacs only, dead text on web New format: [[file:name.org][title]] — works everywhere
22 lines
1.4 KiB
Org Mode
22 lines
1.4 KiB
Org Mode
:PROPERTIES:
|
|
:ID: 67faf52f-9126-50a7-b87e-2bedc610dac7
|
|
:END:
|
|
#+title: Licensing — AGPLv3 + Commercial
|
|
#+filetags: :passepartout:ip:licensing:agpl:commercial:
|
|
|
|
**AGPLv3 for the public repository.** AGPL closes the ASP loophole: anyone who modifies the software and offers it over a network must release their modified source. Protects against proprietary forks.
|
|
|
|
Crucially: AGPL is a *product requirement*, not a concession. The system's value proposition is provable correctness — every decision has Merkle provenance. This claim is structurally incredible with closed source. An enterprise buyer needs to inspect the gate stack, verify the Merkle implementation, and confirm ACL2 integration. AGPL makes this possible without signing an NDA.
|
|
|
|
**AGPL only covers modifications to code, not:**
|
|
- Gate rules specific to a domain (these are data, not code)
|
|
- The fact store (empirical data generated from usage)
|
|
- Ontology categories (design decisions stored as configuration)
|
|
- Proprietary skills loaded at runtime (AGPL boundary on plugin systems is legally unsettled)
|
|
|
|
**Dual license model:**
|
|
- AGPLv3 for open source — builds ecosystem, trust, community
|
|
- Commercial license for enterprises that cannot accept AGPL — MySQL/SugarCRM/GraphQL model
|
|
|
|
See also: [[file:patent-strategy.org][Patent strategy]], [[file:moats.org][Moats]], [[file:pds-as-a-service.org][PDS as a service]]
|