# HyperTwist Repo Evaluation Reset And Implementation Schedule

Created on `2026-05-11`

## Purpose

This document is the canonical current-state correction for HyperTwist repo provenance, implementation truth, and next-step sequencing.

## 2026-05-12 license-tracking authority boundary

HyperTwist now treats the two licensing files this way:

- `docs/REPO_LICENSE_TRACKING.md` is the canonical repo-row legal and provenance ledger
- `docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md` is the project-level policy and vocabulary file

That means:

- repo-specific author attribution belongs only in `docs/REPO_LICENSE_TRACKING.md`
- repo-specific copyright notice preservation belongs only in `docs/REPO_LICENSE_TRACKING.md`
- Apache `NOTICE` obligations, asset-term caveats, and source-basis exceptions belong only in `docs/REPO_LICENSE_TRACKING.md`
- `LICENSETRACKING.md` may summarize policy and reset rules, but it must not become a second repo-row legal ledger

## 2026-05-12 reconciliation note

This schedule was rechecked on `2026-05-12` against:

- `C:\HyperTwist\docs`
- `C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse`
- `C:\Workspaces\HyperTwist`

The current restart authority addendum is:

- `docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md`

Use that document when a future session needs the cross-location restart authority order, the stale-doc demotions, and the explicit post-`Phase 1R` sequence.

## 2026-05-14 intake, retention, and product-fit doctrine

HyperTwist now treats the following as explicit evaluation doctrine:

- `docs/HYPERTWIST_REPO_INTAKE_RETENTION_AND_PRODUCT_FIT_DOCTRINE_2026-05-14.md`
- `docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md`

Strong rule:

- a bookmarked repo is only intake
- a queued repo is only sequencing
- a source-read repo is only evidence gained
- a retained repo is only a repo that survived evaluation in some posture
- product-fit is a separate judgment from retention
- implementation-authorized is a separate judgment from product-fit
- implemented means landed in first-party product surfaces under explicit implementation authority
- donor strength and legal posture are separate axes
- permissive status does not automatically win a lane
- restrictive or boundary-sensitive status does not automatically lose a lane

Schedule implication:

- do not let bookmark presence, queue position, planning artifacts, or docs metadata masquerade as product intent
- do not treat a source-read repo as automatically approved
- do not treat a retained repo as automatically implementation-authorized
- do not treat a discussed repo as already implemented
- decide technical ownership first and integration route second
- do not let route convenience answer an ownership comparison by itself

Future serious repo evaluations should now explicitly try to state:

- exact source basis read
- licensing posture
- technical donor-strength verdict
- ownership verdict
- explicit displacement or non-displacement rationale
- integration-route verdict
- preserved subsystem ideas
- subordinate or later value
- explicit product-fit verdict
- explicit non-promotion decisions
- rationale for exclusion, demotion, or non-fit
- retention posture
- owner-lane placement
- recommended implementation phase if retained
- recommended realization depth if retained
- acceptance markers if the repo later returns
- explicit statement of what the repo should never be mistaken for

Operational scanning rule:

- routine live or product-surface scanning is no longer the default evaluation step
- assume a repo is not implemented unless explicit implementation authority says otherwise
- only verify current implementation state when the active task specifically depends on that fact

## 2026-05-12 Packet 0R-A status

The first `Phase 0R` packet is now closed as an evaluation packet:

- `Packet 0R-A` result doc:
  - `docs/HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md`

Packet result:

- retained: `7`
- discarded: `0`
- newly proven live: `0`

`Packet 0R-A` is no longer just a retain/schedule memo.

It is now the deep-source integration authority for those seven repos and records:

- exact source surfaces inspected
- all promoted value extracted from those surfaces
- every non-promotion decision and the reason for it
- the cross-repo hierarchy for overlapping domains

Most important scheduling result:

- `Aarav2709/KubeTimr` is the earliest `Packet 0R-A` straight permissive subsystem implementation candidate after `Phase 2R-A`
- `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, and `roice3/MagicTile` are retained-set architecture anchors whose widening remains scheduled for `Phase 6R`
- `vivaansinghvi07/rubix-cube-solver` remains the retained recognition companion and is now also packetized to `Phase 6R`
- `roice3/Magic120Cell` and `roice3/MagicCube5D` remain retained later specialized donors

Mandatory read rule before implementing any `0R-A` repo:

1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md`
2. read `docs/REPO_LICENSE_TRACKING.md`
3. then apply the phase schedule in this document

## 2026-05-12 Packet 0R-B status

The second `Phase 0R` packet is now also closed as an evaluation packet:

- `Packet 0R-B` result doc:
  - `docs/HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md`

That result doc is now the `integration-facing deep-source authority` for all thirty-six `0R-B` repos, not just a permissive-retained summary.

Packet result:

- evaluated rows: `36`
- retained: `36`
- discarded: `0`
- newly proven live: `0`

Most important scheduling result:

- the remaining permissive candidate backlog is now closed as a `Phase 0R` evaluation class
- `Hypercubers/hypercubing.xyz` is ratified as the primary knowledge, curriculum, and community donor
- `apache/echarts` is ratified as the analytics/reporting anchor, with `ecomfe/zrender` and `ecomfe/echarts-gl` explicitly subordinate
- `google/model-viewer`, `mrdoob/three.js`, and the `pmndrs/*` / `@react-spring/*` rows are retained as bounded browser-side support and sidecar lanes, not as runtime-foundation replacements
- `met4citizen/TalkingHead` is retained as the embodied coach and companion donor
- `KhronosGroup/glTF-Sample-Viewer` and `KhronosGroup/glTF-Sample-Renderer` are retained as asset QA and standards-validation sidecars

Combined `Phase 0R` packet status so far:

- packet-evaluated non-live rows: `43` of `65`
- remaining non-live rows still awaiting `Phase 0R` closure: `22`
- next packet: `0R-C`

Mandatory read rule before implementing any `0R-B` repo:

1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md`
2. read `docs/REPO_LICENSE_TRACKING.md`
3. then apply the phase schedule in this document

## 2026-05-12 Packet 0R-C status

The third `Phase 0R` packet is now also closed as an evaluation packet:

- `Packet 0R-C` result doc:
  - `docs/HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md`

That result doc is now the `integration-facing deep-source authority` for all six `0R-C` repos.

Packet result:

- evaluated rows: `6`
- retained: `6`
- discarded: `0`
- newly proven live: `0`

Most important scheduling result:

- the boundary-sensitive candidate backlog is now closed as a `Phase 0R` evaluation class
- `cubing/cubing.js` is ratified as the primary classic-cubing semantic/runtime donor, but only through MPL-aware dependency or adapter seams
- `cutelyaware/magiccube4d` is ratified as the primary legacy `4D` interaction, history, and macro donor beneath the `Hyperspeedcube` anchor
- `google/model-viewer/packages/shared-assets` is retained only as a local fixture and QA pack
- `PostHog/posthog` is retained only as a telemetry, replay-diagnostic, and feature-governance control-plane donor
- `screenpipe/screenpipe` is retained only as a local capture/history/replay, deterministic permissions, and vault sidecar donor
- `remotion-dev/remotion` is retained only as a commercially sensitive media-export and replay-explainer sidecar/reference lane

Combined `Phase 0R` packet status so far:

- packet-evaluated non-live rows: `49` of `65`
- remaining non-live rows still awaiting `Phase 0R` closure: `16`
- next packet: `0R-D`

Mandatory read rule before implementing any `0R-C` repo:

1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md`
2. read `docs/REPO_LICENSE_TRACKING.md`
3. then apply the phase schedule in this document

## 2026-05-13 Packet 0R-D status

The fourth `Phase 0R` packet is now also closed as an evaluation packet:

- `Packet 0R-D` result doc:
  - `docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`

That result doc is now the `governance and Model A authority` packet for all four `0R-D` repos.

Packet result:

- evaluated rows: `4`
- retained: `4`
- discarded: `0`
- newly proven live: `0`

Most important scheduling result:

- the restrictive clean-room candidate backlog is now closed as a `Phase 0R` evaluation class
- `cubing/alg.js` is retained as the focused algorithm-language clean-room lane
- `cubing/twisty.js` is retained as the focused embedded viewer/player clean-room lane
- `HactarCE/2x2x2x2-Scrambler` is retained as the narrow Melinda `2x2x2x2` clean-room lane
- `kash/cubedesk` is retained as the strategic timer/trainer/stats/smart-cube/match product-pattern clean-room lane
- all four rows remain `clean-room only`
- the scrubbed Model A handoffs in `C:\Workspaces\HyperTwist\clean-room-specs\` were refreshed and remain the only Model B implementation inputs for those rows

Combined `Phase 0R` packet status so far:

- packet-evaluated non-live rows: `53` of `65`
- remaining non-live rows still awaiting `Phase 0R` closure: `12`
- next packet: `0R-E`

Mandatory read rule before implementing any `0R-D` repo:

1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`
2. read `docs/REPO_LICENSE_TRACKING.md`
3. read the repo-specific scrubbed Model A handoff in `C:\Workspaces\HyperTwist\clean-room-specs\`
4. then apply the phase schedule in this document

## 2026-05-13 Packet 0R-E status

The fifth `Phase 0R` packet is now also closed as an evaluation packet:

- `Packet 0R-E` result doc:
  - `docs/HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md`

That result doc is now the `reference, benchmark, clean-room-later, and discard authority` packet for all twelve `0R-E` repos.

Packet result:

- evaluated rows: `12`
- retained: `9`
- discarded from the active retained set: `3`
- newly proven live: `0`

Most important scheduling result:

- the reference, benchmark, reserve, and discard backlog is now closed as a `Phase 0R` evaluation class, and the later `2026-05-27` per-row hierarchy and discard notes now control operator truth for the surviving non-live rows
- `cs0x7f/cstimer` remains the primary restrictive oracle for competition-grade timer semantics, rolling stats/`DNF` math, session interchange, scramble-registry breadth, and `GAN`/smart-device behavior; reopen only through a dedicated clean-room timer-pattern handoff if a specific gap is proven
- `brownan/Rubiks-Cube-Solver` remains the primary compact solver oracle and clean-room-later heuristic-table benchmark
- `efrantar/rob-twophase` remains a secondary solver oracle for metric and performance comparison
- `ShellPuppy/RCube` remains a large-`N` algorithm and parity benchmark
- `AviKaufman/Rubix-cube-trainer`, `alinen/cube`, `ambisinister/blindsolve`, and `vwcwong/CubeSim` remain clean-room-later pedagogy, planner, memo, and history benchmarks
- `yakupbilen/drl-rubiks-cube` remains a permissive research benchmark for learned heuristic search, `ADI` state generation, and offline solver experimentation
- `aMonteSl/CodeXR`, `MathewKJ2048/Rubiks-cube-simulator`, and `brianpeiris/RiftSketch` are now discarded from the active retained implementation set

Combined `Phase 0R` packet status:

- packet-evaluated non-live rows: `65` of `65`
- remaining non-live rows still awaiting `Phase 0R` closure: `0`
- next phase: `1R`

## 2026-05-13 Phase 1R status

`Phase 1R` is now also closed.

- `Phase 1R` result doc:
  - `docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md`
- live-lane preservation audit doc:
  - `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`

That result doc is now the retained-set contract and handoff authority for all post-`Phase 0R` routing.

Contract result:

- retained rows total: `68`
- rows with source-backed authority now visible in canonical docs: `71`
- active retained implementation-board rows:
  - `53` non-live rows
  - plus the `6` already landed live rows
- retained benchmark, oracle, or clean-room-later rows outside the active implementation board: `9`
- discarded from the active retained set: `3`

Phase-entry result:

- retained straight-permissive widening may re-enter only through `Phase 3R`, except for the `2R-A` core anchor rows later packetized to `Phase 6R`
- the primary `0R-B` support-plane rows are now split further by `2R-B` into `3R-B` through `3R-F` support packets rather than one flat permissive queue
- the residual `0R-B` rows are now split further by `2R-C` into the retained recognition-comparison adjunct lane, the retained symbolic-to-spatial XR pedagogy lane, and the optional `3R-G` alternative browser comparison lane rather than broad inherited permissive routing
- retained boundary-sensitive rows may re-enter only through `Phase 4R`
- retained restrictive rows may re-enter only through `Phase 5R`
- retained benchmark/oracle rows remain outside the active implementation board unless later explicitly reopened
- discarded rows do not survive into the retained implementation board

Next phase:

- `2R`

## 2026-05-13 Phase 2R-A status

`Phase 2R / Packet 2R-A` is now closed.

- `Phase 2R-A` result doc:
  - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`

Core result:

- `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, `Aarav2709/KubeTimr`, and `roice3/MagicTile` now have explicit first-party ownership and acceptance contracts
- `Aarav2709/KubeTimr` is ratified as the only `2R-A` row that may widen directly in `Phase 3R`
- `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, and `roice3/MagicTile` are contract-frozen now but remain scheduled for `Phase 6R` widening
- the older flattened reading that all core `0R-A` permissive rows simply enter `Phase 3R` is now superseded

Next packet:

- `2R-B`

## 2026-05-13 Phase 2R-B status

`Phase 2R / Packet 2R-B` is now closed.

- `Phase 2R-B` result doc:
  - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`

Support-plane result:

- `Hypercubers/hypercubing.xyz` is now the `3R-B` knowledge and curriculum anchor
- `apache/echarts` with `ecomfe/zrender` and `ecomfe/echarts-gl` is now the `3R-C` analytics and reporting lane
- `google/model-viewer` with its package rows plus `KhronosGroup/glTF-Sample-Viewer` and `KhronosGroup/glTF-Sample-Renderer` is now the `3R-D` browser presentation, editor, and QA lane
- `met4citizen/TalkingHead` is now the `3R-E` embodied companion lane
- `mrdoob/three.js`, `pmndrs/react-three-fiber`, `pmndrs/xr`, `pmndrs/uikit`, `pmndrs/postprocessing`, and the remaining browser helper stack are now the `3R-F` browser `3D` / XR support lane
- the `2026-05-27` analytics and browser-viewer subordinate-stack clarification supersedes stale generic `phase0r_permissive_eval_then_implement` row-source wording for `ecomfe/zrender`, `ecomfe/echarts-gl`, the `google/model-viewer` package rows, and the `KhronosGroup/glTF-Sample-*` sidecars; no default widening packet is open for those subordinate rows today
- the older flattened reading that all `0R-B` permissive rows were equal `Phase 3R` donors is now superseded
- the remaining `0R-B` rows `cahidenes/rubiks-cube-solver`, `tentone/rubix-solver`, `NuiLab/code-vr`, `pissang/claygl`, and `pissang/clay-viewer` are still retained but wait for `2R-C`

Next packet:

- `2R-C`

## 2026-05-13 Phase 2R-C status

`Phase 2R / Packet 2R-C` is now closed.

- `Phase 2R-C` result doc:
  - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`

Residual-lane result:

- `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` are now the retained recognition-comparison adjunct lane behind the landed recognition anchors, with no default widening packet currently open
- `NuiLab/code-vr` is now the retained symbolic-to-spatial XR pedagogy experiment lane, with no default widening packet currently open
- `pissang/claygl` and `pissang/clay-viewer` are now the retained optional `3R-G` alternative browser comparison lane beneath the primary retained browser stack
- all retained `0R-B` rows now have explicit ownership and acceptance packetization
- `Phase 2R` is now fully closed for the retained permissive set
- the older inherited routing for the final five `0R-B` rows is now superseded

Next packet:

- `3R-A`

## 2026-05-13 Phase 3R-A status

`Phase 3R / Packet 3R-A` is now closed.

- `Phase 3R-A` result doc:
  - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `Aarav2709/KubeTimr` is now landed as a first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane
- `Aarav2709/KubeTimr` is now `implemented_live_permissive`
- current verified live rows are now:
  - `7` total
  - `6` permissive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `52`
- `Phase 3R` is now open and no longer hypothetical

Validation result:

- `UnrealHyperTwistEditor` build succeeded for the landed widening packet

Next packet:

- `3R-B`

## 2026-05-13 Phase 3R-B status

`Phase 3R / Packet 3R-B` is now closed.

- `Phase 3R-B` result doc:
  - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `Hypercubers/hypercubing.xyz` is now landed as a first-party taxonomy, notation, progression, software-reference, and leaderboard-contract lane
- `Hypercubers/hypercubing.xyz` is now `implemented_live_permissive`
- current verified live rows are now:
  - `8` total
  - `7` permissive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `51`
- the `Hypercubers/hypercubing.xyz` knowledge and curriculum anchor is no longer a queued `Phase 3R` candidate; it is a landed live lane

Validation result:

- `UnrealHyperTwistEditor` build succeeded for the landed widening packet

Next packet:

- `3R-C`

## 2026-05-13 Phase 3R-C status

`Phase 3R / Packet 3R-C` is now closed.

- `Phase 3R-C` result doc:
  - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `apache/echarts` is now landed as a first-party analytics, reporting, export, and progress-visualization lane
- `apache/echarts` is now `implemented_live_permissive`
- `ecomfe/zrender` and `ecomfe/echarts-gl` remain retained subordinate lanes beneath the landed `apache/echarts` owner and are not separately live
- current verified live rows are now:
  - `9` total
  - `8` permissive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `50`
- the `apache/echarts` analytics and reporting anchor is no longer a queued `Phase 3R` candidate; it is a landed live lane

Validation result:

- `UnrealHyperTwistEditor` build succeeded for the landed widening packet

Next packet:

- `3R-D`

## 2026-05-13 Phase 3R-D status

`Phase 3R / Packet 3R-D` is now closed.

- `Phase 3R-D` result doc:
  - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `google/model-viewer` is now landed as a first-party browser presentation, compact editor, and standards-aware asset-QA lane
- `google/model-viewer` is now `implemented_live_permissive`
- `google/model-viewer/packages/space-opera`, `google/model-viewer/packages/render-fidelity-tools`, `google/model-viewer/packages/model-viewer-effects`, `google/model-viewer/packages/modelviewer.dev`, `KhronosGroup/glTF-Sample-Viewer`, and `KhronosGroup/glTF-Sample-Renderer` remain retained subordinate lanes beneath the landed `google/model-viewer` owner and are not separately live
- `google/model-viewer/packages/shared-assets` remains boundary-sensitive only and is not widened by this packet
- current verified live rows are now:
  - `10` total
  - `9` permissive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `49`
- the `google/model-viewer` browser presentation and compact editor anchor is no longer a queued `Phase 3R` candidate; it is a landed live lane

Validation result:

- `UnrealHyperTwistEditor` build succeeded for the landed widening packet

Next packet:

- `3R-E`

`Phase 3R / Packet 3R-E` is now closed.

- `Phase 3R-E` result doc:
  - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `met4citizen/TalkingHead` is now landed as a first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane
- `met4citizen/TalkingHead` is now `implemented_live_permissive`
- sample avatars, media, and external TTS or JWT-backed service flows remain boundary surfaces and are not silently widened by this packet
- current verified live rows are now:
  - `11` total
  - `10` permissive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `48`
- the `met4citizen/TalkingHead` embodied companion anchor is no longer a queued `Phase 3R` candidate; it is a landed live lane

Validation result:

- `UnrealHyperTwistEditor` build succeeded for the landed widening packet

Next packet:

- `3R-F`

## 2026-05-13 Phase 3R-F status

`Phase 3R / Packet 3R-F` is now closed.

- `Phase 3R-F` result doc:
  - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `mrdoob/three.js` is now landed as a first-party browser `3D` substrate lane
- `pmndrs/react-three-fiber` is now landed as a first-party React-side browser renderer and event-bridge lane
- `pmndrs/xr` is now landed as a first-party browser XR session and immersive interaction lane
- all three rows are now `implemented_live_permissive`
- `pmndrs/uikit`, `pmndrs/postprocessing`, `pmndrs/react-postprocessing`, `pmndrs/drei`, `pmndrs/three-stdlib`, `pmndrs/maath`, `pmndrs/zustand`, `pmndrs/leva`, `pmndrs/use-gesture`, `pmndrs/react-spring`, and the `@react-spring/*` packages remain retained subordinate support rows beneath the landed owner trio and are not separately live
- the `2026-05-27` browser-support subordinate-stack clarification supersedes any stale generic `phase0r_permissive_eval_then_implement` row-source wording for those retained support rows; no default widening packet is open for them today
- current verified live rows are now:
  - `14` total
  - `13` permissive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `45`
- the primary retained browser spatial support stack is no longer a queued `Phase 3R` candidate; it is a landed live owner stack

Validation result:

- `UnrealHyperTwistEditor` build succeeded for the landed widening packet

Next packet:

- `4R-B`

## 2026-05-13 Phase 4R-A status

`Phase 4R / Packet 4R-A` is now closed.

- `Phase 4R-A` result doc:
  - `docs/HYPERTWIST_PHASE_4R_PACKET_4R_A_CUBING_JS_ADAPTER_IMPLEMENTATION_2026-05-13.md`

Implementation result:

