scriptoriumadmin/hypertwist
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
hypertwist/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md
axiomlogicnexus 7da4b1da42 Close HyperTwist Phase 4R packet 4R-B
2026-05-13 21:06:22 +02:00

7.7 KiB
Raw Blame History

HyperTwist — LICENSETRACKING.md

Project policy

Every repo should be judged as:

  • incorporate as-is
  • bounded sidecar
  • reverse engineer
  • pattern-only

File boundary

This file is the project-level license policy file.

Use it for:

  • decision categories
  • status vocabulary
  • phase rules
  • project-level compliance reminders

Do not use it for:

  • repo-specific author attribution
  • repo-specific copyright notice text
  • package-specific Apache NOTICE retention requirements
  • mixed-asset attribution lists
  • repo-row source-basis exceptions

Store those details only in:

  • C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md

If a schedule, handoff, or implementation packet needs a repo-row legal fact, point back to the root tracker instead of duplicating the detail here.

Packet docs may include a concise per-repo licensing snapshot for handoff clarity.

They still must point back to C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md for the full repo-row legal record.

Current verified implementation truth

At the moment, HyperTwist should be described this way:

  • current curated shallow-eval set: 71 repos
  • currently verified live/implemented in checked Unreal surfaces: 16
  • permissive live lanes: 13
  • boundary-sensitive live lanes: 2
  • restrictive live lanes: 1

The thirteen permissive live lanes are:

  • Aarav2709/KubeTimr
  • apache/echarts
  • abunickabhi/5style-Trainer
  • google/model-viewer
  • Hypercubers/hypercubing.xyz
  • mrdoob/three.js
  • pmndrs/react-three-fiber
  • pmndrs/xr
  • tao-yu/Alg-Trainer
  • Lykos/cube_trainer
  • met4citizen/TalkingHead
  • poliva/cubedex
  • newyork-anthonyng/rubiks-cross-trainer

The one restrictive live lane is:

  • onionhoney/roux-trainers

The two boundary-sensitive live lanes are:

  • cubing/cubing.js
  • cutelyaware/magiccube4d

That restrictive lane should be treated as:

  • properly clean-roomed
  • properly implemented afterward
  • the only currently verified restrictive HyperTwist repo that is already landed/live

Required status vocabulary

For HyperTwist, keep these labels separate:

  • landed/live now
  • selected or queued but not live
  • future or reserve
  • benchmark/oracle only
  • restrictive clean-room pending

Do not use:

  • full
  • implemented
  • already live

for a repo row unless current first-party evidence supports it.

Current reset rule

The non-live HyperTwist rows were treated as a Phase 0R evaluation backlog before renewed widening.

That closed with these packet classes:

  • permissive rows through deep source integration evaluation
  • boundary-sensitive rows through explicit adapter/dependency review
  • restrictive rows through explicit clean-room scheduling unless already landed through the onionhoney/roux-trainers lane
  • benchmark, reserve, no-license, and all-rights-reserved rows through keep/discard decisions

Current Phase 0R packet status:

  • 0R-A is closed
  • 0R-B is closed
  • 0R-C is closed
  • 0R-D is closed
  • 0R-E is closed
  • non-live rows already packet-evaluated: 65
  • non-live rows still awaiting packet evaluation: 0

Current practical interpretation:

  • Phase 0R is now fully closed
  • Phase 1R is now fully closed
  • Phase 2R-A is now fully closed for the five core retained permissive rows
  • Phase 2R-B is now fully closed for the primary retained permissive support-plane rows in scope
  • Phase 2R-C is now fully closed for the final residual 0R-B permissive rows
  • Phase 2R is now fully closed for the retained permissive set
  • the sixteen already-live rows now have source-backed preservation authority in C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md
  • the retained-set contract now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md
  • the core ownership and acceptance packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
  • the support-plane ownership and acceptance packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
  • the residual 0R-B adjunct and alternative-lane packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
  • the landed Aarav2709/KubeTimr widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md
  • the landed Hypercubers/hypercubing.xyz widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md
  • the landed apache/echarts widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md
  • the landed google/model-viewer widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md
  • the landed met4citizen/TalkingHead widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md
  • the landed mrdoob/three.js, pmndrs/react-three-fiber, and pmndrs/xr widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md
  • the landed cubing/cubing.js boundary-sensitive widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_4R_PACKET_4R_A_CUBING_JS_ADAPTER_IMPLEMENTATION_2026-05-13.md
  • the landed cutelyaware/magiccube4d boundary-sensitive widening packet now lives in C:\HyperTwist\docs\HYPERTWIST_PHASE_4R_PACKET_4R_B_MAGICCUBE4D_ADAPTER_IMPLEMENTATION_2026-05-13.md
  • the next bounded move is Phase 4R-C

Read together with:

  • C:\HyperTwist\docs\HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md
  • C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md
  • C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md
  • C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
  • C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
  • C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
  • C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md
  • C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md
  • C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md
  • C:\HyperTwist\docs\HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md

Family-specific guidance

Simulation foundations

Direct use can be sensible if the engine is excellent and the obligations are acceptable. Reverse engineering is cleaner if deep proprietary/native integration is the true goal.

CV and coaching

Often best as bounded services, donor modules, or selective reimplementations.

Trainers and timers

These are often strategic donors or comparators rather than foundations.

Current HyperTwist correction:

  • thirteen permissive lanes are already live, including the landed analytics/reporting lane, the landed hypercubing knowledge and community-reference lane, and the landed browser spatial owner trio
  • two boundary-sensitive lanes are already live: cubing/cubing.js through an explicit MPL-aware adapter posture and cutelyaware/magiccube4d through an explicit attribution/provenance boundary
  • onionhoney/roux-trainers is the one restrictive training lane already landed through clean-room implementation
  • timer comparators such as cstimer still remain benchmark/reference rows until deep evaluation says otherwise

Hyper ecosystems

Treat carefully. Some repos matter historically or educationally even when they are not operational foundations.