Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
43 changes: 39 additions & 4 deletions LICENCE-POLICY.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading