scriptoriumadmin/hypertwist
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify current MPL website trigger state

Browse source
This commit is contained in:
axiomlogicnexus 2026-05-25 04:37:38 +02:00
parent d795959468
commit 723dbfaf3d
1 changed files with 36 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
docs/ops/HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md
View file

@ -44,6 +44,42 @@ For the current live lanes:
- model, voice, and payload artifacts remain separate per-artifact review
- model or payload approval is not created by the package-code notice alone
## Current repo-state answer
For the current checked HyperTwist product state on `2026-05-25`, the answer is:
- no, the live HyperTwist product does not currently present evidence of a
public website or browser bundle that ships `MPL`-covered `cubing/cubing.js`
or `coqui-ai/TTS` code to end users
Why that answer is correct:
- the live product root is `UnrealHyperTwist/`, which is the current
first-party Unreal application root, not a deployed browser app shell
- the top-level website-like folders at repo root are archive/reference storage
rather than the active product shell
- the landed `cubing/cubing.js` packet is explicitly a first-party compiled
contract and reference-bundle lane; it says no upstream app shell or Twizzle
shell was landed
- the landed `rubix-cube-solver` browser/webcam shell packet is explicitly a
first-party browser-shell profile and session-state contract; it explicitly
excludes bundled frontend-asset redistribution
- the landed `coqui-ai/TTS` packet is explicitly a first-party advanced
narration orchestration profile; it explicitly excludes downloadable
voice/model shipping
So the website-specific `MPL` notice branch is not triggered today merely by
the current checked product code.
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
- if a future HyperTwist website later delivers browser code containing
`MPL`-covered material, the website notice branch becomes active at that time
## Scenario matrix
### 1. Internal-only use inside the organization