# HyperTwist Trainer Foundation And Persisted Coaching Hierarchy Reconciliation - 2026-05-27

## Status

This document is the source-backed reconciliation note for the current
trainer-family hierarchy across:

- `tao-yu/Alg-Trainer`
- `Lykos/cube_trainer`
- the first-party training, review-plan, follow-up, and coaching surfaces
- the landed `Aarav2709/KubeTimr` timer substrate
- the landed `kash/cubedesk` trainer-session and integrated smart-device
  workflow family
- the now-demoted `poliva/cubedex` restrictive comparison row

It answers one narrow question:

- do the current `tao-yu/Alg-Trainer` and `Lykos/cube_trainer` source surfaces
  require reopening already landed HyperTwist training and coaching packets
  before any future trainer-adjacent widening is considered

Result:

- no product-code reopening is required
- yes selective authority backfill is required so the landed trainer-family
  split remains explicit in current canon instead of living only in older
  preserve prose

## Source basis

- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
- `C:\Workspaces\HyperTwist\repos.manifest.json`
- `C:\Workspaces\HyperTwist\mirrors\permissive\tao-yu\Alg-Trainer\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\tao-yu\Alg-Trainer\js\controls.js`
- `C:\Workspaces\HyperTwist\mirrors\permissive\tao-yu\Alg-Trainer\js\oneLookLastLayer.js`
- `C:\Workspaces\HyperTwist\mirrors\permissive\Lykos\cube_trainer\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\Lykos\cube_trainer\app\models\training_session.rb`
- `C:\Workspaces\HyperTwist\mirrors\permissive\Lykos\cube_trainer\client\src\app\utils\sampling\weighted-sampler.ts`
- `C:\Workspaces\HyperTwist\mirrors\permissive\Lykos\cube_trainer\client\src\app\training\trainer.service.ts`
- current first-party training code and content surfaces under:
  - `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Public\HyperTwistTraining`
  - `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Private\HyperTwistTraining`
  - `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog`

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Route | Width | Result |
|---|---|---|---|---|---|
| Landed first-party training-session orchestration, review-plan state, follow-up queues, coach summaries, and broader runtime integration | first-party training and coaching surfaces | the landed permissive trainer rows remain subordinate foundations | existing landed first-party route | `F2` | unchanged live implementation owner |
| Broad algorithm-training shell, organized set/subset case corpus, timer/reveal/scramble/virtual-cube flow, and smartcube-capable algorithm-drill posture | `tao-yu/Alg-Trainer` | current first-party training/coaching surfaces remain the live orchestration owner; `Lykos/cube_trainer` remains the persistence-heavy coaching adjunct | existing landed permissive route | `F2` | unchanged landed trainer-foundation owner beneath current first-party code |
| Persisted training-session modeling, weighted sampling, method exploration, and BLD-heavy coaching/domain value | `Lykos/cube_trainer` | `tao-yu/Alg-Trainer` remains the broader algorithm-shell and case-corpus owner; current first-party training/coaching surfaces remain the live orchestration owner | existing landed permissive route | `F2` | unchanged landed persisted-coaching owner beneath current first-party code |
| Landed local timer substrate and integrated smart-device workflow composition | `Aarav2709/KubeTimr` plus bounded `kash/cubedesk` lanes | the trainer-family rows remain adjacent, not replacement owners | existing landed permissive and clean-room routes | `F2` | unchanged live implementation owner |
| Smartcube-aware practice-shell, review/SRS UX, and split-timing comparison | `poliva/cubedex` restrictive reference row | current first-party and permissive landed trainer owners remain stronger for live implementation | restrictive comparison only | `F2` | unchanged non-live comparison row |

## Why no product-code reopening is required

### `tao-yu/Alg-Trainer`

`Alg-Trainer` still correctly owns the broad landed permissive trainer
foundation slice.

The checked source remains strongest for:

- large organized algorithm case-corpus breadth
- set/subset-oriented drill structure
- timer plus reveal plus scramble plus virtual-cube flow
- smartcube-capable algorithm-drill posture
- user-defined algset friendliness

That is still real live preserve value. It does not make `Alg-Trainer` the
owner of HyperTwist's current persistence-heavy review-plan, queue, follow-up,
or coaching orchestration family.

### `Lykos/cube_trainer`

`cube_trainer` still correctly owns the narrower persistence-heavy coaching
adjunct slice.

The checked source remains strongest for:

- persisted training-session modeling
- weighted and recency-aware case selection
- method exploration and case-count reasoning
- BLD-heavy domain and commutator-oriented coaching value

That is still real live preserve value. It does not make `cube_trainer` the
owner of the broad algorithm-shell/case-corpus foundation and it does not
reopen the already landed first-party training-session, review-plan,
follow-up, or coaching dashboard union.

### Current first-party training and coaching surfaces

HyperTwist already owns the practical live family in current first-party code:

- training-session runtime and orchestration
- review-plan state, repository/runtime access, and update flow
- coach action plans, follow-up packets, and queue state
- weighted selection-policy import and runtime handling
- smartcube-capability preview and training runtime integration
- materialized donor-attribution and imported deck/content-pack surfaces

Those current first-party surfaces are already broader than either preserve row
alone and already sit above the adjacent landed timer, smart-device, and
comparison rows.

## Selective backfill result

### Earlier preserve note reopened

- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`

### Earlier retained-set contract reopened

- `C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md`

### Reason

The live-lane audit already captured the raw preserve split, but the later
first-party training stack and the adjacent `KubeTimr` / `CubeDesk` /
`cubedex` clarification passes mean the trainer-family hierarchy now needs to
be explicit in current canon:

- `tao-yu/Alg-Trainer` remains the landed broad algorithm-training shell and
  case-corpus foundation
- `Lykos/cube_trainer` remains the landed persisted coaching and
  weighted-sampling adjunct
- current first-party code owns the practical training-session, review-plan,
  queue, follow-up, and coaching union above them
- neither row is a default reopened implementation queue row

### Change class

- repo-local extraction did not change
- cross-lane authority wording was sharpened
- no cleanup interpretation changed
- no product-code change occurred

### What remained valid

- both rows remained landed permissive preserve lanes
- the current first-party training/coaching stack remained valid
- the adjacent `KubeTimr`, `CubeDesk`, and `cubedex` hierarchy calls remained
  valid

### What changed

The dependent canon now makes the exact current trainer-family split explicit
instead of leaving it distributed across older preserve prose.

## Propagation result

### Feature registry

Updated.

The registry now explicitly carries the landed algorithm-training foundation
and landed persisted-coaching/weighted-sampling adjunct families in addition to
the generic first-party training/coaching rows.

### Cross-lane doctrine

No doctrine wording change was needed.

### Skillization

No doctrine or `SKILLS.md` change was needed.

This pass did not create or reopen any command or skill surface.

### Legal evidence

No license-status or custody change occurred.

The repo-row tracker, live-lane audit, feature registry, retained-set
contract, and manifest notes were sharpened instead.

## Operational answer

Before any future trainer-adjacent widening is opened, the correct move was
this evaluation and selective backfill pass first.

After this pass:

- do not reopen the live product code
- do not reinterpret `tao-yu/Alg-Trainer` as the persistence-heavy coaching
  owner
- do not reinterpret `Lykos/cube_trainer` as the broad trainer-shell or
  case-corpus foundation owner
- if HyperTwist later widens this family again, do it only against a narrower
  trainer sub-slice that is still provably missing above the current first-party
  training/coaching union
