diff --git a/docs/REPO_LICENSE_TRACKING.md b/docs/REPO_LICENSE_TRACKING.md index 889e235..2ab25ff 100644 --- a/docs/REPO_LICENSE_TRACKING.md +++ b/docs/REPO_LICENSE_TRACKING.md @@ -208,6 +208,9 @@ This file now also preserves the current truth that future models must not lose: - [HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md](C:/HyperTwist/docs/ops/HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md:1) - the dedicated release-placement checklist for that route is: - [HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md](C:/HyperTwist/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md:1) + - that checklist governs both browser-delivered `MPL` code and any public + commercial website, store, checkout, release, or download surface that + sells or delivers a build containing those `MPL` lanes The twenty-three permissive live lanes are: diff --git a/docs/ops/HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md b/docs/ops/HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md index 289dd10..d5d416c 100644 --- a/docs/ops/HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md +++ b/docs/ops/HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md @@ -44,6 +44,9 @@ Current verified product-side reality is: - the dedicated release-placement checklist for selling or externally distributing builds that include those `MPL` lanes is: - [HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md](C:/HyperTwist/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md:1) + - that checklist explicitly covers public commercial website, store, + checkout, release, and download surfaces when they sell or deliver builds + containing those `MPL` lanes - the closed `0R-E` packet still retains these non-live benchmark, oracle, or clean-room-later rows: - `cs0x7f/cstimer` diff --git a/docs/ops/HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md b/docs/ops/HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md index d5baaf2..4160a33 100644 --- a/docs/ops/HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md +++ b/docs/ops/HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md @@ -150,6 +150,9 @@ operational posture is: referenced third-party notices surface. 3. Inform recipients where the source for the `MPL`-covered code can be obtained. + - if HyperTwist sells or delivers the build through a public website, store, + checkout flow, release page, or download page, those public surfaces must + also point recipients to the notices and source-availability materials 4. If HyperTwist modified any `MPL`-covered file, make the modified source for that file available under the `MPL`. 5. Keep first-party files that contain no copied `MPL` code separate, so the diff --git a/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md b/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md index 185e703..fd84026 100644 --- a/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md +++ b/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md @@ -30,6 +30,11 @@ distribution surfaces must tell recipients: - where to read the `MPL-2.0` license - where to obtain the corresponding `MPL`-covered source +For HyperTwist, `public distribution surfaces` explicitly includes any public +website or marketplace page that sells, lists, checks out, or delivers a +downloadable build containing `MPL`-covered code, even when that website is not +itself serving `MPL`-covered browser JavaScript to the visitor. + ## What HyperTwist is relying on today For the current live lanes: @@ -75,8 +80,8 @@ What still does apply today: - if HyperTwist is sold or distributed as a downloadable desktop build that includes these lanes, the downloadable release package, in-product legal - surface, and release/download page still need the `MPL` notices and - source-availability links described below + surface, public product page, checkout/store page, and release/download page + still need the `MPL` notices and source-availability links described below - if a future HyperTwist website later delivers browser code containing `MPL`-covered material, the website notice branch becomes active at that time @@ -113,7 +118,33 @@ If HyperTwist is sold or distributed as a downloadable desktop product, put the - if HyperTwist modified `MPL`-covered files directly, publish those modified files under `MPL` -### 3. Public website or SaaS with server-side code only +### 3. Commercial website, checkout flow, store page, or direct download page + +If HyperTwist is sold, licensed, or distributed through a public website, +checkout flow, store listing, marketplace page, or direct download page, and +the distributed build contains `MPL`-covered code: + +1. treat those public pages as release/distribution surfaces +2. the product page, pricing page, checkout confirmation page, store listing, + release page, or download page should expose or link all of the following: + - an open-source notices page + - the `MPL-2.0` license text or a stable link to it + - the corresponding `MPL`-covered source location +3. the same rule applies even if the public website itself is only HTML, + marketing copy, store UI, or payment flow and does not itself ship + `MPL`-covered browser JavaScript +4. if `coqui-ai/TTS` models, voices, or payloads are shipped with the + downloadable build, those pages or their linked legal materials must also + point to the separate artifact-license disclosures + +For HyperTwist, this is the important split: + +- website sells or links a downloadable build containing `MPL` code: + release-page obligations apply +- website serves `MPL` browser code directly: + browser-bundle obligations also apply + +### 4. Public website or SaaS with server-side code only If the product is a hosted service and users do not receive the `MPL`-covered code in the browser or as a download: @@ -122,7 +153,7 @@ code in the browser or as a download: - a public website legal page is not required solely for that server-side use - keep internal release records anyway -### 4. Public website that delivers client-side JavaScript or other browser code +### 5. Public website that delivers client-side JavaScript or other browser code If HyperTwist delivers browser code that includes `MPL`-covered files or a bundle containing them: @@ -136,7 +167,7 @@ bundle containing them: 5. the bundled asset or release notes should not hide the fact that the code is present -### 5. Source repo only, without distributed build +### 6. Source repo only, without distributed build If HyperTwist only keeps the code in source control and does not yet distribute it: @@ -166,12 +197,35 @@ Before selling or externally distributing HyperTwist in a form that includes ### Required public distribution surfaces for downloadable releases -- the release page or store page should reference the open-source notices -- the release page or store page should reference the corresponding source - location +- the public product page, pricing page, checkout page, store page, release + page, or download page should reference the open-source notices +- those public pages should reference the `MPL-2.0` text directly or through a + stable legal/notices page +- those public pages should reference the corresponding source location - if `coqui-ai/TTS` models, voices, or payloads are shipped, the distribution materials should link to their separate artifact-license page +### Required public commercial website and marketplace surfaces + +If HyperTwist is sold commercially through its own website or a marketplace, +the minimum public surfaces that should carry or link the legal materials are: + +- the product overview page +- the pricing or purchase page +- the checkout or purchase confirmation page when HyperTwist controls it +- the release notes page for the shipped build +- the download page or installer-delivery page +- the marketplace or store listing where the platform allows legal links + +At least one of those public surfaces should link to a stable HyperTwist +`Open Source Notices` or `Legal` page that contains: + +- the `MPL-2.0` license text or a stable link to the full text +- the corresponding source-availability location for the exact shipped build +- component identification for `cubing/cubing.js` and `coqui-ai/TTS` +- separate artifact-license disclosures for any shipped `coqui-ai/TTS` models, + voices, or payloads + ### Required public distribution surfaces for browser-delivered bundles - the website should have a public open-source notices page @@ -212,6 +266,17 @@ If the public website is only marketing the product: - it does not need a special `MPL` page solely because the product exists - it is still cleaner to link to the downloadable product's legal/notices page +If the public website markets the product and also sells it or links the +download for a build containing `MPL`-covered code: + +- it is no longer just a marketing-only surface +- it becomes a release/distribution surface for notice-placement purposes +- it should link to the open-source notices page +- it should link to the `MPL-2.0` text directly or through that notices page +- it should link to the corresponding source location +- if `coqui-ai/TTS` payloads are shipped, it should link to the separate + payload or artifact-license disclosures + If the public website delivers browser code containing `MPL`-covered material: - it should have a public legal or open-source notices page @@ -227,7 +292,8 @@ these lanes is: - `ThirdPartyNotices.txt` - `licenses/MPL-2.0.txt` - an in-product `Open Source Notices` or `Licenses` screen -- release-page notice links +- product-page, store-page, checkout-page, and release/download-page notice + links when those surfaces sell or deliver the build - a stable source URL for the corresponding `MPL`-covered files - separate artifact-level notice handling for any shipped `coqui-ai/TTS` models, voices, or payloads diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md b/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md index b6f53a8..85247f1 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md @@ -216,6 +216,9 @@ Donor-strength rule: - [HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md](C:/HyperTwist/docs/ops/HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md:1) - the dedicated release-placement checklist for this route is: - [HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md](C:/HyperTwist/docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md:1) + - that checklist explicitly covers public commercial website, store, + checkout, release, and download surfaces when they sell or deliver builds + containing those `MPL` lanes - `Phase 0R` is now closed for the remaining `47` non-live rows - `Phase 1R` is now closed as the retained-set contract and handoff overhaul - `Phase 2R` is now closed as the retained-set ownership and acceptance packet sequence