# HyperTwist Smartcube Practice, Review, And SRS Hierarchy Reconciliation - 2026-05-27

## Status

This document is the source-backed reconciliation note for the current
smartcube-aware practice, review, spaced-repetition, and split-timing family
across:

- `poliva/cubedex`
- the first-party training, review-plan, coaching, and stats/history surfaces
- the landed `Aarav2709/KubeTimr` timer substrate
- the landed `kash/cubedesk` trainer-session and integrated smart-device
  workflow family
- the landed permissive trainer foundations under `tao-yu/Alg-Trainer` and
  `Lykos/cube_trainer`

It answers one narrow question:

- does the current `poliva/cubedex` source require reopening already landed
  HyperTwist training, review, timer, or smart-device packets before any future
  smartcube-practice widening is considered

Result:

- no product-code reopening is required
- yes selective authority backfill is required
- `poliva/cubedex` should no longer be treated as a default future clean-room
  candidate row

## 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\restrictive\poliva\cubedex\README.md`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\poliva\cubedex\src\hooks\useTrainingState.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\poliva\cubedex\src\lib\srs.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\poliva\cubedex\src\hooks\useSmartcubeConnection.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\poliva\cubedex\src\views\PracticeView.tsx`
- 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 sessions, review-plan state, spaced review flow, recognition-versus-execution timing policy, stats/history, and smartcube-capability surfaces | first-party training and coaching surfaces | `poliva/cubedex` as comparison context only | existing landed first-party and permissive routes | `F2` | unchanged live implementation owner |
| Landed local timer substrate and integrated smart-device workflow composition | `Aarav2709/KubeTimr` plus bounded `kash/cubedesk` lanes | `poliva/cubedex` as comparison context only | existing landed permissive and clean-room routes | `F2` | unchanged live implementation owner |
| Broad trainer-foundation and persisted coaching lane | `tao-yu/Alg-Trainer` plus `Lykos/cube_trainer` | `poliva/cubedex` as comparison context only | existing landed permissive routes | `F2` | unchanged live implementation owner |
| Smartcube-aware practice-shell comparison, offline-first drill UX composition, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison | `poliva/cubedex` | current first-party owners remain stronger for live implementation | preserve-only now; later `R4` only if a narrower first-party gap is actually proven | `F2` | retained restrictive comparison row only |

## Why no product-code reopening is required

### `poliva/cubedex`

`cubedex` still has real comparison value, but its strongest value is now
narrower than the already landed first-party family.

The restrictive source is still useful for:

- smartcube-aware practice-shell expectations
- offline-first drill UX composition
- review and spaced-repetition workflow presentation
- recognition-versus-execution timing presentation
- local stats and training-history presentation

That is useful comparison context. It is not proof that HyperTwist still lacks
an owner for the underlying training, review, timer, or smart-device family.

### Current first-party training and review surfaces

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

- review-plan state, review-history, and review-plan repository/runtime APIs
- explicit recognition and execution split-phase timing definitions
- smartcube capability flags and smartcube-capability preview surfaces
- active review-plan resume, stored-plan access, and review-plan-backed launch
  behavior
- first-party review policy, follow-up, and stats/history surfaces

Those first-party surfaces are already broader than a future `cubedex`
promotion would need to be.

### `KubeTimr`, `CubeDesk`, `Alg-Trainer`, and `cube_trainer`

Adjacent retained or landed owners are also already explicit:

- `KubeTimr` keeps the landed local timer substrate
- `kash/cubedesk` keeps the landed trainer-session and integrated smart-device
  workflow composition family
- `tao-yu/Alg-Trainer` remains the landed permissive algorithm-training
  foundation
- `Lykos/cube_trainer` remains the landed permissive persisted coaching and
  weighted-sampling lane

That means `cubedex` no longer reads like the next natural implementation queue
row. It reads like restrictive comparison context beneath already stronger live
owners.

## 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 earlier custody correction fixed the legal posture, but it did not finish
the authority split.

Later comparison against current first-party training/review/timer and
smart-device surfaces sharpens the exact remaining role:

- `poliva/cubedex` is not a landed permissive lane anymore
- `poliva/cubedex` is not the current live owner of the smartcube-aware
  practice/review/SRS family anymore
- `poliva/cubedex` is not the default next clean-room queue row either
- `poliva/cubedex` remains useful only as restrictive comparison context for a
  narrower practice-shell and review UX slice

### 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

- the restrictive-custody correction remained valid
- the existing first-party preserved outputs remained valid
- the current first-party training, review-plan, timer, and smart-device
  owners remained valid

### What changed

The dependent canon now makes the exact non-live role explicit:

- keep `poliva/cubedex` only as restrictive comparison context for the narrow
  smartcube-practice, review/SRS UX, split-timing presentation, and local
  history/stats presentation slice
- keep live implementation ownership with current first-party training/review
  surfaces and the already landed adjacent owner lanes
- do not keep `poliva/cubedex` in the default future clean-room queue unless a
  narrower first-party gap is actually proven later

## Propagation result

### Feature registry

Updated.

The registry now explicitly records the retained restrictive comparison slice
instead of leaving `cubedex` implied only by the live-lane audit and legal
tracker.

### Cross-lane doctrine

No doctrine wording change was needed.

This pass applies the current hierarchy; it does not change the hierarchy
rules.

### 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, preserve note, retained-set contract, feature registry,
and manifest role were sharpened instead.

## Operational answer

Before any future smartcube-practice or review-adjacent implementation packet
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 treat `poliva/cubedex` as the next default clean-room packet row
- only reopen this row if a narrower first-party gap above the current
  training/review/timer/smart-device owner set is actually proven, or if
  restored upstream license evidence materially changes the route
