From d8e853006317ca7fdb58c92fdde26e99c5c701b9 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Wed, 26 Aug 2026 18:44:07 +0100 Subject: [PATCH] =?UTF-8?q?policy:=20Rule=202=20becomes=20a=20growing=20re?= =?UTF-8?q?gister=20=E2=80=94=20five=20repos,=20cap=20lifted?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Owner ruling 2026-08-26. The 'exactly three repositories and nowhere else' cap is lifted: as the Palimpsest family develops, more repos will move onto it over time. Adds insolvency-tycoon and sim-public-relations, bringing the register to five. Both were already on PMPL in practice, so under the old wording they read as DRIFT and a future audit would have 'corrected' them -- exactly the trap Rule 5 was written to avoid for games. IMPORTANT SHAPE: this is a growing ALLOWLIST, not an open door. The 'exactly three' cap was not arbitrary strictness -- it is what made stray PMPL detectable as drift. Remove the boundary entirely and any PMPL string anywhere looks legitimate, which is how 471 files of residue accumulated unnoticed in this repo. So the register still binds: a PMPL declaration in an unlisted repo is drift, and adding a name is an owner decision and a one-line change. Also records a legal constraint on the wider P-family before effort goes into it, because it is NOT symmetric: * MPL-2.0 S10.3 EXPRESSLY PERMITS derivation -- 'you may create and use a modified version of this License if you rename the license and remove any references to the name of the license steward'. That clause is why PMPL is legitimate; Mozilla anticipated it. * The GNU licences EXPRESSLY FORBID it -- every GPL/AGPL text says 'changing it is not allowed'. A PAGPL cannot be produced by editing AGPL text the way PMPL was produced from MPL; it would need a freshly drafted licence and legal advice. * Permissive licences place no such restriction, so PMIT and siblings are straightforward by comparison. .claude/CLAUDE.md carried the same three-repo cap and is updated in lockstep, now deferring to LICENCE-POLICY.adoc as authoritative rather than duplicating the list -- two copies of a growing register would drift apart. Co-Authored-By: Claude Opus 5 --- .claude/CLAUDE.md | 2 +- LICENCE-POLICY.adoc | 43 +++++++++++++++++++++++++++++++++++++++---- 2 files changed, 40 insertions(+), 5 deletions(-) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index a09b2ffa..1db40f2c 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -18,7 +18,7 @@ | **2. The 007 repo** | All Rights Reserved (ARR) | `hyperpolymath/007` specifically. Out-of-scope for any normalisation, scanning, or labelling. Surface to owner only. | | **3. Shared with son (Joshua)** | `AGPL-3.0-or-later` | Repos with son as co-author/maintainer. Examples: `idaptik`, `paint-type`. Permanent. | | **4. Third-party / forks** | DO NOT TOUCH | Whatever upstream chose. Never sweep, never normalise. Flag as out-of-scope if it surfaces in an audit. | -| **5. Palimpsest carve-out (extremely narrow)** | `PMPL-1.0-or-later` | EXACTLY three repos: `palimpsest-license` + `palimpsest-plasma` + `metadatastician/consent-aware-web`. The first two retroactively; `metadatastician/consent-aware-web` **prospectively only** (don't flip existing content). NOWHERE ELSE. | +| **5. Palimpsest register** | `PMPL-1.0-or-later` | **Only repos named in the register** in `LICENCE-POLICY.adoc` Rule 2 — currently five: `palimpsest-license`, `palimpsest-plasma`, `metadatastician/consent-aware-web` (prospectively only — don't flip existing content), `insolvency-tycoon`, `sim-public-relations`. The cap of three was lifted 2026-08-26 as the Palimpsest family develops; the register is a growing **allowlist**, so PMPL in an unlisted repo is still drift. `LICENCE-POLICY.adoc` is authoritative — do not duplicate the list's contents here. | ### Hard rules for agents diff --git a/LICENCE-POLICY.adoc b/LICENCE-POLICY.adoc index e3d82d91..5585a9a8 100644 --- a/LICENCE-POLICY.adoc +++ b/LICENCE-POLICY.adoc @@ -29,15 +29,50 @@ narrative docs under CC-BY-SA-4.0 — unless Rule 2, Rule 3 or Rule 4 applies. T `LICENSES/` directory carries the canonical text for both (`MPL-2.0.txt`, `CC-BY-SA-4.0.txt`). -=== Rule 2 — PMPL Is a Narrow Carve-Out (Three Repos Only) +=== Rule 2 — PMPL Is an Explicit Register (Currently Five Repos) -`PMPL-1.0-or-later` (Palimpsest-MPL) is **not** the estate default. Per the -estate licence policy (link:.claude/CLAUDE.md[.claude/CLAUDE.md] §License -Policy), PMPL applies to *exactly three* repositories and nowhere else: +`PMPL-1.0-or-later` (Palimpsest-MPL) is **not** the estate default. It applies +only to repositories **named in the register below**. + +Owner ruling 2026-08-26: the previous *"exactly three and nowhere else"* cap is +lifted. The Palimpsest family is under active development — PMPL first, then +compatible variants adding the Palimpsest and post-quantum layers where the base +licence permits derivation — so more repositories will move onto it over time. + +**The register still binds.** This is a growing allowlist, not an open door: a +PMPL declaration in a repository *not* named here is drift, and remains +detectable as such. Adding a name is an owner decision and a one-line change to +this list. + +==== The register * `palimpsest-license` — defines the PMPL identifiers * `palimpsest-plasma` — the PMPL implementation / tooling repo * `consent-aware-web` (formerly `consent-aware-http`, extracted to `metadatastician/consent-aware-web` 2026-08-07) — **prospectively** (do not flip existing content) +* `insolvency-tycoon` — added 2026-08-26 +* `sim-public-relations` — added 2026-08-26 + +==== On the wider Palimpsest family + +The intent is to mirror the common licences with a `P`-prefixed variant — +`PMIT`, `PBSD` and so on — each adding the Palimpsest and post-quantum layers. +**Only PMPL exists today.** + +One legal constraint is worth recording before effort goes into the others, +because it is not symmetric: + +* **MPL-2.0 §10.3 expressly permits derivation** — *"you may create and use a + modified version of this License if you rename the license and remove any + references to the name of the license steward"*. That clause is why PMPL is + legitimate; Mozilla anticipated exactly this. +* **The GNU licences expressly forbid it** — every GPL/AGPL text carries + *"Everyone is permitted to copy and distribute verbatim copies of this license + document, but changing it is not allowed."* A `PAGPL` therefore **cannot** be + produced by editing AGPL text the way PMPL was produced from MPL. Achieving + AGPL §13's network-copyleft effect under a Palimpsest overlay would require a + freshly drafted licence, and legal advice rather than a text edit. +* Permissive licences (MIT, BSD, Apache-2.0) place no such restriction, so + `PMIT` and siblings are straightforward by comparison. Every other sole-owner repository — including this `standards` repo — is MPL-2.0 (code) / CC-BY-SA-4.0 (docs) per Rule 1, both as the *stated* and the