Skip to content

[carve-out 8/9] ⚠️ OWNER-ONLY licence-flag items: 007 audits in public canon; PALIMPSEST.adoc narrative #497

Open

Description

@hyperpolymath

Child of #479. Flag-only per the Manual-Only licence guardrail — no agent edits, no sweeps. Both items need the owner's hand or explicit per-file approval.

  1. toolchain-readiness-grades/references/007/ — licence exposure. 24 verbatim audit documents of the All-Rights-Reserved 007 project sit inside this public MPL-2.0/CC-BY-SA repo. Recommended: move them back to hyperpolymath/007 (private), keep at most one anonymised exemplar inline for the TRG rubric. Owner decision on timing and whether any content is safe to keep public.
  2. PALIMPSEST.adoc — full Palimpsest narrative in a repo outside the three-repo carve-out (palimpsest-license, palimpsest-plasma, consent-aware-http — the only repos that should "talk about" Palimpsest per the 2026-06-02 directive). It is also internally self-contradicting (its own Licence Summary table says stated licence PMPL; its SPDX Header Summary labels standard code AGPL). Recommended: move the narrative to palimpsest-license, leave a one-paragraph pointer. Related flag-only observations for the same owner session: LICENSES/PMPL-1.0-or-later.txt present outside the carve-out; duplicate lowercase licenses/ dir; coordination.k9 still declaring license: PMPL + a pmpl-license-only invariant.

Downstream automation note: hypatia/gitbot-fleet must keep treating everything here as :review-capped. A "PMPL-token drift outside carve-out" detector (report-only) can point at this issue as its tracking reference.

Activity

  1. hyperpolymath commented on Jul 28, 2026

    @hyperpolymath
    OwnerAuthor

    FLAGGED FOR OWNER DECISION per Issue #479

    The following items require OWNER decision and should NOT be swept automatically:

    1. toolchain-readiness-grades/references/007/ - 24 verbatim audits of the All-Rights-Reserved 007 repo sitting in a public canon repo. Should be moved back to hyperpolymath/007.

    2. PALIMPSEST.adoc - Full narrative should be moved to palimpsest-license repo, leaving only a one-paragraph pointer. Only the three carve-out repos should talk about Palimpsest.

    3. rhodium-standard-repositories/PALIMPSEST.adoc - Duplicate in satellites directory (to be evicted per [carve-out 4/9] rhodium-standard-repositories/ cleanup: de-vendor satellites/, merge templates into rsr-template-repo, delete the lying .gitmodules #493).

    Action required: Owner review and decision on these licence-sensitive items. Do NOT sweep automatically.

  2. added
    documentationDocs, prose, diagrams, READMEs, ADRs
    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup
    on Aug 24, 2026
  3. hyperpolymath commented on Aug 27, 2026

    @hyperpolymath
    OwnerAuthor

    Inventory confirmed and expanded — staying flag-only, per the ruled decision docket

    The flag-only handling is correct and continues. What changed is the scope, which roughly tripled against the issue text (measured 2026-08-27):

    item issue says measured
    audit-*.adoc under toolchain-readiness-grades/references/007/ 24 25
    PALIMPSEST.adoc root only 3 locations (+ rhodium-standard-repositories/ and its satellites/rsr-certifier/)
    PMPL artifacts 1 6 (root LICENSES/, a2ml/LICENSES/, two editors/vscode/LICENSE-PMPL, rhodium.../license/, the migration runbook)

    ⚠️ Two of the six PMPL artifacts travelled with the a2ml eviction (#680) and now live in hyperpolymath/a2ml — the flag follows the files. lowercase licenses/ and coordination.k9 confirmed still present here.

    Left open deliberately: this issue is the standing register of owner-only licence artefacts, and the register keeps working.

  4. hyperpolymath commented on Sep 30, 2026

    @hyperpolymath
    OwnerAuthor

    RULING D134 (2026-09-30T14:11Z) · scope: estate · basis: owner (direct answer, selector)

    OWNER TEXT: "this is going now to MPL-2.0 code, and CC-BY-SA-4.0 docs" — the 24 All-Rights-Reserved 007 audit docs are RELICENSED (docs CC-BY-SA-4.0, any code MPL-2.0) in place, not moved private

    surface: #787 (comment)

    The open question in this issue is answered by the ruling above; future agents should act on it rather than re-ask.

  5. added
    decisionA ruling is required before work can proceed
    and removed
    decisionA ruling is required before work can proceed
    on Sep 30, 2026
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

    documentationDocs, prose, diagrams, READMEs, ADRspriority:p1High - schedule nextscope:estateAffects many or all repos across the estatetech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions