Reconcile v6.3 row source live states

This commit is contained in:
axiomlogicnexus 2026-05-27 19:18:47 +02:00
parent 17d27adb41
commit fa231fad05
4 changed files with 28 additions and 28 deletions

View file

@ -1,12 +1,12 @@
"repo","primary_url","best_fit_project_v2","phase_g_bucket","portfolio_role_v3","recommended_action_v2","repurposing_potential_v2","v6_license_annotation","v6_license_annotation_status","v6_license_annotation_source","copyleft_relevance_v6_1","copyleft_strategy_v6_1","copyleft_rationale_v6_1","copyleft_strategy_confidence_v6_1","copyleft_manual_review_trigger_v6_1","v6_3_source_of_truth","v6_3_live_state_2026_05_11","v6_3_reset_lane_2026_05_11","v6_3_reset_next_step_2026_05_11"
"HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","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","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."
"HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","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","Later Phase 6R-A/K/L/M/N preserve sequence closed. Preserve as the landed first-party hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, not from the old candidate queue wording."
"SYSTRAN/faster-whisper","https://github.com/SYSTRAN/faster-whisper","multi-project","","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.","high","model-artifact-review-required","v6.3_final_source_of_truth","","",""
"cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","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.","high","gpl-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 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","donor bench","repurpose","architecture only","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","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.","high","gpl-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 embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract."
"HactarCE/2x2x2x2-Scrambler","https://github.com/HactarCE/2x2x2x2-Scrambler","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.","high","gpl-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 Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier."
"kkoomen/qbr","https://github.com/kkoomen/qbr","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","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."
"kkoomen/qbr","https://github.com/kkoomen/qbr","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","Later Phase 6R-B/O preserve sequence closed for the currently justified slice. Preserve as the landed first-party recognition calibration, ordered face-observation, and webcam-shell lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while keeping multilingual/font redistribution and broader solve-shell ownership deferred."
"coqui-ai/TTS","https://github.com/coqui-ai/TTS","multi-project","","donor bench","repurpose","moderate modification","MPL-2.0 code; mixed model payload licenses","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.","medium","model-license-selection-required","v6.3_final_source_of_truth","","",""
"vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","Locked Parallel Foundation","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","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."
"vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","Locked Parallel Foundation","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","Later Phase 6R-C/P/Q preserve sequence closed for the currently justified slice. Preserve as the landed first-party committed-face reconstruction, browser/webcam shell, and bounded solve-explanation/recommendation lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broad solver-backend ownership and bundled twistysim.min.js redistribution stay deferred."
"ggml-org/whisper.cpp","https://github.com/ggml-org/whisper.cpp","multi-project","","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.","high","model-artifact-review-recommended","v6.3_final_source_of_truth","","",""
"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","","",""
@ -14,11 +14,11 @@
"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."
"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","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."
"cutelyaware/magiccube4d","https://github.com/cutelyaware/magiccube4d/tree/master","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","medium","custom-license-attribution-review","v6.3_final_source_of_truth","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-B closed. Preserve as the landed attributed legacy 4D interaction, history, macro, topology-reference, and provenance-boundary lane beneath the Hyperspeedcube anchor; start future widening from the live-lane audit, then Phase 4R-B, then REPO_LICENSE_TRACKING.md."
"roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","high","permissive-specialized-donor","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."
"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","high","permissive-specialized-donor","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."
"roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","high","permissive-specialized-donor","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","high","permissive-specialized-donor","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
"cs0x7f/cstimer","https://github.com/cs0x7f/cstimer","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","high","gpl-timer-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle."
"aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0-only","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","high","gpl-reference-only-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows."
"brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope."
@ -37,7 +37,7 @@
"yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation."
"Hypercubers/hypercubing.xyz","https://github.com/Hypercubers/hypercubing.xyz","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.","high","permissive-knowledge-donor","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md."
"Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","high","routine-review-only","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md."
"roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","high","permissive-top-tier-donor","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."
"roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","high","permissive-top-tier-donor","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
"PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","","donor bench","repurpose","moderate modification","MIT outside ee/; enterprise-restricted in ee/","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","high","mixed-license-path-review-required","v6.3_final_source_of_truth","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-D closed. Preserve as the landed first-party control-plane telemetry, replay-diagnostic, scheduled-change, early-access, and explicit root-MIT-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-D, then REPO_LICENSE_TRACKING.md; keep the explicit ee/ exclusion and mixed-license subtree boundary visible."
"met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","high","standard-notice-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md."
"apache/echarts","https://github.com/apache/echarts","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","high","notice-file-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md."