- `cubing/cubing.js` is now landed as a first-party classic-cubing semantic, geometry, viewer-adapter, device-adapter, and search-contract lane
- `cubing/cubing.js` is now `implemented_live_boundary_sensitive`
- no upstream `cubing.js` source-file modifications landed in this packet
- `cutelyaware/magiccube4d` is now landed as a first-party legacy `4D` history, macro, topology-reference, interaction, and attribution-boundary lane
- `cutelyaware/magiccube4d` is now `implemented_live_boundary_sensitive`
- no upstream `magiccube4d` source-file modifications landed in this packet
- current verified live rows are now:
  - `16` total
  - `13` permissive
  - `2` boundary-sensitive
  - `1` restrictive clean-room
- active non-live implementation-board rows are now `43`
- the classic-cubing `MPL`-aware adapter lane and the attributed legacy `4D` lane are no longer queued `Phase 4R` candidates; they are landed live lanes

Validation result:

- `git diff --check` passed apart from CRLF conversion warnings
- JSON validation passed for the updated materialized-catalog files and workspace manifest
- Unreal build succeeded for the landed code-bearing packet

Mandatory read rule before implementing, benchmarking against, or clean-rooming any `0R-E` repo:

1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md`
2. read `docs/REPO_LICENSE_TRACKING.md`
3. then apply the phase schedule in this document

Use it when a future model, operator, or reviewer needs one unambiguous answer to all of the following:

- what is already implemented right now
- which of those implemented lanes are permissive versus restrictive
- which restrictive lane is the one properly clean-roomed and already implemented
- which repos are still only selected, queued, reserve, or future
- whether HyperTwist should restart deep repo evaluation before widening implementation again
- how the remaining repos should be scheduled

This document does not replace the repo-row CSVs.

It corrects how they should be interpreted.

## Authoritative current truth

Current curated HyperTwist shallow-eval set:

- `71` repos

Current verified live implementation state in checked `UnrealHyperTwist` source and materialized training surfaces:

- `29` repos are implemented/live within the original `71`-row shallow-eval set
- `18` of those are permissive `MIT` or `Apache-2.0` lanes
- `6` of those are boundary-sensitive lanes
- `5` of those are restrictive repos that were properly clean-roomed and then implemented

Current repo-row reset counts within the original `71`-row shallow-eval set as
of `2026-05-28`:

- `implemented_live_permissive`: `18`
- `implemented_live_boundary_sensitive`: `6`
- `implemented_live_clean_room_verified`: `5`
- `selected_not_live_permissive_candidate`: `29`
- `selected_not_live_boundary_sensitive`: `0`
- `selected_not_live_clean_room_candidate`: `0`
- `not_live_reference_or_discard_candidate`: `13`

Outside that original `71`-row set, the broader current repo-row source-truth
pack also has four later landed speech rows:

- `ggml-org/whisper.cpp`
- `rhasspy/piper`
- `SYSTRAN/faster-whisper`
- `coqui-ai/TTS`

That broader source-truth pack therefore currently sits at `33` live rows
overall: `21` permissive, `7` boundary-sensitive, and `5` restrictive
clean-room lanes.

### The twenty-nine currently implemented/live repos within the `71`-row shallow-eval set

Permissive `MIT` or `Apache-2.0` lanes already implemented/live:

- `Aarav2709/KubeTimr`
- `abunickabhi/5style-Trainer`
- `apache/echarts`
- `google/model-viewer`
- `HactarCE/Hyperspeedcube`
- `Hypercubers/hypercubing.xyz`
- `kkoomen/qbr`
- `Lykos/cube_trainer`
- `met4citizen/TalkingHead`
- `mrdoob/three.js`
- `pmndrs/react-three-fiber`
- `pmndrs/xr`
- `roice3/Magic120Cell`
- `roice3/MagicCube5D`
- `roice3/MagicTile`
- `tao-yu/Alg-Trainer`
- `newyork-anthonyng/rubiks-cross-trainer`
- `vivaansinghvi07/rubix-cube-solver`

Restrictive lanes already properly clean-roomed and implemented/live:

- `onionhoney/roux-trainers`
- `cubing/alg.js`
- `cubing/twisty.js`
- `HactarCE/2x2x2x2-Scrambler`
- `kash/cubedesk`

Boundary-sensitive lanes already implemented/live:

- `cubing/cubing.js`
- `cutelyaware/magiccube4d`
- `google/model-viewer/packages/shared-assets`
- `PostHog/posthog`
- `screenpipe/screenpipe`
- `remotion-dev/remotion`

### What this means

- HyperTwist does **not** currently have dozens of donor repos already implemented in owned Unreal surfaces.
- HyperTwist does **not** currently show live Unreal evidence for `cstimer`.
- HyperTwist **does** now show live Unreal evidence for `Hyperspeedcube`, `qbr`, `MagicTile`, `MagicCube5D`, and `Magic120Cell` through later landed `Phase 6R` packets.
- HyperTwist also has four later landed speech rows in the broader current
  source-truth pack outside the original `71`-row shallow-eval set:
  `ggml-org/whisper.cpp`, `rhasspy/piper`, `SYSTRAN/faster-whisper`, and
  `coqui-ai/TTS`.
- The previous confusion came from mixing:
  - docs-state classifications such as `integrate`, `repurpose`, `donor bench`, and `locked strategic donor`
  - with actual live implementation evidence

Those are not the same thing.

## Working definitions

### Landed / verified live

Use this only when there is current first-party Unreal evidence such as:

- exact source attribution in owned source
- materialized content bundles
- first-party runtime/library integration that is directly traceable

### Selected / queued

Use this when the current docs still actively retain the repo, but the current checked Unreal surfaces do not yet prove it is live.

### Future / reserve

Use this when the repo remains retained for later evaluation, benchmark, oracle, reference, or possible discard.

### Properly clean-roomed and implemented

Use this only when:

- the restrictive repo has an explicit Model A / Model B governance chain
- the implementation lane is accepted as clean-room compliant
- the resulting first-party output is already landed/live

At the moment, five HyperTwist repos should be described this way:

- `onionhoney/roux-trainers`
- `cubing/alg.js`
- `cubing/twisty.js`
- `HactarCE/2x2x2x2-Scrambler`
- `kash/cubedesk`

## Immediate governance correction

HyperTwist should now proceed from the following rule:

- preserve the twenty-nine live lanes inside the original `71`-row shallow-eval board
- do not reopen the five landed restrictive clean-room lanes as if they were unresolved accidental donor imports
- do not treat the remaining `42` current non-live rows as already implemented
- keep `Phase 0R`, `Phase 1R`, and `Phase 2R` closed as completed packet classes
- continue later-phase widening from the closed packet sequence with no default new `Phase 5R-A` opening; use the landed restrictive per-lane authority for `onionhoney/roux-trainers`, `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`, and keep `Phase 3R-G` deferred unless a real browser comparison gap appears

In practical terms:

- no, do **not** mass-revert the twenty-nine landed lanes
- no, do **not** pretend the remaining `42` current non-live rows are already implemented
- yes, preserve the landed `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, `met4citizen/TalkingHead`, `mrdoob/three.js`, `pmndrs/react-three-fiber`, `pmndrs/xr`, `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, `roice3/MagicTile`, `roice3/Magic120Cell`, `roice3/MagicCube5D`, `cubing/cubing.js`, `cutelyaware/magiccube4d`, `google/model-viewer/packages/shared-assets`, `PostHog/posthog`, `screenpipe/screenpipe`, and `remotion-dev/remotion` lanes as normal first-party enhancement surfaces within their packet-specific legal boundaries
- yes, widen the next retained lane only through its closed packet stack and packet-specific legal boundary

## Phase reset sequence

### Phase `0R` — repo deep source integration evaluation reset

Goal:

- repo-by-repo deep source evaluation for the not-yet-live rows retained after the live-state reset
- after `0R-A`, `0R-B`, `0R-C`, and `0R-D`, `12` rows still remain to be closed

Required method from this point forward:

- read the source directly, not only the ledgers
- extract all meaningful value
- omit only when the surface is an inferior duplicate, superseded by a stronger retained donor, off topic, or host-shell glue with no durable architecture value
- record the rationale every time something is not promoted

Required output for every remaining repo:

- final license posture
- keep / promote / demote / benchmark / discard decision
- implementation lane:
  - direct permissive implementation
  - adapter/dependency or bounded sidecar
  - Model A / Model B clean-room
  - benchmark/oracle only
  - discard
- evidence links
- scheduling wave
- required notices / compliance boundary
- whether the repo survives into later implementation planning at all

### Phase `1R` — contract and handoff overhaul

Goal:

- rewrite the implementation-facing contract and handoff layer so it reflects only:
  - the six already landed lanes
  - the retained repos that survive `Phase 0R`

Required output:

- updated repo-row CSVs
- updated license tracker with the document boundary preserved:
  - `docs/REPO_LICENSE_TRACKING.md` for repo-row legal detail
  - `docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md` for policy and vocabulary only
- updated roadmap and handoff docs
- updated clean-room inventory
- updated keep/discard board
- refreshed Model A dossiers for retained restrictive lanes
- refreshed Model B implementation allowlist/boundary docs

### Later-phase re-entry rule

Do not treat `Phase 2`, `Phase 3`, or `Phase 4` widening as normal again until:

- `Phase 0R` is closed for the remaining `65`
- `Phase 1R` has refreshed the canonical donor/clean-room/benchmark boundary

Already-landed first-party work can remain.

New widening should wait.

## Subsequential restart phases

After `Phase 0R` and `Phase 1R`, the restart sequence is:

### Phase `2R` — retained-set ratification and packet design

- convert the post-`Phase 0R` retained rows into an implementation-ready backlog
- define ownership boundaries, packet classes, acceptance criteria, and subsystem entry points

### Phase `3R` — permissive direct-implementation waves

- execute the retained straight-permissive lanes first
- favor rows that can become first-party capability quickly without clean-room overhead

### Phase `4R` — boundary-sensitive adapter and sidecar waves

- close the mixed-term, attribution-heavy, enterprise-slice, and commercial-boundary rows
- prefer adapter, dependency, or bounded sidecar use where the retained posture says that is the cleanest path

### Phase `5R` — restrictive clean-room waves

- refresh Model A / Model B dossiers for the retained restrictive rows
- implement only from the refreshed clean-room chain

### Phase `6R` — retained-set capability widening

- widen recognition, simulation, hyper, XR, and support-plane work only from the retained evaluated set

### Phase `7R` — benchmark, discard, and release-hardening closure

- close oracle/reference/discard decisions
- tie benchmark rows to validation instead of leaving them as ambiguous backlog

## Scheduling the remaining repos

The right schedule now is not one giant undifferentiated queue.

It should be broken into waves by integration posture.

### Wave `0` — landed truth and parity

Preserve, document, and keep visible:

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

Deliverables:

- keep all six explicitly marked as landed/live in docs
- keep `onionhoney/roux-trainers` explicitly marked as the only verified restrictive clean-room lane already implemented
- ensure future docs do not collapse `selected` into `implemented`

### Wave `1` — permissive core-evaluation and straight implementation candidates

Deep-evaluate first because these are the most likely remaining straight implementation or adapter targets if retained:

- `Aarav2709/KubeTimr`
- `HactarCE/Hyperspeedcube`
- `kkoomen/qbr`
- `vivaansinghvi07/rubix-cube-solver`
- `Hypercubers/hypercubing.xyz`
- `roice3/Magic120Cell`
- `roice3/MagicCube5D`
- `roice3/MagicTile`

Recognition-comparison exception:

- `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` are no longer in the straight implementation subset; they remain retained comparison adjuncts only unless a later first-party owner gap is proven

Expected outcome:

- most of these will end either in:
  - direct permissive implementation
  - bounded adapter/dependency use
  - or discard if deep evaluation shows weak real value

Current packet result:

- `Packet 0R-A` is now closed for:
  - `Aarav2709/KubeTimr`
  - `HactarCE/Hyperspeedcube`
  - `kkoomen/qbr`
  - `vivaansinghvi07/rubix-cube-solver`
  - `roice3/MagicTile`
  - `roice3/Magic120Cell`
  - `roice3/MagicCube5D`
- `Packet 0R-B` is now closed for the remaining permissive candidate backlog

### Wave `2` — permissive browser, analytics, XR, and support stack evaluation

Deep-evaluate next:

- `apache/echarts`
- `ecomfe/echarts-gl`
- `ecomfe/zrender`
- `google/model-viewer`
- `google/model-viewer/packages/model-viewer-effects`
- `google/model-viewer/packages/modelviewer.dev`
- `google/model-viewer/packages/render-fidelity-tools`
- `google/model-viewer/packages/space-opera`
- `KhronosGroup/glTF-Sample-Renderer`
- `KhronosGroup/glTF-Sample-Viewer`
- `mrdoob/three.js`
- `pmndrs/postprocessing`
- `pmndrs/react-postprocessing`
- `pmndrs/react-three-fiber`
- `pmndrs/drei`
- `pmndrs/react-spring`
- `@react-spring/core`
- `@react-spring/shared`
- `@react-spring/types`
- `@react-spring/parallax`
- `@react-spring/rafz`
- `@react-spring/animated`
- `pmndrs/three-stdlib`
- `pmndrs/maath`
- `pmndrs/uikit`
- `pmndrs/xr`
- `pmndrs/zustand`
- `pmndrs/use-gesture`

Current packet result:

- `Packet 0R-B` is now closed for:
  - `cahidenes/rubiks-cube-solver`
  - `tentone/rubix-solver`
  - `Hypercubers/hypercubing.xyz`
  - `met4citizen/TalkingHead`
  - `NuiLab/code-vr`
  - `apache/echarts`
  - `ecomfe/zrender`
  - `ecomfe/echarts-gl`
  - `KhronosGroup/glTF-Sample-Viewer`
  - `KhronosGroup/glTF-Sample-Renderer`
  - `google/model-viewer`
  - `google/model-viewer/packages/model-viewer-effects`
  - `google/model-viewer/packages/modelviewer.dev`
  - `google/model-viewer/packages/render-fidelity-tools`
  - `google/model-viewer/packages/space-opera`
  - `mrdoob/three.js`
  - `pissang/claygl`
  - `pissang/clay-viewer`
  - `pmndrs/postprocessing`
  - `pmndrs/react-postprocessing`
  - `pmndrs/react-three-fiber`
  - `pmndrs/drei`
  - `pmndrs/xr`
  - `pmndrs/uikit`
  - `pmndrs/three-stdlib`
  - `pmndrs/maath`
  - `pmndrs/zustand`
  - `pmndrs/leva`
  - `pmndrs/use-gesture`
  - `pmndrs/react-spring`
  - `@react-spring/core`
  - `@react-spring/shared`
  - `@react-spring/types`
  - `@react-spring/parallax`
  - `@react-spring/rafz`
  - `@react-spring/animated`
- none of those rows are newly proven live in checked Unreal surfaces

Expected outcome:

- clean dependency or adapter boundaries for the survivors
- discard of any rows whose real leverage is weaker than the current docs suggest

### Wave `3` — boundary-sensitive but potentially usable rows

These are not normal straight-permissive rows.

They need deeper evaluation plus boundary discipline before any implementation scheduling:

- `cubing/cubing.js`
- `cutelyaware/magiccube4d`
- `PostHog/posthog`
- `screenpipe/screenpipe`
- `remotion-dev/remotion`
- `google/model-viewer/packages/shared-assets`

Expected outcome:

- adapter/dependency or bounded sidecar use
- explicit notice / publication / subtree restrictions where needed
- discard where the boundary cost exceeds strategic value

Current packet result:

- `Packet 0R-C` is now closed for:
  - `cubing/cubing.js`
  - `cutelyaware/magiccube4d`
  - `google/model-viewer/packages/shared-assets`
  - `PostHog/posthog`
  - `remotion-dev/remotion`
  - `screenpipe/screenpipe`
- none of those rows are newly proven live in checked Unreal surfaces
- the actual result was `retained with sharply bounded use`, not `broad donor promotion`
- next clean packet is `0R-D`

### Wave `4` — restrictive clean-room candidates

These are the restrictive rows still retained for possible implementation after proper deep evaluation and refreshed Model A / Model B handling:

- `cubing/alg.js`
- `cubing/twisty.js`
- `HactarCE/2x2x2x2-Scrambler`
- `kash/cubedesk`

Expected outcome:

- either:
  - keep and refresh Model A dossier, then schedule Model B implementation
  - or demote to benchmark/reference/discard

Important note:

- `onionhoney/roux-trainers` is **not** in this pending set.
- it is already the landed clean-room restrictive lane.

Current packet result:

- `Packet 0R-D` is now closed for:
  - `cubing/alg.js`
  - `cubing/twisty.js`
  - `HactarCE/2x2x2x2-Scrambler`
  - `kash/cubedesk`
- none of those rows are newly proven live in checked Unreal surfaces
- the actual result was `retained clean-room only with refreshed Model A dossiers`, not `direct donor promotion`
- next clean packet is `0R-E`

### Wave `5` — benchmark, reserve, and discard candidates

These were deep-evaluated specifically to answer whether they remain useful at all:

- `cs0x7f/cstimer`
- `efrantar/rob-twophase`
- `aMonteSl/CodeXR`
- `brownan/Rubiks-Cube-Solver`
- `MathewKJ2048/Rubiks-cube-simulator`
- `ShellPuppy/RCube`
- `vwcwong/CubeSim`
- `AviKaufman/Rubix-cube-trainer`
- `alinen/cube`
- `ambisinister/blindsolve`
- `brianpeiris/RiftSketch`
- `yakupbilen/drl-rubiks-cube`

Expected outcome:

- benchmark-only retention
- clean-room-later reservation
- or discard from the active retained set

Current packet result:

- `Packet 0R-E` is now closed for all twelve rows in this wave
- none of those rows are newly proven live in checked Unreal surfaces
- the actual result was:
  - `9` retained benchmark, oracle, or clean-room-later rows
  - `3` discarded active-set rows
- `Phase 0R` is now fully closed
- next clean move is `Phase 1R`

## What should happen to later phases

### `Phase 2`

Rebuild it from the retained set after `Phase 0R` and `Phase 1R`.

It should stop implying that a broad donor universe is already implementation-ready.

### `Phase 3`

Keep already-landed first-party functionality.

Do not widen new donor-driven surfaces until the retained repo board is rebuilt.

### `Phase 4`

Treat current `Phase 4` work as real first-party product implementation, but not as proof that the remaining donor portfolio was fully adjudicated.

No new widening should assume old donor certainty.

## How to proceed further

Yes:

- start now with `Phase 0R` repo deep source integration evaluation

Then:

- complete `Phase 1R` contract and handoff overhaul

Only after that:

- re-engage the broader later-phase implementation lanes

The clean practical sequence is:

1. preserve the twenty-nine landed lanes
2. make the current truth explicit everywhere
3. deep-evaluate the remaining `42`
4. discard what should not survive
5. re-schedule what remains by permissive, boundary-sensitive, clean-room, and benchmark lanes
6. resume later-phase widening from that corrected retained set

Current status:

- steps `1` through `6` are now complete through `Phase 1R`
- `Phase 2R-A` is now also complete
- `Phase 2R-B` is now also complete
- `Phase 2R-C` is now also complete
- `Phase 3R-A` is now also complete
- `Phase 3R-B` is now also complete
- `Phase 3R-C` is now also complete
- `Phase 3R-D` is now also complete
- `Phase 3R-E` is now also complete
- `Phase 3R-F` is now also complete
- `Phase 4R-A` is now also complete
- `Phase 4R-B` is now also complete
- `Phase 4R-C` is now also complete
- `Phase 4R-D` is now also complete
- `Phase 4R-E` is now also complete
- `Phase 4R-F` is now also complete
- there is no remaining default `Phase 5R-A` opening because later restrictive clean-room truth already landed `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`; keep the optional `Phase 3R-G` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap
- the `2026-05-27` restrictive clean-room live-state reconciliation also governs the `v6.3` source-pack backfill for those four later-landed rows; they should carry `implemented_live_clean_room_verified` plus `landed_clean_room_preserve`, not the old clean-room entry lane

## Companion docs

Read together with:

- `docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
- `docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_4R_PACKET_4R_A_CUBING_JS_ADAPTER_IMPLEMENTATION_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_4R_PACKET_4R_B_MAGICCUBE4D_ADAPTER_IMPLEMENTATION_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_4R_PACKET_4R_C_SHARED_ASSETS_ALLOWLIST_IMPLEMENTATION_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_4R_PACKET_4R_D_POSTHOG_CONTROL_PLANE_IMPLEMENTATION_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_4R_PACKET_4R_E_SCREENPIPE_CAPTURE_HISTORY_IMPLEMENTATION_2026-05-13.md`
- `docs/HYPERTWIST_PHASE_4R_PACKET_4R_F_REMOTION_MEDIA_EXPORT_IMPLEMENTATION_2026-05-13.md`
- `docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md`
- `docs/REPO_LICENSE_TRACKING.md`
- `docs/HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md`
- `docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md`
- `docs/MODEL_B_SOURCE_ACCESS_BOUNDARY.md`
