# HyperTwist Later Permissive Live State Reconciliation - 2026-05-27

## Status

This document is the board-scoped reconciliation note for the later permissive
live-state correction inside HyperTwist's original `71`-row shallow-eval set.

It answers one narrow question:

- does the current `71`-row board still correctly describe six later `Phase 6R`
  permissive rows as future candidates and `poliva/cubedex` as a landed live
  permissive lane, or have later implementation and later hierarchy work
  reversed that split

Result:

- six later permissive `Phase 6R` rows are already landed inside the
  `71`-row board and must now be treated as preserve-or-later-widen owner
  lanes
- `poliva/cubedex` is no longer a landed permissive lane and now survives only
  as restrictive comparison context for a narrower smartcube
  practice/review/SRS slice
- no product-code reopening is required
- yes selective authority backfill is required

## Source basis

- `C:\HyperTwist\docs\HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md`
- `C:\HyperTwist\docs\HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\ROADMAP.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md`
- `C:\HyperTwist\docs\HYPERTWIST_SMARTCUBE_PRACTICE_REVIEW_AND_SRS_HIERARCHY_RECONCILIATION_2026-05-27.md`

## Board-scoped live correction

Inside the original `71`-row shallow-eval board, later current-live permissive
lanes now also include:

- `HactarCE/Hyperspeedcube`
- `kkoomen/qbr`
- `vivaansinghvi07/rubix-cube-solver`
- `roice3/MagicTile`
- `roice3/Magic120Cell`
- `roice3/MagicCube5D`

At the same time:

- `poliva/cubedex` is no longer a landed permissive lane
- `poliva/cubedex` is no longer the default next clean-room queue row
- `poliva/cubedex` remains useful only as restrictive comparison context for
  smartcube-aware practice-shell behavior, review/SRS UX, recognition-versus-
  execution timing presentation, and local stats/history comparison

Current board-scoped counts are therefore:

- `71` total curated repo rows
- `29` current live repo rows
- `18` live permissive rows
- `6` live boundary-sensitive rows
- `5` live restrictive clean-room rows
- `42` current non-live rows

This note is intentionally board-scoped.

Broader later product live truth is higher once the later speech/provider rows
that live outside this original `71`-row shallow-eval board are included. That
broader truth stays with `ROADMAP.md`, `FEATURE_REGISTRY.md`, and the later
speech/provider packet stack rather than with this board.

## Why the old board split is now stale

Later current authority already says:

- `HactarCE/Hyperspeedcube` is landed through bounded `Phase 6R-A/K/L/M/N` and
  is closed for the currently justified retained families
- `kkoomen/qbr` is landed through bounded `Phase 6R-B/O` and remains partially
  incorporated rather than non-live
- `vivaansinghvi07/rubix-cube-solver` is landed through bounded
  `Phase 6R-C/P/Q` and remains partially incorporated rather than non-live
- `roice3/MagicTile` is landed through bounded `Phase 6R-D/T` and remains
  partially incorporated rather than non-live
- `roice3/Magic120Cell` is landed through bounded `Phase 6R-I` and remains
  partially incorporated rather than non-live
- `roice3/MagicCube5D` is landed through bounded `Phase 6R-J` and remains
  partially incorporated rather than non-live
- `poliva/cubedex` should no longer be treated as a landed permissive lane and
  should no longer be treated as the next default clean-room queue row

That means the old board split of:

- `24` live rows
- `13` live permissive rows
- `35` non-live permissive candidate rows
- `12` reference/benchmark/discard rows

is now historical only.

The corrected board split is:

- `29` live rows
- `18` live permissive rows
- `29` non-live permissive candidate rows
- `13` reference/benchmark/discard rows

## Current preserve-and-widen rule

For the six later permissive rows:

- do not route future work from the old candidate queue wording
- do not reopen `Phase 0R`, `Phase 1R`, or `Phase 2R` as if these rows were
  still awaiting first implementation
- start future preservation or later widening from `ROADMAP.md`,
  `FEATURE_REGISTRY.md`, `REPO_LICENSE_TRACKING.md`, and the repo-specific
  landed `Phase 6R-*` packets

For `poliva/cubedex`:

- do not treat it as a live permissive lane
- do not treat it as the default next clean-room packet row
- start any later comparison or reopening decision from current first-party
  training/review/timer/smart-device owner surfaces,
  `REPO_LICENSE_TRACKING.md`, and the `2026-05-27` smartcube
  practice/review/SRS hierarchy reconciliation note

## Final call

The correct current board-scoped operator posture is:

- preserve six later landed permissive `Phase 6R` rows as live owner lanes
- preserve `poliva/cubedex` only as restrictive comparison context
- keep the original `24`-row board split as historical only
- do not reopen product code from this pass