1 repo primary_url best_fit_project_v2 phase_g_bucket portfolio_role_v3 recommended_action_v2 repurposing_potential_v2 v6_license_annotation v6_license_annotation_status v6_license_annotation_source copyleft_relevance_v6_1 copyleft_strategy_v6_1 copyleft_rationale_v6_1 copyleft_strategy_confidence_v6_1 copyleft_manual_review_trigger_v6_1 v6_3_source_of_truth v6_3_live_state_2026_05_11 v6_3_reset_lane_2026_05_11 v6_3_reset_next_step_2026_05_11
2 HactarCE/Hyperspeedcube https://github.com/HactarCE/Hyperspeedcube 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 selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-A/K/L/M/N preserve sequence closed. Preserve as the landed first-party hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, not from the old candidate queue wording.
3 SYSTRAN/faster-whisper https://github.com/SYSTRAN/faster-whisper multi-project donor bench repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default. high model-artifact-review-required v6.3_final_source_of_truth
4 cubing/alg.js https://github.com/cubing/alg.js HyperTwist Donor Bench donor bench repurpose architecture only GPL-3.0-or-later known_from_reference_material uploaded_reference_docs 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. high gpl-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 algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract.
5 cubing/twisty.js https://github.com/cubing/twisty.js HyperTwist Donor Bench donor bench repurpose architecture only GPL-3.0-or-later known_from_reference_material uploaded_reference_docs 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. high gpl-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 embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract.
6 HactarCE/2x2x2x2-Scrambler https://github.com/HactarCE/2x2x2x2-Scrambler HyperTwist Donor Bench donor bench repurpose architecture only GPL-3.0 known_from_reference_material uploaded_reference_docs mixed_or_boundary_sensitive_known reverse_engineer_preferred The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification. high gpl-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 Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier.
7 kkoomen/qbr https://github.com/kkoomen/qbr 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 selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-B/O preserve sequence closed for the currently justified slice. Preserve as the landed first-party recognition calibration, ordered face-observation, and webcam-shell lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while keeping multilingual/font redistribution and broader solve-shell ownership deferred.
8 coqui-ai/TTS https://github.com/coqui-ai/TTS multi-project donor bench repurpose moderate modification MPL-2.0 code; mixed model payload licenses known_from_reference_material uploaded_reference_docs mixed_or_boundary_sensitive_known bounded_sidecar_or_selective_reimplementation Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency. medium model-license-selection-required v6.3_final_source_of_truth
9 vivaansinghvi07/rubix-cube-solver https://github.com/vivaansinghvi07/rubix-cube-solver HyperTwist Locked Parallel Foundation 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 selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-C/P/Q preserve sequence closed for the currently justified slice. Preserve as the landed first-party committed-face reconstruction, browser/webcam shell, and bounded solve-explanation/recommendation lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broad solver-backend ownership and bundled twistysim.min.js redistribution stay deferred.
10 ggml-org/whisper.cpp https://github.com/ggml-org/whisper.cpp multi-project donor bench repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default. high model-artifact-review-recommended v6.3_final_source_of_truth
11 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.
12 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
14 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.
15 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.
16 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.
17 poliva/cubedex https://github.com/poliva/cubedex HyperTwist Locked Strategic Donor locked strategic donor integrate direct MIT no explicit license visible known_from_reference_material pending_repo_license_audit uploaded_reference_docs not_resolved_from_uploaded_materials permissive_or_noncopyleft_known license_unknown_pending direct_incorporation_ok reverse_engineer_preferred 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. 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. high medium strategic-or-implemented-component no-license-clean-room-benchmark v6.3_final_source_of_truth implemented_live_permissive not_live_reference_or_discard_candidate landed_permissive_preserve phase0r_reference_benchmark_or_discard_eval Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 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.
18 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.
19 cutelyaware/magiccube4d https://github.com/cutelyaware/magiccube4d/tree/master HyperTwist Locked Strategic Donor locked strategic donor repurpose moderate modification Custom broad-use license with attribution requested known_from_reference_material uploaded_reference_docs mixed_or_boundary_sensitive_known direct_incorporation_ok The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked. medium custom-license-attribution-review v6.3_final_source_of_truth implemented_live_boundary_sensitive landed_boundary_sensitive_preserve Phase 4R-B closed. Preserve as the landed attributed legacy 4D interaction, history, macro, topology-reference, and provenance-boundary lane beneath the Hyperspeedcube anchor; start future widening from the live-lane audit, then Phase 4R-B, then REPO_LICENSE_TRACKING.md.
20 roice3/Magic120Cell https://github.com/roice3/Magic120Cell HyperTwist Locked Strategic Donor locked strategic donor repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces. high permissive-specialized-donor v6.3_final_source_of_truth selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet.
21 roice3/MagicCube5D https://github.com/roice3/MagicCube5D HyperTwist Locked Strategic Donor locked strategic donor repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior. high permissive-specialized-donor v6.3_final_source_of_truth selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet.
22 cs0x7f/cstimer https://github.com/cs0x7f/cstimer HyperTwist Reserve Bench Reserve Bench future candidate architecture only GPL-3.0 known_from_reference_material uploaded_reference_docs mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation. high gpl-timer-benchmark v6.3_final_source_of_truth not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle.
23 aMonteSl/CodeXR https://github.com/aMonteSl/CodeXR HyperTwist Reserve Bench Reserve Bench future candidate architecture only GPL-3.0-only known_from_reference_material uploaded_reference_docs mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows. high gpl-reference-only-benchmark v6.3_final_source_of_truth not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows.
24 brianpeiris/RiftSketch https://github.com/brianpeiris/RiftSketch HyperTwist Reserve Bench Reserve Bench future candidate architecture only MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known pattern_only_preferred The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope. high strategic-or-implemented-component v6.3_final_source_of_truth not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope.
37 yakupbilen/drl-rubiks-cube https://github.com/yakupbilen/drl-rubiks-cube HyperTwist Reserve Bench Reserve Bench future candidate architecture only MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known pattern_only_preferred The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor. high strategic-or-implemented-component v6.3_final_source_of_truth not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation.
38 Hypercubers/hypercubing.xyz https://github.com/Hypercubers/hypercubing.xyz HyperTwist Locked Strategic Donor locked strategic donor repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist. high permissive-knowledge-donor v6.3_final_source_of_truth implemented_live_permissive landed_permissive_preserve Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md.
39 Aarav2709/KubeTimr https://github.com/Aarav2709/KubeTimr HyperTwist Donor Bench donor bench repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist. high routine-review-only v6.3_final_source_of_truth implemented_live_permissive landed_permissive_preserve Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md.
40 roice3/MagicTile https://github.com/roice3/MagicTile HyperTwist Locked Strategic Donor locked strategic donor repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it. high permissive-top-tier-donor v6.3_final_source_of_truth selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred.
41 PostHog/posthog https://github.com/PostHog/posthog HyperTwist donor bench repurpose moderate modification MIT outside ee/; enterprise-restricted in ee/ known_from_reference_material uploaded_reference_docs mixed_or_boundary_sensitive_known bounded_sidecar_or_selective_reimplementation The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths. high mixed-license-path-review-required v6.3_final_source_of_truth implemented_live_boundary_sensitive landed_boundary_sensitive_preserve Phase 4R-D closed. Preserve as the landed first-party control-plane telemetry, replay-diagnostic, scheduled-change, early-access, and explicit root-MIT-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-D, then REPO_LICENSE_TRACKING.md; keep the explicit ee/ exclusion and mixed-license subtree boundary visible.
42 met4citizen/TalkingHead https://github.com/met4citizen/TalkingHead HyperTwist Donor Bench donor bench repurpose moderate modification MIT known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell. high standard-notice-review v6.3_markdown_backfill implemented_live_permissive landed_permissive_preserve Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md.
43 apache/echarts https://github.com/apache/echarts HyperTwist Donor Bench donor bench repurpose moderate modification Apache-2.0 known_from_reference_material uploaded_reference_docs permissive_or_noncopyleft_known direct_incorporation_ok The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor. high notice-file-review v6.3_markdown_backfill implemented_live_permissive landed_permissive_preserve Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md.

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View file

@ -7,7 +7,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.","HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' 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.","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.","Audit HactarCE/Hyperspeedcube 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) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [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.","HT_hyper_engine_0001","HT_hyper_engine","hactarce/hyperspeedcube","","","","","","","Original global P0-P3 source audit retained","MIT","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","160.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.","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.","HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' 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.","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.","Audit HactarCE/Hyperspeedcube 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) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [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.","HT_hyper_engine_0001","HT_hyper_engine","hactarce/hyperspeedcube","","","","","","","Original global P0-P3 source audit retained","MIT","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","160.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","Later Phase 6R-A/K/L/M/N preserve sequence closed. Preserve as the landed first-party hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, not from the old candidate queue wording."
"kkoomen/qbr","https://github.com/kkoomen/qbr","HyperTwist","Locked Foundation","Live cube-recognition substrate","P0","21","9204","4.0","158.0","191.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","Validate whether kkoomen/qbr truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/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 vivaansinghvi07/rubix-cube-solver, 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: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","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.","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 | 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 core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
@ -16,7 +16,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.","kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' 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.","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.","Audit kkoomen/qbr 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) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 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_vision_0001","HT_cube_vision","kkoomen/qbr","","","","","","","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","1","158.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.","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.","kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' 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.","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.","Audit kkoomen/qbr 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) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 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_vision_0001","HT_cube_vision","kkoomen/qbr","","","","","","","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","1","158.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","Later Phase 6R-B/O preserve sequence closed for the currently justified slice. Preserve as the landed first-party recognition calibration, ordered face-observation, and webcam-shell lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while keeping multilingual/font redistribution and broader solve-shell ownership deferred."
"vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","Locked Parallel Foundation","Vision / reconstruction donor layer","P0","22","9205","8.0","158.0","191.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","Validate whether vivaansinghvi07/rubix-cube-solver truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","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 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: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","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.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","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 | 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 core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
@ -25,7 +25,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.","vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion 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.","Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.","Audit vivaansinghvi07/rubix-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) cubing/cubing.js [state/render backend]; 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_vision_0002","HT_cube_vision","vivaansinghvi07/rubix-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","1","158.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 wording to dossier-backed parallel-foundation 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.","vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion 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.","Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.","Audit vivaansinghvi07/rubix-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) cubing/cubing.js [state/render backend]; 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_vision_0002","HT_cube_vision","vivaansinghvi07/rubix-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","1","158.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 wording to dossier-backed parallel-foundation posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-C/P/Q preserve sequence closed for the currently justified slice. Preserve as the landed first-party committed-face reconstruction, browser/webcam shell, and bounded solve-explanation/recommendation lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broad solver-backend ownership and bundled twistysim.min.js redistribution stay deferred."
"tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","Locked Parallel Foundation","Training / timing layer","P0","23","9206","9.0","156.0","189.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","Validate whether tao-yu/Alg-Trainer truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","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 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.","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.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
@ -90,7 +90,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.","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.","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.","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.","HT_training_stack_0016","HT_training_stack","poliva/cubedex","","","","","","","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","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","Assigned from legacy HY_misc to HT_training_stack during cluster normalization 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."
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.","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.","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.","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.","HT_training_stack_0016","HT_training_stack","poliva/cubedex","","","","","","","Original global P0-P3 source audit 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","2","2","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."
"cs0x7f/cstimer","https://github.com/cs0x7f/cstimer","HyperTwist","Reserve Bench","Gold-standard timer benchmark","P2","60","9216","22.0","121.0","147.0","medium","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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the timer, persistence, statistics, and hardware-support behaviors that make cstimer the gold-standard timer benchmark for HyperTwist.","Timer transitions, persistence, statistics, reconstruction, scramble flow, and smart-device surfaces as benchmark material.","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.","Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.","Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.","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.","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.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","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.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in cs0x7f/cstimer
2) What must stay benchmark-only or clean-room-only
3) Acceptance-test, oracle, or behavior targets worth preserving","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 in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.","GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.","HT_timer_training_0001","HT_timer_training","cs0x7f/cstimer","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","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","121.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.","high","gpl-timer-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle."
@ -111,7 +111,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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Audit roice3/Magic120Cell 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 moderate modification and whether it belongs as subsystem donor / 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.","HT_hyper_engine_0004","HT_hyper_engine","roice3/magic120cell","","","","","","","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","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Audit roice3/Magic120Cell 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 moderate modification and whether it belongs as subsystem donor / 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.","HT_hyper_engine_0004","HT_hyper_engine","roice3/magic120cell","","","","","","","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","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","Specialized 5D cube interaction, progress, and macro donor","P1","7465","9220","50.0","122.0","137.0","medium","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 generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether roice3/MagicCube5D should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/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 higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","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.","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.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
@ -120,7 +120,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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Audit roice3/MagicCube5D 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 moderate modification and whether it belongs as subsystem donor / 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.","HT_hyper_engine_0005","HT_hyper_engine","roice3/magiccube5d","","","","","","","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","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Audit roice3/MagicCube5D 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 moderate modification and whether it belongs as subsystem donor / 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.","HT_hyper_engine_0005","HT_hyper_engine","roice3/magiccube5d","","","","","","","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","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
"aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","Reserve Bench","Reference-only XR benchmark","P3","7467","9222","51.0","119.0","134.0","medium","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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","future candidate","architecture only","Validate that CodeXR remains reference-only and record the specific immersive interaction ideas worth preserving without direct source reuse.","Collaboration-room flow, scene launch, virtual screens, and immersive interaction behavior as benchmark material only.","Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?","Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.","Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.","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.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in aMonteSl/CodeXR
2) What must stay benchmark-only or clean-room-only
3) Acceptance-test, oracle, or behavior targets worth preserving","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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.","GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.","HT_cube_vision_0005","HT_cube_vision","amontesl/codexr","","","","","","","Original global P0-P3 source audit retained","GPL-3.0-only","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","3","119.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-reference-only-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows."
@ -228,7 +228,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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. 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_hyper_engine_0007","HT_hyper_engine","roice3/magictile","","","","","","","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","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. 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_hyper_engine_0007","HT_hyper_engine","roice3/magictile","","","","","","","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","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
"PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","Donor Bench","Adjacency / future transfer","P2","7492","9247","20.0","72.0","81.0","medium","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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Determine whether PostHog/posthog should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","telemetry and event schemas, replay product boundaries, feature-flag governance, diagnostics, service slices, hidden modules","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","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, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.","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.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages

1 repo primary_url project phase_g_bucket stack_layer audit_tier tier_queue_order global_order wave_number portfolio_priority_score execution_priority_score_v3 current_confidence modification_scope_detail_v3 recommended_action_v2 repurposing_potential_v2 audit_goal inspect_emphasis source_code_audit_targets source_inspection_questions integration_realization_detail consolidation_detail repurpose_detail merger_partner_1 merger_type_1 merger_rationale_1 merger_partner_2 merger_type_2 merger_rationale_2 merger_partner_3 merger_type_3 merger_rationale_3 cross_project_transfer_targets cross_project_transfer_rationale reclassify_up_if reclassify_down_if deliverable_expected session_note_template recommended_context_packet phase_g_master_list_rationale phase_g_bucket_reason coding_model_instruction_v3 source_audit_packet_id cluster_tag _repo_norm v5_runtime_project v5_scriptorium_override_status v5_scriptorium_bucket v5_scriptorium_stack_layer v5_scriptorium_current_reality_status v5_scriptorium_supersedes_prior_assessment v5_source_of_truth v6_license_annotation v6_license_annotation_status v6_license_annotation_source v6_supplemental_intake_present v6_supplemental_source_groups v6_supplemental_source_sections v6_supplemental_source_files v6_reference_material_position v6_kali_agent_access_relevance v6_branch_seed_prompt_included v6_branch_seed_scope v6_intake_wave v6_notes v6_source_of_truth project_rank_num tier_rank_num priority_num copyleft_relevance_v6_1 copyleft_strategy_v6_1 copyleft_rationale_v6_1 preferred_boundary_model_v6_1 open_compliance_if_used_as_is_v6_1 reverse_engineer_if_proprietary_core_needed_v6_1 copyleft_strategy_confidence_v6_1 copyleft_manual_review_trigger_v6_1 as_is_incorporation_sensible_v6_1 v6_2_sre_layer v6_2_sre_stratum v6_2_sre_role v6_2_sre_family v6_2_related_kali_package v6_2_related_upstream_repo v6_2_kali_package_suffices_for_tool_execution v6_2_upstream_repo_preferred_for_deep_eval v6_2_index_page_followup_useful v6_2_index_page_followup_reason v6_2_sre_notes v6_2_dnspy_ilspy_relevance v6_3_source_of_truth v6_3_merge_note v6_3_live_state_2026_05_11 v6_3_reset_lane_2026_05_11 v6_3_reset_next_step_2026_05_11
7 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.
8 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.
9 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 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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.
10 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 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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.
11 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 4) Integration path into target project 5) Repurpose path outside the original thesis 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. 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. Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain. 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. HT_training_stack_0002 HT_training_stack lykos/cube_trainer 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 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.
12 kash/cubedesk https://github.com/kash/cubedesk HyperTwist Locked Strategic Donor Restrictive clean-room donor target P1 58 9214 16.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 generalized puzzle/state/render logic while building a new application shell around it. repurpose architecture only Confirm the donor thesis for kash/cubedesk 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 higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks. Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. 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. 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. 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 5) Repurpose path outside the original thesis 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. Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment. 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. 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. HT_hyper_engine_0002 HT_hyper_engine kash/cubedesk Original global P0-P3 source audit 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 2 2 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.
13 poliva/cubedex https://github.com/poliva/cubedex HyperTwist Locked Strategic Donor Training / timing layer P1 59 9215 15.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 scene/layout primitives and replacing surrounding data models or backend assumptions. integrate direct Confirm the donor thesis for poliva/cubedex 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 scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. 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. 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. 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 5) Repurpose path outside the original thesis 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. 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. 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. 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. HT_training_stack_0016 HT_training_stack poliva/cubedex Original global P0-P3 source audit retained MIT no explicit license visible known_from_reference_material pending_repo_license_audit uploaded_reference_docs 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 2 2 145.0 permissive_or_noncopyleft_known license_unknown_pending direct_incorporation_ok reverse_engineer_preferred 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. 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. Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires. Model A may inspect and summarize smartcube practice/review behavior; Model B should implement only from a scrubbed clean-room specification. Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed. Do not incorporate source directly without a confirmed license grant. Usually unnecessary unless you later decide the existing implementation is too constraining architecturally. Yes - this is the preferred path if a narrower smartcube practice/review slice later proves strategically necessary. high medium strategic-or-implemented-component 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. implemented_live_permissive not_live_reference_or_discard_candidate landed_permissive_preserve phase0r_reference_benchmark_or_discard_eval Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 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.
16 roice3/Magic120Cell https://github.com/roice3/Magic120Cell HyperTwist Locked Strategic Donor Specialized 4D interaction and puzzle-UX donor P1 7464 9219 49.0 122.0 137.0 medium 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 generalized puzzle/state/render logic while building a new application shell around it. repurpose moderate modification Determine whether roice3/Magic120Cell should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. puzzle model, learning flow, UX loops, data schema, replay/export, plugin/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 higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks. Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. 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. 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. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment. MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value. Audit roice3/Magic120Cell 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 moderate modification and whether it belongs as subsystem donor / 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. HT_hyper_engine_0004 HT_hyper_engine roice3/magic120cell 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 3 122.0 permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces. Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior. Preserve MIT notices and attribution where required. Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code. high permissive-specialized-donor yes v6.3_final_source_of_truth Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status. selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet.
17 roice3/MagicCube5D https://github.com/roice3/MagicCube5D HyperTwist Locked Strategic Donor Specialized 5D cube interaction, progress, and macro donor P1 7465 9220 50.0 122.0 137.0 medium 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 generalized puzzle/state/render logic while building a new application shell around it. repurpose moderate modification Determine whether roice3/MagicCube5D should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. puzzle model, learning flow, UX loops, data schema, replay/export, plugin/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 higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks. Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. 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. 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. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment. MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value. Audit roice3/MagicCube5D 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 moderate modification and whether it belongs as subsystem donor / 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. HT_hyper_engine_0005 HT_hyper_engine roice3/magiccube5d 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 3 122.0 permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior. Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior. Preserve MIT notices and attribution where required. Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code. high permissive-specialized-donor yes v6.3_final_source_of_truth Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status. selected_not_live_permissive_candidate implemented_live_permissive phase0r_permissive_eval_then_implement landed_permissive_preserve 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. Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet.
18 aMonteSl/CodeXR https://github.com/aMonteSl/CodeXR HyperTwist Reserve Bench Reference-only XR benchmark P3 7467 9222 51.0 119.0 134.0 medium 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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces. future candidate architecture only Validate that CodeXR remains reference-only and record the specific immersive interaction ideas worth preserving without direct source reuse. Collaboration-room flow, scene launch, virtual screens, and immersive interaction behavior as benchmark material only. Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only. Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source? Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist. Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell. Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in aMonteSl/CodeXR 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code. GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns. Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only. HT_cube_vision_0005 HT_cube_vision amontesl/codexr Original global P0-P3 source audit retained GPL-3.0-only 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 3 119.0 mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows. Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark. high gpl-reference-only-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows.
19 brianpeiris/RiftSketch https://github.com/brianpeiris/RiftSketch HyperTwist Reserve Bench Adjacency / future transfer P2 7468 9223 51.0 119.0 134.0 medium 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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces. future candidate architecture only Determine whether brianpeiris/RiftSketch should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. puzzle model, learning flow, UX loops, data schema, replay/export, plugin/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. Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. 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, Lykos/cube_trainer. Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode 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. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. brianpeiris/RiftSketch is placed in Reserve Bench for HyperTwist because it best serves the 'XR interaction and spatial-UI bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths. Useful MIT WebXR interaction benchmark for spatial editor panels, world-space monitors, and keyboard-first immersive tooling, but explicitly below the HyperTwist core tier. Audit brianpeiris/RiftSketch 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 moderate modification and whether it belongs as subsystem donor / 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_0006 HT_cube_vision brianpeiris/riftsketch 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 3 119.0 permissive_or_noncopyleft_known pattern_only_preferred The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope. Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation. 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 merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope.
20 MathewKJ2048/Rubiks-cube-simulator https://github.com/MathewKJ2048/Rubiks-cube-simulator HyperTwist Reserve Bench Clean-room simulator benchmark P3 7469 9224 51.0 118.0 133.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the lightweight simulator behaviors worth preserving from MathewKJ2048/Rubiks-cube-simulator through a scrubbed clean-room spec. Command grammar, move-history logging, beginner-solver flow, and timed step playback as clean-room benchmark material. Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only. Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only. Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in MathewKJ2048/Rubiks-cube-simulator 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors. GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material. Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0004 HT_training_clean_room mathewkj2048/rubiks-cube-simulator Original global P0-P3 source audit retained GPL-3.0 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 3 118.0 mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks. Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary. high gpl-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.
21 NuiLab/code-vr https://github.com/NuiLab/code-vr HyperTwist Donor Bench XR pedagogy and code-to-scene representation donor P2 7470 9225 51.0 118.0 133.0 medium 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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces. repurpose moderate modification Determine whether NuiLab/code-vr should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. puzzle model, learning flow, UX loops, data schema, replay/export, plugin/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. Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. 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, Lykos/cube_trainer. Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode 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. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell. MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment. Audit NuiLab/code-vr 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 moderate modification and whether it belongs as subsystem donor / 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_0007 HT_cube_vision nuilab/code-vr 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 3 118.0 permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership. Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time. Preserve MIT notices and attribution where required. Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code. high below-core-mit-donor yes v6.3_final_source_of_truth Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status. 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.
22 ShellPuppy/RCube https://github.com/ShellPuppy/RCube HyperTwist Reserve Bench Large-N solver benchmark P3 7471 9226 51.0 118.0 133.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Document the large-N orientation and stage-framing ideas that justify retaining RCube only as a benchmark row. Large-cube orientation logic, stage framing, and solver behavior as benchmark material. Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only. Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge? Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code. Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed. Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in ShellPuppy/RCube 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a restrictive benchmark for large-N state/orientation techniques. GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core. Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code. HT_solver_oracles_0001 HT_solver_oracles shellpuppy/rcube Original global P0-P3 source audit retained GPL-3.0 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 3 118.0 mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use. Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark. high gpl-large-n-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor.
25 newyork-anthonyng/rubiks-cross-trainer https://github.com/newyork-anthonyng/rubiks-cross-trainer HyperTwist Donor Bench Training / timing layer P2 7475 9230 51.0 118.0 133.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. repurpose moderate modification Determine whether newyork-anthonyng/rubiks-cross-trainer should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. 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, Lykos/cube_trainer. 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. 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. project-local first Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. newyork-anthonyng/rubiks-cross-trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths. Focused donor for the precomputed cross-difficulty corpus and CFOP micro-drill progression rather than a broader training-platform shell. Audit newyork-anthonyng/rubiks-cross-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 moderate modification and whether it belongs as subsystem donor / 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) Lykos/cube_trainer [sampling/analytics 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. HT_training_stack_0008 HT_training_stack newyork-anthonyng/rubiks-cross-trainer 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 3 118.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 merge-bench wording to dossier-backed focused-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.
26 vwcwong/CubeSim https://github.com/vwcwong/CubeSim HyperTwist Reserve Bench Clean-room state/history benchmark P3 7476 9231 51.0 118.0 133.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the state/history and replay behaviors worth preserving from vwcwong/CubeSim through a scrubbed clean-room spec. State/history separation, parser/scramble modules, tests, and replay-oriented behavior as clean-room benchmark material. Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only. Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only. Repurpose here means: derive first-party state/history and replay behavior through a clean-room process. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in vwcwong/CubeSim 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a clean-room state/history benchmark for first-party simulator architecture. GPL simulator with unusually clean state/history architecture; retain only as clean-room benchmark material. Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0005 HT_training_clean_room vwcwong/cubesim Original global P0-P3 source audit retained GPL-3.0 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 3 118.0 mixed_or_boundary_sensitive_known reverse_engineer_preferred The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use. Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary. high gpl-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use.
27 AviKaufman/Rubix-cube-trainer https://github.com/AviKaufman/Rubix-cube-trainer HyperTwist Reserve Bench Clean-room pedagogy benchmark P3 7477 9232 52.0 117.0 132.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the teaching-flow and tutorial behaviors worth preserving from AviKaufman/Rubix-cube-trainer through a scrubbed clean-room spec. Beginner-method sequencing, step guidance, and tutorial-state transitions as clean-room benchmark material. Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only. Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only. Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in AviKaufman/Rubix-cube-trainer 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a clean-room pedagogy benchmark for first-party teaching-flow work. All-rights-reserved repo with narrow teaching-flow value; retain only as clean-room benchmark material. Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0003 HT_training_clean_room avikaufman/rubix-cube-trainer Original global P0-P3 source audit retained 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 2 3 117.0 mixed_or_boundary_sensitive_known reverse_engineer_preferred The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications. Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification. Do not incorporate source or assets directly without separate rights. Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary. high all-rights-reserved-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design.
28 alinen/cube https://github.com/alinen/cube HyperTwist Reserve Bench Clean-room planner benchmark P3 7478 9233 52.0 117.0 132.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the planner and guided-lesson behaviors worth preserving from alinen/cube through a scrubbed clean-room spec. Planner flow, guided lessons, cube-state handling, and bounded-search behavior as clean-room benchmark material. Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only. Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only. Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in alinen/cube 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a clean-room planner benchmark for first-party guided-lesson and planner work. No explicit license visible and limited scope; retain only for clean-room planner behavior extraction. Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0001 HT_training_clean_room alinen/cube Original global P0-P3 source audit 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 2 3 117.0 license_unknown_pending reverse_engineer_preferred No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications. Model A may inspect and summarize planner 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 planner or lesson behavior later proves strategically necessary. medium no-license-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room planner benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly.
29 ambisinister/blindsolve https://github.com/ambisinister/blindsolve HyperTwist Reserve Bench Clean-room BLD memo benchmark P3 7479 9234 52.0 117.0 132.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the memo-practice and feedback behaviors worth preserving from blindsolve through a scrubbed clean-room spec. Memo-practice flow, feedback behavior, and narrow training-state transitions as clean-room benchmark material. Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only. Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only. Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in ambisinister/blindsolve 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a clean-room BLD memo benchmark for later first-party micro-mode work. No explicit license visible and extremely narrow scope; retain only as clean-room benchmark material. Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0002 HT_training_clean_room ambisinister/blindsolve Original global P0-P3 source audit 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 2 3 117.0 license_unknown_pending reverse_engineer_preferred No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications. Model A may inspect and summarize memo-practice 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 memo-practice micro-mode later proves strategically necessary. medium no-license-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room BLD memo benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only.
30 efrantar/rob-twophase https://github.com/efrantar/rob-twophase HyperTwist Reserve Bench Solver oracle and robot-metric benchmark P2 7480 9235 52.0 117.0 132.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the correctness, metric, and oracle behaviors that justify keeping rob-twophase only as a benchmark row. Robot metrics, pruning tables, CLI oracle behavior, and multiple-solution search as benchmark material. Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only. Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation? Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code. Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests. Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, or clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in efrantar/rob-twophase 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon as a restrictive solver oracle benchmark with robot-metric value. GPL solver/oracle repo whose retained value is correctness, performance, and metric benchmarking rather than donor use. Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code. HT_solver_oracles_0002 HT_solver_oracles efrantar/rob-twophase Original global P0-P3 source audit retained GPL-3.0 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 3 117.0 mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code. Reference only: use as a solver oracle and robot-metric benchmark without direct source incorporation. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Only if a narrow oracle behavior later needs first-party recreation; otherwise keep this as a benchmark. high gpl-solver-oracle-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed solver oracle benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code.
31 onionhoney/roux-trainers https://github.com/onionhoney/roux-trainers HyperTwist Donor Bench Focused restrictive clean-room donor target P2 7481 9236 52.0 117.0 132.0 medium 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 cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. repurpose architecture only Capture the stage-specific training, analyzer, recognition, and drill-loop behaviors that justify keeping roux-trainers as a clean-room donor target. Stage-specific training flows, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries. Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries. Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff? Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code. Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary. Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process. 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. 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. HyperTwist only Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Model A salvage map + clean-room boundary note + first-party subsystem extraction plan. 1) Which stage-specific subsystems are worth preserving 2) What must stay behind Model A / Model B separation 3) What first-party implementations should replace the GPL source 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. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon as a focused restrictive clean-room donor for method-specific training and analyzer behavior. GPLv3 method-specific trainer with real subsystem value that should be preserved through clean-room extraction rather than donor use. Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only. HT_training_clean_room_0006 HT_training_clean_room onionhoney/roux-trainers Original global P0-P3 source audit retained GPL-3.0 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 3 117.0 mixed_or_boundary_sensitive_known reverse_engineer_preferred The repo is GPLv3 and should not be used as direct donor code in the HyperTwist core. Its value is in selective behavior and subsystem extraction through a clean-room Model A / Model B process. Model A inspects the restrictive source; Model B implements only from a scrubbed first-party specification and must not access the repo directly. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Yes — preferred path for selectively reproducing stage-specific training and analyzer behavior in first-party code. high gpl-clean-room-donor no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed focused restrictive clean-room donor status. implemented_live_clean_room_verified landed_clean_room_preserve Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs.
90
91
92
93
94
95
96
111
112
113
114
115
116
117
120
121
122
123
124
125
126
228
229
230
231
232
233
234