HyperTwist — LICENSETRACKING.md

Project policy

Every repo should be judged as:

incorporate as-is
bounded sidecar
reverse engineer
pattern-only

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: 6
permissive live lanes: 5
restrictive live lanes: 1

The five permissive live lanes are:

abunickabhi/5style-Trainer
tao-yu/Alg-Trainer
Lykos/cube_trainer
poliva/cubedex
newyork-anthonyng/rubiks-cross-trainer

The one restrictive live lane is:

onionhoney/roux-trainers

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 remaining 65 HyperTwist rows should now be treated as an evaluation backlog.

That means:

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

Read together with:

C:\HyperTwist\docs\HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.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:

five trainer-style permissive lanes are already live
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.

2.8 KiB Raw Blame History