Skip to content

FLAG: discarded local edit wanted iseriser relabelled PMPL-1.0-or-later — owner decision needed #104

Description

@hyperpolymath

Flag from the R-16 reconciliation (2026-08-28 ruling, filed 2026-08-31). No licence change made.

An unpublished local edit to README.md relabelled the licence badges/section from the ratified MPL-2.0 (code) / CC-BY-SA-4.0 (docs) split to "PMPL-1.0-or-later" + Palimpsest Covenant. Per ruling R-28b (iseriser singleton) the merge took origin's .adoc, which restores the ratified split — a merge resolution must not enact a licence change, and PMPL relabelling of MPL repos is a known contamination class (PMPL is ratified for exactly three repos).

If iseriser is genuinely intended to move to PMPL/Palimpsest, that is an explicit owner decision to make here — the discarded edit is preserved in the estate control tree at forensics/r16-class-conflict-reports/iseriser.diff. If not intended, close this issue.

🤖 Generated with Claude Code

Activity

  1. hyperpolymath commented on Sep 21, 2026

    @hyperpolymath
    OwnerAuthor

    Ruling: not intended — iseriser stays MPL-2.0 (code) / CC-BY-SA-4.0 (docs). Closing per this issue's own instruction.

    Ruling recorded 2026-09-21. No licence change. The ratified split stands.

    Grounds

    1. standards/3-practice/LICENCE-POLICY.adoc, Rule 1 — the estate default is MPL-2.0 (code) / CC-BY-SA-4.0 (prose). iseriser is category-default with no Rule 3/4/5 classification.
    2. Rule 2 — PMPL is an explicit register (currently five repos: palimpsest-license, palimpsest-plasma, consent-aware-web prospective, insolvency-tycoon, sim-public-relations; the "exactly three" cap cited in this issue's body was lifted by owner ruling 2026-08-26). iseriser is not register-named, and a PMPL declaration in a repo not named there is defined as drift, detectable as such. Adding a name is an owner decision — no such decision exists or is being made.
    3. A2 — never relicense an existing file; never run an automated licence sweep. The discarded local edit had no authority even had it survived.
    4. R-16 / ruling R-28b (iseriser singleton) — a merge resolution must not enact a licence change; origin's ratified tree was correctly kept. The discarded edit remains preserved in the estate control tree at forensics/r16-class-conflict-reports/iseriser.diff — retained as forensic record, no further action.
    5. Owner ruling 2026-09-02, already executed — chore(license): migrate PMPL scaffold emissions to MPL-2.0 per owner ruling #106 ("migrate PMPL scaffold emissions to MPL-2.0 per owner ruling", merged 2026-09-02) restored the canonical MPL-2.0 text in src/codegen/scaffold.rs's generate_license(), fixed guix.scm, and installed the contractile.just licence gate. That ruling post-dates this flag by two days; this comment is the bookkeeping that closes the loop.

    Fresh audit of main (2026-09-21) — clean

    Surface Found
    README.adoc badges (lines 1–4) + License § (387–391) MPL-2.0 + CC-BY-SA-4.0
    LICENSE, LICENSES/ (MPL-2.0.txt, CC-BY-SA-4.0.txt) canonical
    Cargo.toml license = "MPL-2.0" + SPDX header
    src/codegen/scaffold.rs — all 6 licence emitters MPL-2.0
    Only remaining palimpsest refs the contractile.just contamination guard (line 65, root + satellites/a2mliser) — deliberate
    Only remaining PMPL refs an estate-policy citation comment in .machine_readable/6a2/AGENTIC.a2ml line 29 (root + satellite) — not a licence declaration

    No residual contamination; nothing to migrate.

    Cross-links (estate bookkeeping)

    Closing this issue. If iseriser is ever genuinely intended to join the Rule 2 register, the mechanism is a one-line register addition by owner decision — not a badge edit.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    decisionA ruling is required before work can proceed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions