@mindflight/ghostcrab-personal-mcp-win32-arm64 0.4.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/Licence.md +147 -0
- package/bin/ghostcrab-backend.exe +0 -0
- package/bin/ghostcrab-document.exe +0 -0
- package/package.json +19 -0
package/Licence.md
ADDED
|
@@ -0,0 +1,147 @@
|
|
|
1
|
+
# GhostCrab Personal — Licence Position
|
|
2
|
+
|
|
3
|
+
**GhostCrab Personal** is the SQLite-backed MCP memory server and related artefacts in this repository, built on **MindBrain** as its operational substrate.
|
|
4
|
+
|
|
5
|
+
**Trademarks.** The names **GhostCrab**, **MindBrain**, and related branding (including logos where published) are marks of **Web Igniter SRL**, Belgium. This document governs copyright and licence terms for the shipped code and content; it does not grant any right to use Web Igniter’s trade marks except as allowed by applicable law (for example fair nominative use) and by any separate branding or partner agreement.
|
|
6
|
+
|
|
7
|
+
This repository is intended to follow a layered licence model:
|
|
8
|
+
|
|
9
|
+
- source code may be released under Apache License 2.0 where explicitly marked;
|
|
10
|
+
- ontology, schema, model, prompt, and template content is governed separately by the MindBrain Ontology License;
|
|
11
|
+
- commercial operation of MindBrain-backed capabilities for third parties requires a separate MindBrain Operator License.
|
|
12
|
+
|
|
13
|
+
This file is a licence overview, not a substitute for a signed commercial agreement.
|
|
14
|
+
|
|
15
|
+
## 1. Code Layer
|
|
16
|
+
|
|
17
|
+
Unless a file or package states otherwise, the intended licence for open source code in this repository is:
|
|
18
|
+
|
|
19
|
+
**Apache License 2.0**
|
|
20
|
+
|
|
21
|
+
The Apache-2.0 layer is meant to cover implementation code that enables local development, integration, tooling, and personal use of GhostCrab / MindBrain components.
|
|
22
|
+
|
|
23
|
+
It does not automatically grant commercial operator rights over MindBrain as an operational substrate for third parties.
|
|
24
|
+
|
|
25
|
+
## 2. Ontology And Content Layer
|
|
26
|
+
|
|
27
|
+
The following materials are not automatically covered by the Apache-2.0 code grant:
|
|
28
|
+
|
|
29
|
+
- ontologies;
|
|
30
|
+
- schema packs;
|
|
31
|
+
- inference models;
|
|
32
|
+
- prompt packs;
|
|
33
|
+
- recipe libraries;
|
|
34
|
+
- domain templates;
|
|
35
|
+
- curated knowledge structures;
|
|
36
|
+
- sample workspaces that encode reusable business or cognitive models.
|
|
37
|
+
|
|
38
|
+
These materials are governed by the **MindBrain Ontology License** unless a specific file states otherwise.
|
|
39
|
+
|
|
40
|
+
The MindBrain Ontology License is intended to allow legitimate evaluation, development, learning, and internal use while preserving MindBrain's semantic corpus from unauthorized commercial cloning, repackaging, or competing registry use.
|
|
41
|
+
|
|
42
|
+
## 3. Operator Layer
|
|
43
|
+
|
|
44
|
+
MindBrain is more than a peripheral library. It can become the operational substrate of an application: it may encode ontologies, inference rules, agent memory, workflow state, and deterministic agent flows.
|
|
45
|
+
|
|
46
|
+
Because of that, the following uses require a separate **MindBrain Operator License (MOL)** or another written commercial agreement:
|
|
47
|
+
|
|
48
|
+
- offering MindBrain as a managed infrastructure service;
|
|
49
|
+
- embedding MindBrain inside a commercial SaaS product sold to customers;
|
|
50
|
+
- exposing MindBrain-backed capabilities to external users, customers, partners, or tenants through an API;
|
|
51
|
+
- redistributing a MindBrain-backed product through white-label, franchise, reseller, or OEM arrangements;
|
|
52
|
+
- packaging MindBrain as a default backend inside a commercial agent framework, platform, or deployment service;
|
|
53
|
+
- transferring the operational benefit of MindBrain to a legally distinct third party.
|
|
54
|
+
|
|
55
|
+
## 4. Internal And Development Use
|
|
56
|
+
|
|
57
|
+
The licence model is intended to allow low-friction use for:
|
|
58
|
+
|
|
59
|
+
- personal development;
|
|
60
|
+
- local experimentation;
|
|
61
|
+
- open source development;
|
|
62
|
+
- internal company use;
|
|
63
|
+
- integrators deploying MindBrain for a named end customer under the customer's licence or an approved deployment agreement.
|
|
64
|
+
|
|
65
|
+
Internal use can become operator use if the system is later exposed to customers, partners, tenants, or other legally distinct entities.
|
|
66
|
+
|
|
67
|
+
## 5. Definition: Operating MindBrain For Third Parties
|
|
68
|
+
|
|
69
|
+
For the purposes of this licence model, "operating MindBrain for third parties" includes making MindBrain or MindBrain-backed capabilities available to customers, partners, tenants, external users, or legally distinct entities, whether:
|
|
70
|
+
|
|
71
|
+
- directly as managed infrastructure;
|
|
72
|
+
- indirectly as part of a SaaS product;
|
|
73
|
+
- through APIs;
|
|
74
|
+
- through white-label or franchise redistribution;
|
|
75
|
+
- through embedded framework or platform functionality;
|
|
76
|
+
- through any contractual arrangement that transfers the operational benefit of MindBrain to a third party.
|
|
77
|
+
|
|
78
|
+
## 6. NPM And Public Distribution
|
|
79
|
+
|
|
80
|
+
Publishing a package publicly does not imply that every asset in the package is open source.
|
|
81
|
+
|
|
82
|
+
Packages containing only Apache-2.0 code may use:
|
|
83
|
+
|
|
84
|
+
```json
|
|
85
|
+
{
|
|
86
|
+
"license": "Apache-2.0"
|
|
87
|
+
}
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
Packages that include ontology packs, schema packs, templates, proprietary content, or mixed-rights materials should instead use:
|
|
91
|
+
|
|
92
|
+
```json
|
|
93
|
+
{
|
|
94
|
+
"license": "SEE LICENSE IN Licence.md"
|
|
95
|
+
}
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
Published packages should explicitly limit their included files and avoid install-time scripts unless they are necessary and documented.
|
|
99
|
+
|
|
100
|
+
## 7. Commercial Agreements
|
|
101
|
+
|
|
102
|
+
Commercial operator rights are expected to be handled through separate agreements, including:
|
|
103
|
+
|
|
104
|
+
- SaaS / OEM licences;
|
|
105
|
+
- white-label or franchise licences;
|
|
106
|
+
- managed infrastructure agreements;
|
|
107
|
+
- framework partnership agreements;
|
|
108
|
+
- enterprise subscriptions;
|
|
109
|
+
- deployment agreements for integrators.
|
|
110
|
+
|
|
111
|
+
These agreements may include usage scope, attribution, support, telemetry or reporting terms, revenue sharing, per-instance fees, change-of-control clauses, and service-level commitments.
|
|
112
|
+
|
|
113
|
+
## 8. Contributions And Contributor Licence Agreement (CLA)
|
|
114
|
+
|
|
115
|
+
The mechanism you are describing is not an “extension” of the SPDX licence text itself: it is a **Contributor Licence Agreement (CLA)** — a separate agreement between each contributor and the project steward (**Web Igniter SRL**, Belgium, or as stated in the signed CLA).
|
|
116
|
+
|
|
117
|
+
### Why a CLA matters for future licence changes
|
|
118
|
+
|
|
119
|
+
Merging a pull request or accepting a contribution without a CLA typically leaves that contribution governed by **the licence that applied when the contribution landed**. Contributors may then dispute or delay a later licence change affecting their copyrightable expression.
|
|
120
|
+
|
|
121
|
+
A CLA addresses this by obtaining, **before merge**, an explicit grant from the contributor that includes:
|
|
122
|
+
|
|
123
|
+
- a **perpetual, irrevocable** licence to use the contribution under the project’s then-current terms;
|
|
124
|
+
- the right for the steward to **sublicense** and **relicense** the contribution, including under **different** open-source licences or **proprietary / commercial** terms, as the steward’s published policy and the CLA allow.
|
|
125
|
+
|
|
126
|
+
That is the **irreversible sublicensing / relicensing** language people associate with CLAs (often modelled on Apache’s ICLA patterns), not a clause inside Apache-2.0 or MIT by itself.
|
|
127
|
+
|
|
128
|
+
### CLA versus DCO (Developer Certificate of Origin)
|
|
129
|
+
|
|
130
|
+
| | **CLA** | **DCO** |
|
|
131
|
+
| :-------------------------- | :------------------------------------ | :------------------------------------------------------------------------------------------------------------------ |
|
|
132
|
+
| Relicensing for the steward | Typically **yes**, if the CLA says so | **No** — contribution stays under the licence in force at submit time (with the usual outbound licence of the repo) |
|
|
133
|
+
| Contributor friction | Higher (explicit agreement) | Lower (`Signed-off-by` in commit message) |
|
|
134
|
+
|
|
135
|
+
Projects that need freedom to evolve from community terms to layered or commercial licences **without contributor vetoes** generally use a **CLA with explicit relicensing language**, not DCO alone.
|
|
136
|
+
|
|
137
|
+
### What this repository expects
|
|
138
|
+
|
|
139
|
+
Until a formal CLA template is published and linked from `CONTRIBUTING.md` (or equivalent), treat this section as **policy intent** only: **merged third-party contributions should be accepted only under a signed CLA** (or another written grant with equivalent sublicensing scope) where required by Web Igniter’s counsel.
|
|
140
|
+
|
|
141
|
+
Illustrative wording often used in CLAs (not legally operative until executed):
|
|
142
|
+
|
|
143
|
+
> You grant Web Igniter SRL a perpetual, worldwide, non-exclusive, royalty-free, irrevocable licence to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works, including under proprietary or commercial licences.
|
|
144
|
+
|
|
145
|
+
## 9. No Legal Advice
|
|
146
|
+
|
|
147
|
+
This document describes the intended licence structure for the project. It should be reviewed and converted into final legal terms by qualified counsel before commercial release or public package publication.
|
|
Binary file
|
|
Binary file
|
package/package.json
ADDED
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@mindflight/ghostcrab-personal-mcp-win32-arm64",
|
|
3
|
+
"version": "0.4.3",
|
|
4
|
+
"description": "Platform binary for @mindflight/ghostcrab-personal-mcp (win32-arm64).",
|
|
5
|
+
"license": "SEE LICENSE IN Licence.md",
|
|
6
|
+
"os": [
|
|
7
|
+
"win32"
|
|
8
|
+
],
|
|
9
|
+
"cpu": [
|
|
10
|
+
"arm64"
|
|
11
|
+
],
|
|
12
|
+
"files": [
|
|
13
|
+
"bin",
|
|
14
|
+
"Licence.md"
|
|
15
|
+
],
|
|
16
|
+
"scripts": {
|
|
17
|
+
"prepack": "node ../../scripts/stage-platform-packages.mjs --platform win32-arm64"
|
|
18
|
+
}
|
|
19
|
+
}
|