Skip to content

policy: Rule 2 becomes a growing register — five repos, cap lifted - #649

Merged
hyperpolymath merged 1 commit into
mainfrom
policy/rule-2-register-of-five
Aug 26, 2026
Merged

policy: Rule 2 becomes a growing register — five repos, cap lifted#649
hyperpolymath merged 1 commit into
mainfrom
policy/rule-2-register-of-five

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

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. That is exactly the trap Rule 5 was written to avoid for games.

The shape matters: allowlist, not 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 precisely how 471 files of residue accumulated unnoticed in this repo.

So the register still binds. A PMPL declaration in an unlisted repo is drift; adding a name is an owner decision and a one-line change.

A legal constraint on the wider P-family, recorded before effort goes into it

It is not symmetric, which is not obvious:

Base licence Can a P-variant be derived from its text?
MPL-2.0 Yes — §10.3 expressly permits it: "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." This clause is why PMPL is legitimate; Mozilla anticipated exactly this.
GPL / AGPL No. Every GNU licence text states "changing it is not allowed." PAGPL cannot be made by editing AGPL text the way PMPL was made from MPL — it would need a freshly drafted licence achieving §13's effect, and legal advice rather than a text edit.
MIT / BSD / Apache-2.0 ✅ No such restriction — PMIT and siblings are straightforward.

Kept in lockstep

.claude/CLAUDE.md carried the same three-repo cap. Updated, and now defers to LICENCE-POLICY.adoc as authoritative rather than duplicating the list — two copies of a growing register would drift apart.

🤖 Generated with Claude Code

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 <noreply@anthropic.com>
@hyperpolymath
hyperpolymath merged commit 6cb237c into main Aug 26, 2026
@hyperpolymath
hyperpolymath deleted the policy/rule-2-register-of-five branch August 26, 2026 17:44
@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 43 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: be9a5ba5-9e11-428e-8427-db85894eb2d6

📥 Commits

Reviewing files that changed from the base of the PR and between 53eb567 and d8e8530.

📒 Files selected for processing (2)
  • .claude/CLAUDE.md
  • LICENCE-POLICY.adoc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

Copy link
Copy Markdown

@gitar-bot

gitar-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant