diff --git a/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md b/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md
index df1456b..987a92b 100644
--- a/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md
+++ b/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md
@@ -547,7 +547,7 @@ Result:
 - `google/model-viewer` plus `KhronosGroup/glTF-Sample-Viewer` are now the landed browser presentation/editor and standards-QA `3R-D` lane
 - `met4citizen/TalkingHead` is now the landed embodied companion `3R-E` lane
 - `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` are now the landed browser spatial owner trio through `3R-F`
-- `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` now form the retained `6R-E` recognition-comparison adjunct lane
+- `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` now form the retained recognition-comparison adjunct lane, not a currently open `Phase 6R-*` packet route
 - `NuiLab/code-vr` now forms the retained `6R-F` symbolic-to-spatial XR pedagogy experiment lane
 - `pissang/claygl` and `pissang/clay-viewer` now form the retained optional `3R-G` alternative browser comparison lane
 - `cubing/cubing.js` is now the fifteenth live row overall and one live boundary-sensitive lane through the closed `Phase 4R-A` classic-cubing adapter packet
diff --git a/docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md b/docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
index efb5733..cdcc435 100644
--- a/docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
+++ b/docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md
@@ -105,13 +105,24 @@ Document responsibilities are strict:
 `2R-C` freezes the following routing:
 
 - `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` are now a retained recognition-comparison adjunct lane, not a primary recognition lane
-- those two rows may widen only later through `Phase 6R-E`, after the retained recognition anchors are already fixed
+- those two rows may widen only later if a narrower first-party recognition-comparison owner gap survives the landed `qbr`, `rubix-cube-solver`, and correction-stack seams
 - `NuiLab/code-vr` is now a retained symbolic-to-spatial XR pedagogy experiment lane only
 - `NuiLab/code-vr` may widen only later through `Phase 6R-F`, after the retained knowledge and XR support lanes already exist
 - `pissang/claygl` and `pissang/clay-viewer` are now an optional alternative browser comparison lane beneath the retained browser stack
 - those two rows may widen only later through `Phase 3R-G`, and only if the primary retained browser stack leaves a real gap
 - none of these rows are newly proven live in checked Unreal surfaces
 
+## 2026-05-27 recognition-adjunct clarification
+
+Later live product work now uses `Phase 6R-E` for the landed `ggml-org/whisper.cpp` speech transcript session packet.
+
+Therefore, for the two retained recognition-comparison adjunct rows only:
+
+- the older historical `6R-E` widening label from this packet is superseded
+- current canon should use `retained recognition-comparison adjunct lane` wording instead
+- no default widening packet is currently open
+- any later widening must begin from a fresh first-party owner-gap proof note rather than from the stale packet label alone
+
 Important correction:
 
 - all retained `0R-B` rows now have explicit ownership and acceptance packetization
@@ -124,8 +135,8 @@ Implementation entry result:
 
 | Repo or lane | Ownership class | Earliest widening phase | Packet entry |
 | --- | --- | --- | --- |
-| `cahidenes/rubiks-cube-solver` | face-placement and cube-string comparison adjunct | `Phase 6R` | `6R-E` |
-| `tentone/rubix-solver` | native capture and quad/color comparison adjunct | `Phase 6R` | `6R-E` |
+| `cahidenes/rubiks-cube-solver` | face-placement and cube-string comparison adjunct | only if a later first-party gap is proven | no default packet open |
+| `tentone/rubix-solver` | native capture and quad/color comparison adjunct | only if a later first-party gap is proven | no default packet open |
 | `NuiLab/code-vr` | symbolic-to-spatial XR pedagogy experiment donor | `Phase 6R` | `6R-F` |
 | `pissang/claygl` | alternative browser `3D` comparison substrate | `Phase 3R` only if a real gap remains | `3R-G` |
 | `pissang/clay-viewer` | alternative browser viewer/editor comparison sidecar | `Phase 3R` only if a real gap remains | `3R-G` |
@@ -165,7 +176,7 @@ Acceptance markers before widening may start:
 
 Earliest widening route:
 
-- `Phase 6R / Packet 6R-E`
+- no default packet is currently open; reopen only if a narrower face-placement, cube-string, or divergence-reporting gap is later proven above the landed recognition stack
 
 ### `tentone/rubix-solver`
 
@@ -190,7 +201,7 @@ Acceptance markers before widening may start:
 
 Earliest widening route:
 
-- `Phase 6R / Packet 6R-E`
+- no default packet is currently open; reopen only if a narrower native quad, mask, or divergence-reporting gap is later proven above the landed recognition stack
 
 ### `NuiLab/code-vr`
 
diff --git a/docs/HYPERTWIST_RECOGNITION_COMPARISON_ADJUNCT_HIERARCHY_RECONCILIATION_2026-05-27.md b/docs/HYPERTWIST_RECOGNITION_COMPARISON_ADJUNCT_HIERARCHY_RECONCILIATION_2026-05-27.md
new file mode 100644
index 0000000..99ae61d
--- /dev/null
+++ b/docs/HYPERTWIST_RECOGNITION_COMPARISON_ADJUNCT_HIERARCHY_RECONCILIATION_2026-05-27.md
@@ -0,0 +1,106 @@
+# Created on `2026-05-27`
+
+## Status
+
+`closed`
+
+## Purpose
+
+This note reconciles the retained permissive recognition-comparison adjunct rows:
+
+- `cahidenes/rubiks-cube-solver`
+- `tentone/rubix-solver`
+
+The earlier `Phase 2R-C` packet correctly kept both rows subordinate, but it used the historical label `Phase 6R-E` for their possible later widening route.
+
+That label is no longer safe current truth because later live product work already uses `Phase 6R-E` for the landed `ggml-org/whisper.cpp` speech transcript session packet.
+
+The goal of this note is therefore:
+
+- keep the retained donor value
+- remove the stale packet-label collision
+- clarify the exact narrow retained slices
+- confirm whether any already landed recognition packet needs reopening
+
+## Current judgment
+
+- no previously landed product packet needs reopening
+- no product code change is justified from this pass
+- no default recognition-adjunct widening packet is open
+- `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` stay retained as a narrow recognition-comparison adjunct lane only
+
+Current live owners already cover the primary product stack:
+
+- landed `qbr` bounded packets own calibration, ordered face observation, and the webcam shell
+- landed `vivaansinghvi07/rubix-cube-solver` bounded packets own committed-face reconstruction, browser-shell routing, and bounded solve explanation
+- first-party `Phase 6R-R` and `Phase 6R-S` surfaces own the bounded correction and correction-resolution closure family
+
+## Source-backed retained slices
+
+### `cahidenes/rubiks-cube-solver`
+
+Retain only the narrow comparison value visible in the checked mirror:
+
+- face-orientation fill logic
+- cube-string assembly from partial capture
+- lightweight HSV and per-sticker bookkeeping
+- the two-opposite-corner capture assumption as an optional comparator heuristic
+
+Do not promote:
+
+- the repo as a primary recognition owner
+- its camera shell as a product boundary
+- its `kociemba` handoff as generalized solver ownership
+
+### `tentone/rubix-solver`
+
+Retain only the narrow comparison value visible in the checked mirror:
+
+- quad clustering and quad ordering
+- square-mask color sampling and threshold comparison
+- center-color face identification
+- local native face-array or move-state comparison behavior
+
+Do not promote:
+
+- the brute-force solve shell
+- the local camera application shell
+- the repo as a primary recognition or correction owner
+
+## Why no reopen is justified
+
+The currently landed first-party stack already exposes the bounded recognition path that these rows would otherwise justify:
+
+- `qbr` webcam-shell validation exists
+- committed-face reconstruction exists
+- browser recognition shell and manual-edit handoff exist
+- contradiction-aware correction and resolution closure exist
+
+That means the remaining value from `cahidenes` and `tentone` is comparison-oriented, not ownership-oriented.
+
+They remain useful only if a later first-party gap is proven in one of these exact narrow seams:
+
+- face-placement disagreement reporting
+- cube-string assembly cross-checking
+- quad-sorting or square-mask comparison diagnostics
+- bounded native-versus-primary recognition divergence reporting
+
+Until such a gap is proven, they stay retained and non-live.
+
+## Sequence correction
+
+The current routing truth is:
+
+- `Phase 2R-C` remains closed and still owns the residual-row ownership boundary
+- the older historical widening label `Phase 6R-E` is superseded for these two rows only
+- use `retained recognition-comparison adjunct lane` as the current canon wording
+- later widening may happen only if a concrete first-party recognition-comparison owner gap is proven after the landed `qbr`, `rubix-cube-solver`, and correction-stack seams
+
+## Required canon posture
+
+Current authority surfaces should now say all of the following consistently:
+
+- these two rows are not straight `Phase 3R` implementation candidates
+- these two rows are not primary recognition owners
+- these two rows are retained comparison adjuncts behind landed first-party owners
+- no default widening packet is open for them today
diff --git a/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md b/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md
index 4756268..bf043b5 100644
--- a/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md
+++ b/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md
@@ -296,7 +296,7 @@ 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 `6R-E`, `6R-F`, and `3R-G` rather than broad inherited permissive routing
+- the residual `0R-B` rows are now split further by `2R-C` into the retained recognition-comparison adjunct lane, the retained `6R-F` 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
@@ -354,7 +354,7 @@ Next packet:
 
 Residual-lane result:
 
-- `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` are now the retained `6R-E` recognition-comparison adjunct lane behind the retained recognition anchors
+- `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 `6R-F` symbolic-to-spatial XR pedagogy experiment lane
 - `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
@@ -820,13 +820,15 @@ Deep-evaluate first because these are the most likely remaining straight impleme
 - `HactarCE/Hyperspeedcube`
 - `kkoomen/qbr`
 - `vivaansinghvi07/rubix-cube-solver`
-- `tentone/rubix-solver`
-- `cahidenes/rubiks-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:
diff --git a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md
index 079285f..ae4ecb7 100644
--- a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md
+++ b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md
@@ -308,7 +308,7 @@ Count: `29`
 | `@react-spring/rafz` | `MIT` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain only as the subordinate frame-loop and scheduling package beneath `pmndrs/react-spring` inside `Phase 3R-F`. |
 | `@react-spring/shared` | `MIT` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain only as the subordinate motion-utility package beneath `pmndrs/react-spring` inside `Phase 3R-F`. |
 | `@react-spring/types` | `MIT` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain only as the subordinate type-contract package beneath `pmndrs/react-spring` inside `Phase 3R-F`. |
-| `cahidenes/rubiks-cube-solver` | `MIT` | Locked Strategic Donor | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as part of the `Phase 6R-E` recognition-comparison adjunct lane for face placement and cube-string cross-checks behind the retained recognition anchors; do not widen in `Phase 3R`. |
+| `cahidenes/rubiks-cube-solver` | `MIT` | Locked Strategic Donor | `integrate` | `selected_not_live_permissive_candidate` | `phase2rc_recognition_adjunct_gap_eval_only` | `Phase 2R-C` plus the `2026-05-27` recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed `qbr`, `rubix-cube-solver`, and first-party correction-stack owners; no default widening packet is open. |
 | `ecomfe/echarts-gl` | `BSD-3-Clause` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-C` closed for the anchor. Retain as an optional subordinate `3D` analytics and explainer sidecar beneath the landed `apache/echarts` lane; do not treat it as separately live. |
 | `ecomfe/zrender` | `BSD-3-Clause` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-C` closed for the anchor. Retain as the lower-level subordinate `2D` substrate beneath the landed `apache/echarts` lane; do not treat it as separately live. |
 | `google/model-viewer/packages/model-viewer-effects` | `Apache-2.0` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed `google/model-viewer` lane; do not treat it as separately live. |
@@ -330,7 +330,7 @@ Count: `29`
 | `pmndrs/uikit` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Freeze as the browser spatial UI layer inside `Phase 3R-F` beside `pmndrs/xr`; do not promote it into a standalone product lane. |
 | `pmndrs/use-gesture` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the gesture/input substrate inside `Phase 3R-F`; widen only where browser sidecars actually need it. |
 | `pmndrs/zustand` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the browser-side state substrate inside `Phase 3R-F`; use only where browser sidecars actually need local/editor state. |
-| `tentone/rubix-solver` | `MIT` | Locked Strategic Donor | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as part of the `Phase 6R-E` native recognition-comparison adjunct lane for quad sorting, square-mask color sampling, and native face/state cross-checks behind the retained recognition anchors; do not widen in `Phase 3R`. |
+| `tentone/rubix-solver` | `MIT` | Locked Strategic Donor | `integrate` | `selected_not_live_permissive_candidate` | `phase2rc_recognition_adjunct_gap_eval_only` | `Phase 2R-C` plus the `2026-05-27` recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed `qbr`, `rubix-cube-solver`, and first-party correction-stack owners; no default widening packet is open. |
 
 ## Retained Boundary-Sensitive Candidates
 
diff --git a/docs/REPO_LICENSE_TRACKING.md b/docs/REPO_LICENSE_TRACKING.md
index 8de979e..3699894 100644
--- a/docs/REPO_LICENSE_TRACKING.md
+++ b/docs/REPO_LICENSE_TRACKING.md
@@ -1105,6 +1105,7 @@ Approved working posture:
 Decision date:
 
 - `2026-05-13`
+- refreshed on `2026-05-27`
 
 Current licensing judgment:
 
@@ -1134,7 +1135,8 @@ Approved working posture:
 - HyperTwist may use the codebase directly under the checked `MIT` posture
 - keep it subordinate to the retained `kkoomen/qbr` and `vivaansinghvi07/rubix-cube-solver` lanes
 - do not let it expand into the primary recognition, calibration, or correction shell
-- use its later widening only through the comparison-adjunct route packetized in `Phase 2R-C`
+- no default widening packet is open today; reopen only if a narrower face-placement, cube-string, or divergence-reporting gap is later proven above the landed recognition stack
+- use any later widening only through the retained comparison-adjunct route authority defined by `Phase 2R-C` plus the `2026-05-27` recognition-comparison hierarchy reconciliation
 
 ### `kkoomen/qbr`
 
@@ -1259,6 +1261,7 @@ Decision date:
 
 - `2026-04-24`
 - refreshed on `2026-05-13`
+- refreshed on `2026-05-27`
 
 Current licensing judgment:
 
@@ -1269,18 +1272,29 @@ Current licensing judgment:
 Source basis:
 
 - `C:\Workspaces\HyperTwist\mirrors\permissive\tentone\rubix-solver\README.md`
+- `C:\Workspaces\HyperTwist\mirrors\permissive\tentone\rubix-solver\vision.cpp`
+- `C:\Workspaces\HyperTwist\mirrors\permissive\tentone\rubix-solver\cube.cpp`
 - public repo page observed on `2026-04-24`
 
 Important caveat:
 
 - the mirrored source tree does not contain a top-level `LICENSE` file
 - the MIT posture is asserted by upstream README/repo presentation rather than proven by a bundled license text in the mirror
+- the strongest current product value is not the brute-force solve shell, but a narrow native comparison lane:
+  - quad clustering and ordering
+  - square-mask color sampling
+  - center-color face identification
+  - lightweight native face-array and state-mutation comparison behavior
+- that makes it useful as a bounded native recognition comparator behind the landed first-party recognition stack, not as a primary recognition, correction, or solver owner
 
 Approved working posture:
 
 - keep active as a strategic donor
 - preserve the upstream README licensing statement in the evaluation record
 - if HyperTwist later vendors code directly from this repo, capture and retain the final authoritative upstream license text at that time rather than relying only on the current mirror
+- keep it subordinate to the landed `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, and first-party correction-stack seams
+- explicitly exclude the brute-force solve shell and local camera shell from owned HyperTwist functionality
+- no default widening packet is open today; reopen only if a narrower native quad, mask, or divergence-reporting gap is later proven above the landed recognition stack
 
 ### `NuiLab/code-vr`
 
diff --git a/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv b/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv
index 57fd977..a931cfd 100644
--- a/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv
+++ b/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv
@@ -11,8 +11,8 @@
 "tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","","locked core candidate","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
 "rhasspy/piper","https://github.com/rhasspy/piper","multi-project","","donor bench","repurpose","moderate modification","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","high","voice-artifact-review-required","v6.3_final_source_of_truth","","",""
 "cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","high","dual-license-boundary-review","v6.3_final_source_of_truth","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-A closed. Preserve as the landed first-party classic-cubing semantic/runtime adapter lane through explicit MPL-aware dependency or adapter use; keep notices and publication duties explicit before any future direct upstream file modification."
-"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
-"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
+"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
+"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","Practical working assumption remains MIT from README and repo presentation, but the checked mirror lacks a bundled top-level license file. Keep this row permissive-active only as a subordinate recognition comparison adjunct, and capture the final authoritative upstream license text before any direct vendoring.","medium","readme-only-license-capture-before-direct-vendoring","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
 "Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
 "poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible in the current checked mirror. Retain this repo only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison; implement any strategically necessary behavior only from scrubbed first-party specifications if a narrower gap is later proven.","medium","no-license-clean-room-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Phase 1R plus the 2026-05-27 smartcube practice/review/SRS hierarchy clarification are closed. Retain only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS UX, recognition-versus-execution timing presentation, and local stats/history comparison; do not treat it as a live owner or a default clean-room next row."
 "kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","architecture only","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","high","license-contradiction-clean-room-donor","v6.3_final_source_of_truth","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier."
diff --git a/docs/repo_portfolio_unified_operational_v6_3.csv b/docs/repo_portfolio_unified_operational_v6_3.csv
index 5f35786..07b9e30 100644
--- a/docs/repo_portfolio_unified_operational_v6_3.csv
+++ b/docs/repo_portfolio_unified_operational_v6_3.csv
@@ -11,8 +11,8 @@
 "11766","tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","4.0","156.0","189.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","5.0","HT_training_stack","HT_training_stack_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","tao-yu/alg-trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","4.0","5","156.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
 "11769","rhasspy/piper","https://github.com/rhasspy/piper","multi-project","4.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0004","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","rhasspy/piper","multi-project","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","4.0","5","71.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.","Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.","Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.","high","voice-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","",""
 "11771","cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","5.0","152.0","185.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","medium-high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","1.0","HT_cube_semantics","HT_cube_semantics_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","cubing/cubing.js","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","5.0","5","152.0","Locked Strategic Donor","Boundary-sensitive classic-cubing semantics and rendering donor","","P1","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-A closed. Preserve as the landed first-party classic-cubing semantic/runtime adapter lane through explicit MPL-aware dependency or adapter use; keep notices and publication duties explicit before any future direct upstream file modification."
-"11848","cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","6.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0003","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","cahidenes/rubiks-cube-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","6.0","5","148.0","Locked Strategic Donor","Active recognition-heuristics and validation donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
-"11852","tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","7.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 7","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.","memo","False","True","0.0","7.0","HT_cube_vision","HT_cube_vision_0004","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","tentone/rubix-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","7.0","5","148.0","Locked Strategic Donor","Active native-CV donor and comparison bench","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
+"11848","cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","6.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","cahidenes/rubiks-cube-solver — MIT — opposite-corner capture heuristic, face-orientation fill logic, cube-string assembly from partial capture, and lightweight HSV or per-sticker bookkeeping retained only as a comparison adjunct behind qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface face-placement, cube-string assembly, or divergence-reporting comparisons without widening camera shell, primary calibration, or solver ownership.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded cross-checking or disagreement reporting; do not form a separate recognition silo or reopen primary recognition ownership.","Repurpose here means: optional face-placement, cube-string, or disagreement comparator logic only, not a primary recognition service or AR shell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect opposite-corner capture assumptions; face-placement fill; cube-string assembly; per-sticker bookkeeping; HSV sampling; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Inspect face-orientation fill logic, cube-string assembly, per-sticker bookkeeping, HSV sampling, opposite-corner capture assumptions, and divergence-reporting possibilities against the landed first-party stack.","Audit cahidenes/rubiks-cube-solver only as a retained recognition-comparison adjunct for HyperTwist. Inspect opposite-corner capture assumptions, face-orientation fill logic, cube-string assembly from partial capture, and lightweight HSV or per-sticker bookkeeping. Do not reopen it as a primary recognition, calibration, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0003","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","cahidenes/rubiks-cube-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","6.0","5","148.0","Locked Strategic Donor","Retained face-placement and cube-string comparison adjunct","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
+"11852","tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","7.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — README-only MIT posture — quad clustering, square-mask color sampling, center-color face identification, and lightweight native face or state comparison retained only as a comparison adjunct behind qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow native comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface quad, mask, or divergence comparisons without widening the local camera shell or brute-force solve shell.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded native comparison, side-by-side validation, or disagreement reporting; do not form a separate recognition silo or promote the local solve shell.","Repurpose here means: optional quad-sorting, square-mask, and native face-state comparator logic only, not a primary recognition service or solver shell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect quad clustering; sort stability; square-mask and threshold logic; center-color face labeling; native state-mutation semantics; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Inspect quad detection and sorting, square-mask color sampling, center-color face labeling, native face-array mutation behavior, and brute-force solve-shell exclusion.","Audit tentone/rubix-solver only as a retained native recognition-comparison adjunct for HyperTwist. Inspect quad clustering, square-mask color sampling, center-color face identification, native face-array mutation behavior, and brute-force solve-shell exclusion. Do not reopen it as a primary recognition, correction, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 7","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.","memo","False","True","0.0","7.0","HT_cube_vision","HT_cube_vision_0004","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","tentone/rubix-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","7.0","5","148.0","Locked Strategic Donor","Retained native quad and color comparison adjunct","","","permissive_or_noncopyleft_known","direct_incorporation_ok","Practical working assumption remains MIT from README and repo presentation, but the checked mirror lacks a bundled top-level license file. Keep this row permissive-active only as a subordinate recognition comparison adjunct, and capture the final authoritative upstream license text before any direct vendoring.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","medium","readme-only-license-capture-before-direct-vendoring","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
 "11857","Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","8.0","145.0","171.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0002","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","lykos/cube_trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","8.0","5","145.0","Locked Strategic Donor","Top-tier persistent training-domain donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
 "11861","poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","9.0","145.0","171.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0016","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","poliva/cubedex","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","9.0","5","145.0","Locked Strategic Donor","Top-tier training UX and smartcube donor","","","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible in the current checked mirror. Retain this repo only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison; implement any strategically necessary behavior only from scrubbed first-party specifications if a narrower gap is later proven.","Model A may inspect and summarize smartcube practice/review behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source directly without a confirmed license grant.","Yes - this is the preferred path if a narrower smartcube practice/review slice later proves strategically necessary.","medium","no-license-clean-room-benchmark","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Phase 1R plus the 2026-05-27 smartcube practice/review/SRS hierarchy clarification are closed. Retain only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS UX, recognition-versus-execution timing presentation, and local stats/history comparison; do not treat it as a live owner or a default clean-room next row."
 "11865","kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","10.0","145.0","171.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked strategic donor","repurpose","architecture only","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source","kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.","memo","False","True","0.0","4.0","HT_hyper_engine","HT_hyper_engine_0002","cubing / algorithm training","Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.","HyperTwist","hypercubing / nD simulation","integrate","direct","medium","kash/cubedesk","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","10.0","5","145.0","Locked Strategic Donor","Restrictive clean-room donor target","","P1","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier."
diff --git a/docs/repo_portfolio_unified_phase_g_v6_3.csv b/docs/repo_portfolio_unified_phase_g_v6_3.csv
index 6fa3551..4b7fa1b 100644
--- a/docs/repo_portfolio_unified_phase_g_v6_3.csv
+++ b/docs/repo_portfolio_unified_phase_g_v6_3.csv
@@ -11,8 +11,8 @@
 "4.0","tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","4.0","156.0","189.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","5.0","HT_training_stack","HT_training_stack_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","tao-yu/alg-trainer","1.0","Locked Parallel Foundation","2.0","Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.","Training / timing layer","Included","P0","tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","8548.0","111.0","","tao-yu/alg-trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4.0","1","2.0","156.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
 "1749.0","rhasspy/piper","https://github.com/rhasspy/piper","multi-project","4.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0004","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","rhasspy/piper","1.0","Donor Bench","4.0","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Cross-project / future-adjacent","Included","P2","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","4.0","2.0","2.0","8565.0","8.0","","rhasspy/piper","multi-project","","","","","","","","","","Original global Phase G v4 retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4.0","3","4.0","71.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.","Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.","Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.","high","voice-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","",""
 "5.0","cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","5.0","152.0","185.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","medium-high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","1.0","HT_cube_semantics","HT_cube_semantics_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","cubing/cubing.js","1.0","Locked Strategic Donor","1.0","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Boundary-sensitive classic-cubing semantics and rendering donor","Included","P1","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","2.0","4.0","3.0","11771.0","112.0","","cubing/cubing.js","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","5.0","1","1.0","152.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-A closed. Preserve as the landed first-party classic-cubing semantic/runtime adapter lane through explicit MPL-aware dependency or adapter use; keep notices and publication duties explicit before any future direct upstream file modification."
-"6.0","cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","6.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0003","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","cahidenes/rubiks-cube-solver","1.0","Locked Strategic Donor","3.0","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Active recognition-heuristics and validation donor","Included","P1","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11849.0","113.0","","cahidenes/rubiks-cube-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","6.0","2","3.0","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
-"7.0","tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","7.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 7","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.","memo","False","True","0.0","7.0","HT_cube_vision","HT_cube_vision_0004","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","tentone/rubix-solver","1.0","Locked Strategic Donor","3.0","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Active native-CV donor and comparison bench","Included","P1","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11852.0","114.0","","tentone/rubix-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","7.0","2","3.0","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
+"6.0","cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","6.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","cahidenes/rubiks-cube-solver — MIT — opposite-corner capture heuristic, face-orientation fill logic, cube-string assembly from partial capture, and lightweight HSV or per-sticker bookkeeping retained only as a comparison adjunct behind qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface face-placement, cube-string assembly, or divergence-reporting comparisons without widening camera shell, primary calibration, or solver ownership.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded cross-checking or disagreement reporting; do not form a separate recognition silo or reopen primary recognition ownership.","Repurpose here means: optional face-placement, cube-string, or disagreement comparator logic only, not a primary recognition service or AR shell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect opposite-corner capture assumptions; face-placement fill; cube-string assembly; per-sticker bookkeeping; HSV sampling; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Inspect face-orientation fill logic, cube-string assembly, per-sticker bookkeeping, HSV sampling, opposite-corner capture assumptions, and divergence-reporting possibilities against the landed first-party stack.","Audit cahidenes/rubiks-cube-solver only as a retained recognition-comparison adjunct for HyperTwist. Inspect opposite-corner capture assumptions, face-orientation fill logic, cube-string assembly from partial capture, and lightweight HSV or per-sticker bookkeeping. Do not reopen it as a primary recognition, calibration, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0003","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","cahidenes/rubiks-cube-solver","1.0","Locked Strategic Donor","3.0","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Retained face-placement and cube-string comparison adjunct","Included","P1","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11849.0","113.0","","cahidenes/rubiks-cube-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","6.0","2","3.0","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
+"7.0","tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","7.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — README-only MIT posture — quad clustering, square-mask color sampling, center-color face identification, and lightweight native face or state comparison retained only as a comparison adjunct behind qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow native comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface quad, mask, or divergence comparisons without widening the local camera shell or brute-force solve shell.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded native comparison, side-by-side validation, or disagreement reporting; do not form a separate recognition silo or promote the local solve shell.","Repurpose here means: optional quad-sorting, square-mask, and native face-state comparator logic only, not a primary recognition service or solver shell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect quad clustering; sort stability; square-mask and threshold logic; center-color face labeling; native state-mutation semantics; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Inspect quad detection and sorting, square-mask color sampling, center-color face labeling, native face-array mutation behavior, and brute-force solve-shell exclusion.","Audit tentone/rubix-solver only as a retained native recognition-comparison adjunct for HyperTwist. Inspect quad clustering, square-mask color sampling, center-color face identification, native face-array mutation behavior, and brute-force solve-shell exclusion. Do not reopen it as a primary recognition, correction, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 7","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.","memo","False","True","0.0","7.0","HT_cube_vision","HT_cube_vision_0004","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","tentone/rubix-solver","1.0","Locked Strategic Donor","3.0","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Retained native quad and color comparison adjunct","Included","P1","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11852.0","114.0","","tentone/rubix-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","7.0","2","3.0","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","Practical working assumption remains MIT from README and repo presentation, but the checked mirror lacks a bundled top-level license file. Keep this row permissive-active only as a subordinate recognition comparison adjunct, and capture the final authoritative upstream license text before any direct vendoring.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","medium","readme-only-license-capture-before-direct-vendoring","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
 "8.0","Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","8.0","145.0","171.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0002","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","lykos/cube_trainer","1.0","Locked Strategic Donor","3.0","Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain.","Top-tier persistent training-domain donor","Included","P1","Lykos/cube_trainer is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier persistent training-domain donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11857.0","115.0","","lykos/cube_trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","8.0","2","3.0","145.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
 "10.0","poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","9.0","145.0","171.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0016","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","poliva/cubedex","1.0","Locked Strategic Donor","3.0","Top-tier strategic donor for smartcube-aware, offline-first training UX and practical drill ergonomics, but not the owner of the long-term training backend.","Top-tier training UX and smartcube donor","Included","P1","poliva/cubedex is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier training UX and smartcube donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11861.0","116.0","","poliva/cubedex","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","9.0","2","3.0","145.0","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible in the current checked mirror. Retain this repo only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison; implement any strategically necessary behavior only from scrubbed first-party specifications if a narrower gap is later proven.","Model A may inspect and summarize smartcube practice/review behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source directly without a confirmed license grant.","Yes - this is the preferred path if a narrower smartcube practice/review slice later proves strategically necessary.","medium","no-license-clean-room-benchmark","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Phase 1R plus the 2026-05-27 smartcube practice/review/SRS hierarchy clarification are closed. Retain only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS UX, recognition-versus-execution timing presentation, and local stats/history comparison; do not treat it as a live owner or a default clean-room next row."
 "9.0","kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","10.0","145.0","171.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked strategic donor","repurpose","architecture only","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source","kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.","memo","False","True","0.0","4.0","HT_hyper_engine","HT_hyper_engine_0002","cubing / algorithm training","Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.","HyperTwist","hypercubing / nD simulation","integrate","direct","medium","kash/cubedesk","1.0","Locked Strategic Donor","3.0","Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.","Restrictive clean-room donor target","Included","P1","Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.","2.0","5.0","3.0","11865.0","117.0","","kash/cubedesk","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","10.0","2","3.0","145.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier."
diff --git a/docs/repo_portfolio_unified_source_audit_v6_3.csv b/docs/repo_portfolio_unified_source_audit_v6_3.csv
index 3ba43e2..4895f48 100644
--- a/docs/repo_portfolio_unified_source_audit_v6_3.csv
+++ b/docs/repo_portfolio_unified_source_audit_v6_3.csv
@@ -46,7 +46,7 @@
 9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_semantics_0001","HT_cube_semantics","cubing/cubing.js","","","","","","","Original global P0-P3 source audit retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","2","1","152.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-A closed. Preserve as the landed first-party classic-cubing semantic/runtime adapter lane through explicit MPL-aware dependency or adapter use; keep notices and publication duties explicit before any future direct upstream file modification."
 "cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","25","9208","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/alg.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.","Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.","Inspect cubing/alg.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0002","HT_cube_semantics","cubing/alg.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract."
 "cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","27","9210","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/twisty.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.","Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.","Inspect cubing/twisty.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0003","HT_cube_semantics","cubing/twisty.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract."
-"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","Vision / reconstruction donor layer","P1","55","9211","4.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the donor thesis for cahidenes/rubiks-cube-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
+"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","Retained face-placement and cube-string comparison adjunct","P1","55","9211","4.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the retained comparison-adjunct thesis for cahidenes/rubiks-cube-solver in HyperTwist: what exact narrow logic survives, how it compares against the landed first-party recognition stack, and whether any later owner-gap reopening is actually justified.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect face-orientation fill logic, cube-string assembly, per-sticker bookkeeping, HSV sampling, opposite-corner capture assumptions, and divergence-reporting possibilities against the landed first-party stack.","Inspect opposite-corner capture assumptions; face-placement fill; cube-string assembly; per-sticker bookkeeping; HSV sampling; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface face-placement, cube-string assembly, or divergence-reporting comparisons without widening camera shell, primary calibration, or solver ownership.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded cross-checking or disagreement reporting; do not form a separate recognition silo or reopen primary recognition ownership.","Repurpose here means: optional face-placement, cube-string, or disagreement comparator logic only, not a primary recognition service or AR shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages
 4) Integration path into target project
@@ -54,8 +54,8 @@
 6) Best merge partners and exact coupling seam
 7) Reasons to promote / retain / demote
 8) Confidence change after source audit
-9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0003","HT_cube_vision","cahidenes/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
-"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","Vision / reconstruction donor layer","P1","56","9212","5.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the donor thesis for tentone/rubix-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
+9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver only as a retained recognition-comparison adjunct for HyperTwist. Inspect opposite-corner capture assumptions, face-orientation fill logic, cube-string assembly from partial capture, and lightweight HSV or per-sticker bookkeeping. Do not reopen it as a primary recognition, calibration, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","HT_cube_vision_0003","HT_cube_vision","cahidenes/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
+"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","Retained native quad and color comparison adjunct","P1","56","9212","5.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the retained native comparison-adjunct thesis for tentone/rubix-solver in HyperTwist: what exact narrow logic survives, how it compares against the landed first-party recognition stack, and whether any later owner-gap reopening is actually justified.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect quad detection and sorting, square-mask color sampling, center-color face labeling, native face-array mutation behavior, and brute-force solve-shell exclusion.","Inspect quad clustering; sort stability; square-mask and threshold logic; center-color face labeling; native state-mutation semantics; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow native comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface quad, mask, or divergence comparisons without widening the local camera shell or brute-force solve shell.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded native comparison, side-by-side validation, or disagreement reporting; do not form a separate recognition silo or promote the local solve shell.","Repurpose here means: optional quad-sorting, square-mask, and native face-state comparator logic only, not a primary recognition service or solver shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages
 4) Integration path into target project
@@ -63,7 +63,7 @@
 6) Best merge partners and exact coupling seam
 7) Reasons to promote / retain / demote
 8) Confidence change after source audit
-9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0004","HT_cube_vision","tentone/rubix-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
+9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Audit tentone/rubix-solver only as a retained native recognition-comparison adjunct for HyperTwist. Inspect quad clustering, square-mask color sampling, center-color face identification, native face-array mutation behavior, and brute-force solve-shell exclusion. Do not reopen it as a primary recognition, correction, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","HT_cube_vision_0004","HT_cube_vision","tentone/rubix-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","Practical working assumption remains MIT from README and repo presentation, but the checked mirror lacks a bundled top-level license file. Keep this row permissive-active only as a subordinate recognition comparison adjunct, and capture the final authoritative upstream license text before any direct vendoring.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","medium","readme-only-license-capture-before-direct-vendoring","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
 "Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","Locked Strategic Donor","Training / timing layer","P1","57","9213","14.0","145.0","171.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","integrate","direct","Confirm the donor thesis for Lykos/cube_trainer in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages
diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md
index 1708094..47d3e70 100644
--- a/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md
+++ b/docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md
@@ -186,6 +186,7 @@ repo.
 | Bounded solve explanation/recommendation shell | Implemented now | `rubix-cube-solver` bounded packet | Live stage-ladder recommendation state above the bounded browser recognition shell. This is not a generalized solver backend. |
 | Provider-backed recognition service contract | Implemented now | first-party recognition client surfaces | First-party normalized recognition session boundary is real. |
 | Multilingual recognition guidance shell | Deep-source grounded retained | `qbr` retained remainder | Kept deferred until a font-safe and provenance-safe shipping path is explicit. |
+| Recognition-comparison adjunct boundary | Deep-source grounded retained | `cahidenes/rubiks-cube-solver` + `tentone/rubix-solver` retained adjunct lane | Narrow face-placement, cube-string cross-check, quad sorting, square-mask color sampling, center-color face labeling, and native face/state comparison value remain retained only behind the landed `qbr`, `rubix-cube-solver`, and first-party correction-stack owners. No default widening packet is open. |
 | Multi-face correction/explanation shell | Implemented now | first-party recognition/training surfaces | Current bounded correction profile, contradiction-aware correction state, accepted-resolution ledger, and correction-explanation / solve-unlock shell are live above the landed `Phase 6R-O`, `Phase 6R-P`, `Phase 6R-Q`, `Phase 6R-R`, and `Phase 6R-S` seams. Bundled-asset, generalized solver-backend, and broad playback/runtime widening remain deferred. |
 | Compact classic-cube solver correctness and heuristic-search oracle | Deep-source grounded retained | `brownan/Rubiks-Cube-Solver` retained lane + `efrantar/rob-twophase` comparator | Broad solver-backend ownership remains non-live. `brownan` remains the primary compact correctness and heuristic-table oracle, while `efrantar` remains the retained metric, pruning, robot-execution, and performance comparator. |