|
|
|
|
@ -1,5 +1,5 @@
|
|
|
|
|
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
|
|
|
|
|
HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,Locked Foundation,nD / hypercubing simulation substrate,P0,20,9203,2.0,160.0,193.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.",integrate,direct,"Validate whether HactarCE/Hyperspeedcube truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","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 cubing/cubing.js, then into tao-yu/Alg-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: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,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.,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
|
|
|
|
|
"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"
|
|
|
|
|
"HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","HyperTwist","Locked Foundation","nD / hypercubing simulation substrate","P0","20","9203","2.0","160.0","193.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.","integrate","direct","Validate whether HactarCE/Hyperspeedcube truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","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 cubing/cubing.js, then into tao-yu/Alg-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: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","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.","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
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -7,8 +7,8 @@ HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,Lo
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -16,8 +16,8 @@ kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,Locked Foundation,Live cub
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -25,8 +25,8 @@ vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -34,8 +34,8 @@ tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,Locked Paral
|
|
|
|
|
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.","tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.,"Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0001,HT_training_stack,tao-yu/alg-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,1,156.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work.
|
|
|
|
|
cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,Locked Strategic Donor,Boundary-sensitive classic-cubing semantics and rendering donor,P1,24,9207,7.0,152.0,185.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,"Validate whether cubing/cubing.js truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.",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 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
|
|
|
|
|
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.","tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0001","HT_training_stack","tao-yu/alg-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","1","156.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
|
|
|
|
|
"cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","Locked Strategic Donor","Boundary-sensitive classic-cubing semantics and rendering donor","P1","24","9207","7.0","152.0","185.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","Validate whether cubing/cubing.js truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.","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 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
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -43,10 +43,10 @@ cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,Locked Strategic
|
|
|
|
|
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 the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_semantics_0001,HT_cube_semantics,cubing/cubing.js,,,,,,,Original global P0-P3 source audit retained,MPL-2.0 OR GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,2,1,152.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.",Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.,Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.,Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.,high,dual-license-boundary-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable.
|
|
|
|
|
cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,25,9208,0.0,95.0,95.0,medium,"Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.",repurpose,architecture only,"Determine the real reusable value of cubing/alg.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Audit for hidden abstractions that travel across projects.,"Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.",Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.,Use v6 unified board + P0 tier packet + project design language + relevant family references.,"Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.",Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.,"Inspect cubing/alg.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.",HT_cube_semantics_0002,HT_cube_semantics,cubing/alg.js,supplemental_v6_not_runtime_anchored,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2,1,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract.
|
|
|
|
|
cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,27,9210,0.0,95.0,95.0,medium,"Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.",repurpose,architecture only,"Determine the real reusable value of cubing/twisty.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Audit for hidden abstractions that travel across projects.,"Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.",Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.,Use v6 unified board + P0 tier packet + project design language + relevant family references.,Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.,Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.,"Inspect cubing/twisty.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.",HT_cube_semantics_0003,HT_cube_semantics,cubing/twisty.js,supplemental_v6_not_runtime_anchored,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2,1,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract.
|
|
|
|
|
cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,Locked Strategic Donor,Vision / reconstruction donor layer,P1,55,9211,4.0,148.0,174.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",integrate,direct,"Confirm the donor thesis for cahidenes/rubiks-cube-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities
|
|
|
|
|
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_semantics_0001","HT_cube_semantics","cubing/cubing.js","","","","","","","Original global P0-P3 source audit retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","2","1","152.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable."
|
|
|
|
|
"cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","25","9208","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/alg.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.","Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.","Inspect cubing/alg.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0002","HT_cube_semantics","cubing/alg.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract."
|
|
|
|
|
"cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","27","9210","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/twisty.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.","Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.","Inspect cubing/twisty.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0003","HT_cube_semantics","cubing/twisty.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract."
|
|
|
|
|
"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","Vision / reconstruction donor layer","P1","55","9211","4.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the donor thesis for cahidenes/rubiks-cube-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
|
|
|
|
|
2) Hidden capabilities found only in source
|
|
|
|
|
3) Best salvageable modules/files/packages
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -54,8 +54,8 @@ cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,Hyp
|
|
|
|
|
6) Best merge partners and exact coupling seam
|
|
|
|
|
7) Reasons to promote / retain / demote
|
|
|
|
|
8) Confidence change after source audit
|
|
|
|
|
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0003,HT_cube_vision,cahidenes/rubiks-cube-solver,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
|
|
|
|
|
tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,Locked Strategic Donor,Vision / reconstruction donor layer,P1,56,9212,5.0,148.0,174.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",integrate,direct,"Confirm the donor thesis for tentone/rubix-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities
|
|
|
|
|
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0003","HT_cube_vision","cahidenes/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
|
|
|
|
|
"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","Vision / reconstruction donor layer","P1","56","9212","5.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the donor thesis for tentone/rubix-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
|
|
|
|
|
2) Hidden capabilities found only in source
|
|
|
|
|
3) Best salvageable modules/files/packages
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -63,8 +63,8 @@ tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,Locked S
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
@ -72,8 +72,8 @@ Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,Locked Strat
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
@ -81,8 +81,8 @@ kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,Locked Strategic Donor
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
@ -90,11 +90,11 @@ poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,Locked Strategic Don
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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.
|
|
|
|
|
cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,Locked Strategic Donor,"Top-tier 4D interaction, history, and macro donor with attribution obligations",P1,7463,9218,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 cutelyaware/magiccube4d 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
|
|
|
|
|
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."
|
|
|
|
|
"cutelyaware/magiccube4d","https://github.com/cutelyaware/magiccube4d/tree/master","HyperTwist","Locked Strategic Donor","Top-tier 4D interaction, history, and macro donor with attribution obligations","P1","7463","9218","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 cutelyaware/magiccube4d 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
|
|
|
|
|
@ -102,8 +102,8 @@ cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,H
|
|
|
|
|
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 one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.",Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.,"Audit cutelyaware/magiccube4d 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_0003,HT_hyper_engine,cutelyaware/magiccube4d,,,,,,,Original global P0-P3 source audit retained,Custom broad-use license with attribution requested,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,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.",Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.,"Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.",Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.,medium,custom-license-attribution-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly.
|
|
|
|
|
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
|
|
|
|
|
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 one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.","Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.","Audit cutelyaware/magiccube4d 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_0003","HT_hyper_engine","cutelyaware/magiccube4d","","","","","","","Original global P0-P3 source audit retained","Custom broad-use license with attribution requested","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","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.","Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.","Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.","Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.","medium","custom-license-attribution-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly."
|
|
|
|
|
"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
|
|
|
|
|
@ -111,8 +111,8 @@ roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,Locked Str
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
@ -120,11 +120,11 @@ roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,Locked Strat
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
@ -132,11 +132,11 @@ brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,Rese
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
@ -144,11 +144,11 @@ NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,Donor Bench,XR pedag
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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."
|
|
|
|
|
abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,Donor Bench,Training / timing layer,P2,7472,9227,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 abunickabhi/5style-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
|
|
|
|
|
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."
|
|
|
|
|
"abunickabhi/5style-Trainer","https://github.com/abunickabhi/5style-Trainer","HyperTwist","Donor Bench","Training / timing layer","P2","7472","9227","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 abunickabhi/5style-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
|
|
|
|
|
@ -156,8 +156,8 @@ abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTw
|
|
|
|
|
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.","abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training 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 advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.","Audit abunickabhi/5style-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_0006,HT_training_stack,abunickabhi/5style-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 advanced-training 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.
|
|
|
|
|
brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,Reserve Bench,Benchmark oracle and clean-room optimal-solver candidate,P2,7473,9228,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,"Determine whether brownan/Rubiks-Cube-Solver 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 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
|
|
|
|
|
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.","abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training 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 advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.","Audit abunickabhi/5style-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_0006","HT_training_stack","abunickabhi/5style-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 advanced-training 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."
|
|
|
|
|
"brownan/Rubiks-Cube-Solver","https://github.com/brownan/Rubiks-Cube-Solver","HyperTwist","Reserve Bench","Benchmark oracle and clean-room optimal-solver candidate","P2","7473","9228","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","Determine whether brownan/Rubiks-Cube-Solver 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 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
|
|
|
|
|
@ -165,8 +165,8 @@ brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTw
|
|
|
|
|
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 primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.,GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.,"Audit brownan/Rubiks-Cube-Solver 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_0007,HT_training_stack,brownan/rubiks-cube-solver,,,,,,,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-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for any later first-party optimal-solver effort.,high,gpl-oracle-clean-room-review,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code."
|
|
|
|
|
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
|
|
|
|
|
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 primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.","GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.","Audit brownan/Rubiks-Cube-Solver 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_0007","HT_training_stack","brownan/rubiks-cube-solver","","","","","","","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-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.","Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for any later first-party optimal-solver effort.","high","gpl-oracle-clean-room-review","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code."
|
|
|
|
|
"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
|
|
|
|
|
@ -174,26 +174,26 @@ newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubi
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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.
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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.
|
|
|
|
|
yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,Reserve Bench,Adjacency / future transfer,P2,7482,9237,53.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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",future candidate,architecture only,"Determine whether yakupbilen/drl-rubiks-cube 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
|
|
|
|
|
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."
|
|
|
|
|
"yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","Reserve Bench","Adjacency / future transfer","P2","7482","9237","53.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 calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","future candidate","architecture only","Determine whether yakupbilen/drl-rubiks-cube 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
|
|
|
|
|
@ -201,8 +201,8 @@ yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTw
|
|
|
|
|
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.","yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems 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 search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.","Audit yakupbilen/drl-rubiks-cube 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_0008,HT_cube_vision,yakupbilen/drl-rubiks-cube,,,,,,,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,117.0,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.",Reference only: benchmark learned heuristic search and training experiments without near-term 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. 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,Knowledge and curriculum donor,P1,7483,9238,1.0,92.0,101.0,medium,"Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. 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 Hypercubers/hypercubing.xyz 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.,"Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","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
|
|
|
|
|
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.","yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems 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 search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.","Audit yakupbilen/drl-rubiks-cube 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_0008","HT_cube_vision","yakupbilen/drl-rubiks-cube","","","","","","","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","117.0","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.","Reference only: benchmark learned heuristic search and training experiments without near-term 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. 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","Knowledge and curriculum donor","P1","7483","9238","1.0","92.0","101.0","medium","Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. 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 Hypercubers/hypercubing.xyz 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.","Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","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
|
|
|
|
|
@ -210,8 +210,8 @@ Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,Hyper
|
|
|
|
|
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 one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.,"MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.","Audit Hypercubers/hypercubing.xyz 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 heavy 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_0006,HT_hyper_engine,hypercubers/hypercubing.xyz,,,,,,,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,92.0,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.,"Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.",Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.,high,permissive-knowledge-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.,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,Adjacency / future transfer,P2,7485,9240,2.0,88.0,97.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 Aarav2709/KubeTimr 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 cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","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
|
|
|
|
|
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 one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.","MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.","Audit Hypercubers/hypercubing.xyz 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 heavy 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_0006","HT_hyper_engine","hypercubers/hypercubing.xyz","","","","","","","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","92.0","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.","Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.","high","permissive-knowledge-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.","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","Adjacency / future transfer","P2","7485","9240","2.0","88.0","97.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 Aarav2709/KubeTimr 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 cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","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
|
|
|
|
|
@ -219,8 +219,8 @@ Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,Donor Bench,
|
|
|
|
|
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.","Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem 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.","Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.","Audit Aarav2709/KubeTimr 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_0015,HT_training_stack,aarav2709/kubetimr,,,,,,,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,"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.","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,routine-review-only,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.,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,Top-tier non-Euclidean geometry and topology donor,P1,7487,9242,2.0,88.0,97.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 collectors/adapters/runtime topology logic while integrating into a larger control plane.",repurpose,moderate modification,"Determine whether roice3/MagicTile 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 topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","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.",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.,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
|
|
|
|
|
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.","Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem 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.","Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.","Audit Aarav2709/KubeTimr 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_0015","HT_training_stack","aarav2709/kubetimr","","","","","","","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","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.","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","routine-review-only","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.","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","Top-tier non-Euclidean geometry and topology donor","P1","7487","9242","2.0","88.0","97.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 collectors/adapters/runtime topology logic while integrating into a larger control plane.","repurpose","moderate modification","Determine whether roice3/MagicTile 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 topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","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.","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.","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
|
|
|
|
|
@ -228,8 +228,8 @@ roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,Locked Strategic
|
|
|
|
|
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."
|
|
|
|
|
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
|
|
|
|
|
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."
|
|
|
|
|
"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
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -237,9 +237,9 @@ PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,Donor Bench,Adjace
|
|
|
|
|
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.","PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.","Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.",HT_control_plane_0001,HT_control_plane,posthog/posthog,,,,,,,Original global P0-P3 source audit retained,MIT outside ee/; enterprise-restricted in ee/,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,72.0,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.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.",Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.,"Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed.
|
|
|
|
|
HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,7496,9251,2.0,63.0,63.0,low-to-medium,"Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.",repurpose,architecture only,"Determine the real reusable value of HactarCE/2x2x2x2-Scrambler 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 HactarCE/2x2x2x2-Scrambler 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 HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use HactarCE/2x2x2x2-Scrambler 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 + P2 tier packet + project design language + relevant family references.,"Keep as a narrow but real clean-room donor for Melinda 2x2x2x2 state encoding, handedness/parity repair, random-state generation, move-family representation, and flat debug/teaching views.","GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.","Inspect HactarCE/2x2x2x2-Scrambler directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.",HT_cube_semantics_0004,HT_cube_semantics,hactarce/2x2x2x2-scrambler,supplemental_v6_not_runtime_anchored,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2,3,63.0,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.,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 — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors 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 Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier.
|
|
|
|
|
SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8351,10345,49.0,71.0,80.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 parsers/graph schema/indexing while swapping layout, storage, or UX layers.",repurpose,moderate modification,"Determine whether SYSTRAN/faster-whisper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","STT API surface, VAD chunking, batch inference, timestamps, service boundaries, model/runtime constraints, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.",Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.,"Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.",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.,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
|
|
|
|
|
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.","PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.","Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.","HT_control_plane_0001","HT_control_plane","posthog/posthog","","","","","","","Original global P0-P3 source audit retained","MIT outside ee/; enterprise-restricted in ee/","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","72.0","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.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.","Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed."
|
|
|
|
|
"HactarCE/2x2x2x2-Scrambler","https://github.com/HactarCE/2x2x2x2-Scrambler","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","7496","9251","2.0","63.0","63.0","low-to-medium","Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","repurpose","architecture only","Determine the real reusable value of HactarCE/2x2x2x2-Scrambler 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 HactarCE/2x2x2x2-Scrambler 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 HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use HactarCE/2x2x2x2-Scrambler 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 + P2 tier packet + project design language + relevant family references.","Keep as a narrow but real clean-room donor for Melinda 2x2x2x2 state encoding, handedness/parity repair, random-state generation, move-family representation, and flat debug/teaching views.","GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.","Inspect HactarCE/2x2x2x2-Scrambler directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0004","HT_cube_semantics","hactarce/2x2x2x2-scrambler","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","3","63.0","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.","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 — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors 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 Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier."
|
|
|
|
|
"SYSTRAN/faster-whisper","https://github.com/SYSTRAN/faster-whisper","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8351","10345","49.0","71.0","80.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 parsers/graph schema/indexing while swapping layout, storage, or UX layers.","repurpose","moderate modification","Determine whether SYSTRAN/faster-whisper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","STT API surface, VAD chunking, batch inference, timestamps, service boundaries, model/runtime constraints, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.","Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.","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.","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
|
|
|
|
|
@ -247,8 +247,8 @@ SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,D
|
|
|
|
|
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.","SYSTRAN/faster-whisper is placed in Donor Bench for multi-project because it provides the clearest Python STT service-layer path in the voice stack. Recommended action remains repurpose, but the real retained value is batch transcription, VAD-aware chunking, timestamps, and Python-side service integration rather than any code-intelligence or graph role.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current Python STT donor and service-layer candidate in the voice stack.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",MU_misc_0001,MU_misc,systran/faster-whisper,,,,,,,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.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,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.",Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.,"Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.",Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.,high,model-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,,
|
|
|
|
|
coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8352,10346,49.0,71.0,80.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 streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",repurpose,moderate modification,"Determine whether coqui-ai/TTS should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","API surface, synthesis orchestration, multilingual and speaker handling, voice conversion, model registry, deployment boundary, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.",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.","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
|
|
|
|
|
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.","SYSTRAN/faster-whisper is placed in Donor Bench for multi-project because it provides the clearest Python STT service-layer path in the voice stack. Recommended action remains repurpose, but the real retained value is batch transcription, VAD-aware chunking, timestamps, and Python-side service integration rather than any code-intelligence or graph role.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current Python STT donor and service-layer candidate in the voice stack.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","MU_misc_0001","MU_misc","systran/faster-whisper","","","","","","","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.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","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.","Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.","Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.","high","model-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","",""
|
|
|
|
|
"coqui-ai/TTS","https://github.com/coqui-ai/TTS","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8352","10346","49.0","71.0","80.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 streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","repurpose","moderate modification","Determine whether coqui-ai/TTS should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","API surface, synthesis orchestration, multilingual and speaker handling, voice conversion, model registry, deployment boundary, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.","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.","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
|
|
|
|
|
@ -256,8 +256,8 @@ coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,Donor Bench,Cross-pro
|
|
|
|
|
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.","coqui-ai/TTS is placed in Donor Bench for multi-project because it provides the richest current voice-output and coaching architecture in the stack. Recommended action remains repurpose, but the real retained value is synthesis orchestration, multilingual and speaker handling, XTTS/voice-conversion paths, and model-registry discipline rather than broad assistant scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current voice and coaching donor, but boundary-sensitive because code and model payload licensing must be separated.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",MU_misc_0002,MU_misc,coqui-ai/tts,,,,,,,Original global P0-P3 source audit retained,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,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.",Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.,"Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.",Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.,medium,model-license-selection-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,,
|
|
|
|
|
ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8353,10347,49.0,71.0,80.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 streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",repurpose,moderate modification,"Determine whether ggml-org/whisper.cpp should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","native STT runtime seam, VAD, grammar-constrained decoding, server boundary, portability, hidden modules","Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.",Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.,"Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.",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.","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
|
|
|
|
|
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.","coqui-ai/TTS is placed in Donor Bench for multi-project because it provides the richest current voice-output and coaching architecture in the stack. Recommended action remains repurpose, but the real retained value is synthesis orchestration, multilingual and speaker handling, XTTS/voice-conversion paths, and model-registry discipline rather than broad assistant scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current voice and coaching donor, but boundary-sensitive because code and model payload licensing must be separated.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","MU_misc_0002","MU_misc","coqui-ai/tts","","","","","","","Original global P0-P3 source audit retained","MPL-2.0 code; mixed model payload licenses","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","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.","Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.","Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.","Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.","medium","model-license-selection-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","",""
|
|
|
|
|
"ggml-org/whisper.cpp","https://github.com/ggml-org/whisper.cpp","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8353","10347","49.0","71.0","80.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 streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","repurpose","moderate modification","Determine whether ggml-org/whisper.cpp should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","native STT runtime seam, VAD, grammar-constrained decoding, server boundary, portability, hidden modules","Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.","Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.","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.","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
|
|
|
|
|
@ -265,8 +265,8 @@ ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,Donor
|
|
|
|
|
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.","ggml-org/whisper.cpp is placed in Donor Bench for multi-project because it is the clearest native/offline STT anchor in the voice stack. Recommended action remains repurpose, but the real retained value is a bounded speech-input runtime, VAD, grammar-constrained decoding, and portable deployment rather than a full product shell.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current native/offline STT sidecar candidate in the voice stack.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",MU_misc_0003,MU_misc,ggml-org/whisper.cpp,,,,,,,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.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,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.,"Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.",Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.,high,model-artifact-review-recommended,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.,,,
|
|
|
|
|
rhasspy/piper,https://github.com/rhasspy/piper,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8354,10348,49.0,71.0,80.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 streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",repurpose,moderate modification,"Determine whether rhasspy/piper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","local TTS runtime seam, ONNX and eSpeak integration, streaming output, HTTP service boundary, voice catalog, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.",Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.,"Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.",Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.,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.","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
|
|
|
|
|
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.","ggml-org/whisper.cpp is placed in Donor Bench for multi-project because it is the clearest native/offline STT anchor in the voice stack. Recommended action remains repurpose, but the real retained value is a bounded speech-input runtime, VAD, grammar-constrained decoding, and portable deployment rather than a full product shell.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current native/offline STT sidecar candidate in the voice stack.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","MU_misc_0003","MU_misc","ggml-org/whisper.cpp","","","","","","","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.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","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.","Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.","Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.","high","model-artifact-review-recommended","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.","","",""
|
|
|
|
|
"rhasspy/piper","https://github.com/rhasspy/piper","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8354","10348","49.0","71.0","80.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 streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","repurpose","moderate modification","Determine whether rhasspy/piper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","local TTS runtime seam, ONNX and eSpeak integration, streaming output, HTTP service boundary, voice catalog, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.","Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.","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.","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
|
|
|
|
|
@ -274,39 +274,39 @@ rhasspy/piper,https://github.com/rhasspy/piper,multi-project,Donor Bench,Cross-p
|
|
|
|
|
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.","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",MU_misc_0004,MU_misc,rhasspy/piper,,,,,,,Original global P0-P3 source audit retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.,"Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.",Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.,high,voice-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,,
|
|
|
|
|
met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,Browser embodied coach surface,P2,,,,,,medium,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",repurpose,moderate modification,Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.,"avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.",Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",HT_browser_surface_0001,HT_browser_surface,met4citizen/talkinghead,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,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.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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,Browser analytics and reporting surface,P2,,,,,,medium,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",repurpose,moderate modification,Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces.,"option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",HT_browser_surface_0002,HT_browser_surface,apache/echarts,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,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.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,Merge Bench,Browser 3D analytics and explainer surface,P3,,,,,,medium,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",integrate,moderate modification,Determine whether echarts-gl should remain the bounded 3D analytics extension beneath echarts and what should stay outside HyperTwist core.,"3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",HT_browser_surface_0003,HT_browser_surface,ecomfe/echarts-gl,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live."
|
|
|
|
|
KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,Donor Bench,Browser asset validation and viewer surface,P3,,,,,,medium,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",repurpose,moderate modification,Determine whether glTF-Sample-Viewer should remain the primary standards-validation viewer donor for browser asset tooling.,"validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",HT_browser_surface_0004,HT_browser_surface,khronosgroup/gltf-sample-viewer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
google/model-viewer,https://github.com/google/model-viewer,HyperTwist,Donor Bench,Browser 3D presentation and inspection surface,P2,,,,,,medium,"Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.",repurpose,moderate modification,Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces.,"custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.",,"Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.",HT_browser_surface_0005,HT_browser_surface,google/model-viewer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,"Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.",Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md."
|
|
|
|
|
mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,Donor Bench,Browser 3D substrate,P2,,,,,,medium,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,repurpose,moderate modification,Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces.,"renderer, scene, camera, math core, loaders, WebXR manager, addons, editor","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",HT_browser_surface_0006,HT_browser_surface,mrdoob/three.js,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,Merge Bench,Browser post-processing substrate,P3,,,,,,medium,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",integrate,moderate modification,Determine whether postprocessing should remain the bounded browser effect-composer substrate beneath the companion stack.,"EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",HT_browser_surface_0007,HT_browser_surface,pmndrs/postprocessing,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,Donor Bench,Browser React 3D substrate,P2,,,,,,medium,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",repurpose,moderate modification,Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes.,"Canvas, createRoot, reconciler runtime, event system, hooks, native path","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",HT_browser_surface_0008,HT_browser_surface,pmndrs/react-three-fiber,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,Merge Bench,Browser 3D helper and abstraction layer,P3,,,,,,medium,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,integrate,moderate modification,Determine which drei helpers should remain active merge candidates for browser companion surfaces and which should be ignored as generic convenience.,"Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",HT_browser_surface_0009,HT_browser_surface,pmndrs/drei,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,Donor Bench,Browser XR and immersive UI substrate,P2,,,,,,medium,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",repurpose,moderate modification,Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces.,"XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",HT_browser_surface_0010,HT_browser_surface,pmndrs/xr,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,Donor Bench,Browser spatial UI surface,P2,,,,,,medium,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",repurpose,moderate modification,Determine whether pmndrs/uikit should remain the default browser spatial UI donor for HyperTwist companion surfaces.,"flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",HT_browser_surface_0011,HT_browser_surface,pmndrs/uikit,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,Merge Bench,Browser motion and animation layer,P3,,,,,,medium,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",integrate,moderate modification,Determine which react-spring motion surfaces should remain active merge candidates for browser companion views.,"Controller and SpringValue runtime, scheduler, layered explainer behavior, browser motion ergonomics","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",HT_browser_surface_0012,HT_browser_surface,pmndrs/react-spring,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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."
|
|
|
|
|
screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,Donor Bench,"Support-plane capture, history, and replay sidecar",P2,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,"Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_support_sidecars_0001,HT_support_sidecars,screenpipe/screenpipe,,,,,,,,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.,Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.,Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.,"Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted."
|
|
|
|
|
remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,Donor Bench,Commercially licensed media-export and explainer sidecar,P2,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.,"player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_support_sidecars_0002,HT_support_sidecars,remotion-dev/remotion,,,,,,,,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.,Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.,Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.,Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.,high,commercial-license-sidecar-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use.
|
|
|
|
|
ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,Merge Bench,Browser 2D render substrate,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether ecomfe/zrender should remain active in the Browser 2D render substrate lane and which seams should stay bounded.,"scene graph, canvas and SVG painters, event handling, animation primitives","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0001,HT_browser_support,ecomfe/zrender,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live."
|
|
|
|
|
pissang/claygl,https://github.com/pissang/claygl,HyperTwist,Merge Bench,Browser WebGL substrate,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pissang/claygl should remain active in the Browser WebGL substrate lane and which seams should stay bounded.,"renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0002,HT_browser_support,pissang/claygl,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,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."
|
|
|
|
|
pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,Merge Bench,Browser viewer and editor sidecar,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pissang/clay-viewer should remain active in the Browser viewer and editor sidecar lane and which seams should stay bounded.,"viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0003,HT_browser_support,pissang/clay-viewer,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,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."
|
|
|
|
|
KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,Merge Bench,Browser asset renderer substrate,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether KhronosGroup/glTF-Sample-Renderer should remain active in the Browser asset renderer substrate lane and which seams should stay bounded.,"GltfView, GltfState, resource loader, user camera, renderer core","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0004,HT_browser_support,khronosgroup/gltf-sample-renderer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live."
|
|
|
|
|
google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,Merge Bench,Browser asset editor and inspection surface,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/space-opera should remain active in the Browser asset editor and inspection surface lane and which seams should stay bounded.,"editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0005,HT_browser_support,google/model-viewer/packages/space-opera,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,Merge Bench,Browser fidelity QA harness,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/render-fidelity-tools should remain active in the Browser fidelity QA harness lane and which seams should stay bounded.,"golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0006,HT_browser_support,google/model-viewer/packages/render-fidelity-tools,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,Merge Bench,Browser emphasis and post-processing extension,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/model-viewer-effects should remain active in the Browser emphasis and post-processing extension lane and which seams should stay bounded.,"effect composer integration, outline, SSAO, emphasis behavior, custom-element surface","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0007,HT_browser_support,google/model-viewer/packages/model-viewer-effects,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,Merge Bench,Browser docs and demo surface,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/modelviewer.dev should remain active in the Browser docs and demo surface lane and which seams should stay bounded.,"live docs generation, snippet-to-demo coupling, sidebar and HTML generation","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0008,HT_browser_support,google/model-viewer/packages/modelviewer.dev,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner."
|
|
|
|
|
google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,Donor Bench,Boundary-sensitive sample-asset and test-fixture pack,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",repurpose,architecture only,Determine whether google/model-viewer/packages/shared-assets should remain active in the Browser sample-asset and fixture pack lane and which seams should stay bounded.,"asset provenance, attribution terms, environment fixtures, sample models, fetch script behavior","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.","Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0009,HT_browser_support,google/model-viewer/packages/shared-assets,,,,,,,,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.,Preserve container notices and review each selected asset attribution or usage condition separately before shipping.,"Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.",high,mixed-asset-whitelist-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use.
|
|
|
|
|
pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,Merge Bench,Browser React effect-wrapper layer,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/react-postprocessing should remain active in the Browser React effect-wrapper layer lane and which seams should stay bounded.,"React EffectComposer orchestration, selection model, wrapper ergonomics","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0010,HT_browser_support,pmndrs/react-postprocessing,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,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."
|
|
|
|
|
pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,Merge Bench,Browser 3D utility substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/three-stdlib should remain active in the Browser 3D utility substrate lane and which seams should stay bounded.,"controls, loaders, WebXR helpers, post-processing helpers, utility exports","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0011,HT_browser_support,pmndrs/three-stdlib,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,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."
|
|
|
|
|
pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,Merge Bench,Browser math-helper substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/maath should remain active in the Browser math-helper substrate lane and which seams should stay bounded.,"easing and damp functions, random helpers, geometry utilities","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0012,HT_browser_support,pmndrs/maath,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,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."
|
|
|
|
|
pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,Donor Bench,Browser state-management substrate,P3,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether pmndrs/zustand should remain active in the Browser state-management substrate lane and which seams should stay bounded.,"vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0013,HT_browser_support,pmndrs/zustand,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,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."
|
|
|
|
|
pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,Merge Bench,Browser control-panel and parameter UI layer,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/leva should remain active in the Browser control-panel and parameter UI layer lane and which seams should stay bounded.,"control store, schema parsing, useControls, plugin system, headless mode","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0014,HT_browser_support,pmndrs/leva,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,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."
|
|
|
|
|
pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,Donor Bench,Browser gesture and pointer-input substrate,P3,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether pmndrs/use-gesture should remain active in the Browser gesture and pointer-input substrate lane and which seams should stay bounded.,"gesture controller, drag engine, pointer capture, scroll prevention, React and vanilla bindings","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0015,HT_browser_support,pmndrs/use-gesture,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,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."
|
|
|
|
|
@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,Merge Bench,Browser layered-motion and explainer sidecar,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/parallax should remain active in the Browser layered-motion and explainer sidecar lane and which seams should stay bounded.,"layered page-space runtime, sticky layers, scroll-driven spring behavior, scrollTo","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0016,HT_browser_support,@react-spring/parallax,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,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."
|
|
|
|
|
@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,Merge Bench,Browser frame-loop and scheduling utility,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/rafz should remain active in the Browser frame-loop and scheduling utility lane and which seams should stay bounded.,"phased queues, timeout scheduling, throttling, demand versus always loop control","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0017,HT_browser_support,@react-spring/rafz,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,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."
|
|
|
|
|
@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,Merge Bench,Browser animatable-component substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/animated should remain active in the Browser animatable-component substrate lane and which seams should stay bounded.,"host creation, animated wrapper behavior, dependency observation, native-update fallback","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0018,HT_browser_support,@react-spring/animated,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,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."
|
|
|
|
|
@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,Donor Bench,Browser spring-runtime core,P3,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether @react-spring/core should remain active in the Browser spring-runtime core lane and which seams should stay bounded.,"controller orchestration, SpringValue runtime, useSprings lifecycle, frame advancement","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0019,HT_browser_support,@react-spring/core,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,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."
|
|
|
|
|
@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,Merge Bench,Browser motion utility substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/shared should remain active in the Browser motion utility substrate lane and which seams should stay bounded.,"globals customization, frame loop, interpolation helpers, fluid observer substrate","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0020,HT_browser_support,@react-spring/shared,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,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."
|
|
|
|
|
@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,Merge Bench,Browser motion type-contract substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/types should remain active in the Browser motion type-contract substrate lane and which seams should stay bounded.,"shared type contracts, animatable types, interpolation types, utility types","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0021,HT_browser_support,@react-spring/types,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,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.","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","MU_misc_0004","MU_misc","rhasspy/piper","","","","","","","Original global P0-P3 source audit retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.","Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.","Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.","high","voice-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","",""
|
|
|
|
|
"met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","Donor Bench","Browser embodied coach surface","P2","","","","","","medium","Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.","repurpose","moderate modification","Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.","avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.","","Repurpose here means: turn it into a browser-side embodied coach or companion layer.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.","HT_browser_surface_0001","HT_browser_surface","met4citizen/talkinghead","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","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.","Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","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","Browser analytics and reporting surface","P2","","","","","","medium","Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.","repurpose","moderate modification","Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces.","option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.","","Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.","HT_browser_surface_0002","HT_browser_surface","apache/echarts","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","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.","Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","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."
|
|
|
|
|
"ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","Merge Bench","Browser 3D analytics and explainer surface","P3","","","","","","medium","Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.","integrate","moderate modification","Determine whether echarts-gl should remain the bounded 3D analytics extension beneath echarts and what should stay outside HyperTwist core.","3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.","","Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.","HT_browser_surface_0003","HT_browser_surface","ecomfe/echarts-gl","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live."
|
|
|
|
|
"KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","Donor Bench","Browser asset validation and viewer surface","P3","","","","","","medium","Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.","repurpose","moderate modification","Determine whether glTF-Sample-Viewer should remain the primary standards-validation viewer donor for browser asset tooling.","validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.","","Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.","HT_browser_surface_0004","HT_browser_surface","khronosgroup/gltf-sample-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer","https://github.com/google/model-viewer","HyperTwist","Donor Bench","Browser 3D presentation and inspection surface","P2","","","","","","medium","Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.","repurpose","moderate modification","Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces.","custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.","","Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.","HT_browser_surface_0005","HT_browser_surface","google/model-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.","Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md."
|
|
|
|
|
"mrdoob/three.js","https://github.com/mrdoob/three.js","HyperTwist","Donor Bench","Browser 3D substrate","P2","","","","","","medium","Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.","repurpose","moderate modification","Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces.","renderer, scene, camera, math core, loaders, WebXR manager, addons, editor","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.","","Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.","HT_browser_surface_0006","HT_browser_surface","mrdoob/three.js","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.","Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md."
|
|
|
|
|
"pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","Merge Bench","Browser post-processing substrate","P3","","","","","","medium","Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.","integrate","moderate modification","Determine whether postprocessing should remain the bounded browser effect-composer substrate beneath the companion stack.","EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.","","Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.","HT_browser_surface_0007","HT_browser_surface","pmndrs/postprocessing","","","","","","","","Zlib","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.","Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser post-effect substrate beneath the landed browser spatial owner trio; do not treat it as separately live."
|
|
|
|
|
"pmndrs/react-three-fiber","https://github.com/pmndrs/react-three-fiber","HyperTwist","Donor Bench","Browser React 3D substrate","P2","","","","","","medium","Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.","repurpose","moderate modification","Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes.","Canvas, createRoot, reconciler runtime, event system, hooks, native path","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.","","Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.","HT_browser_surface_0008","HT_browser_surface","pmndrs/react-three-fiber","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.","Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md."
|
|
|
|
|
"pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","Merge Bench","Browser 3D helper and abstraction layer","P3","","","","","","medium","Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.","integrate","moderate modification","Determine which drei helpers should remain active merge candidates for browser companion surfaces and which should be ignored as generic convenience.","Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.","","Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.","HT_browser_surface_0009","HT_browser_surface","pmndrs/drei","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"pmndrs/xr","https://github.com/pmndrs/xr","HyperTwist","Donor Bench","Browser XR and immersive UI substrate","P2","","","","","","medium","Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.","repurpose","moderate modification","Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces.","XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.","","Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.","HT_browser_surface_0010","HT_browser_surface","pmndrs/xr","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.","Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md."
|
|
|
|
|
"pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","Donor Bench","Browser spatial UI surface","P2","","","","","","medium","Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.","repurpose","moderate modification","Determine whether pmndrs/uikit should remain the default browser spatial UI donor for HyperTwist companion surfaces.","flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.","","Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.","HT_browser_surface_0011","HT_browser_surface","pmndrs/uikit","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser spatial UI layer beside the landed pmndrs/xr lane; do not treat it as separately live."
|
|
|
|
|
"pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","Merge Bench","Browser motion and animation layer","P3","","","","","","medium","Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.","integrate","moderate modification","Determine which react-spring motion surfaces should remain active merge candidates for browser companion views.","Controller and SpringValue runtime, scheduler, layered explainer behavior, browser motion ergonomics","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.","","Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.","HT_browser_surface_0012","HT_browser_surface","pmndrs/react-spring","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side motion substrate inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","Donor Bench","Support-plane capture, history, and replay sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0001","HT_support_sidecars","screenpipe/screenpipe","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted."
|
|
|
|
|
"remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","Donor Bench","Commercially licensed media-export and explainer sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.","player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0002","HT_support_sidecars","remotion-dev/remotion","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use."
|
|
|
|
|
"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","Browser 2D render substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether ecomfe/zrender should remain active in the Browser 2D render substrate lane and which seams should stay bounded.","scene graph, canvas and SVG painters, event handling, animation primitives","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0001","HT_browser_support","ecomfe/zrender","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live."
|
|
|
|
|
"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Browser WebGL substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pissang/claygl should remain active in the Browser WebGL substrate lane and which seams should stay bounded.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","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."
|
|
|
|
|
"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Browser viewer and editor sidecar","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pissang/clay-viewer should remain active in the Browser viewer and editor sidecar lane and which seams should stay bounded.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","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."
|
|
|
|
|
"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","Browser asset renderer substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether KhronosGroup/glTF-Sample-Renderer should remain active in the Browser asset renderer substrate lane and which seams should stay bounded.","GltfView, GltfState, resource loader, user camera, renderer core","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0004","HT_browser_support","khronosgroup/gltf-sample-renderer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","Browser asset editor and inspection surface","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/space-opera should remain active in the Browser asset editor and inspection surface lane and which seams should stay bounded.","editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0005","HT_browser_support","google/model-viewer/packages/space-opera","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","Browser fidelity QA harness","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/render-fidelity-tools should remain active in the Browser fidelity QA harness lane and which seams should stay bounded.","golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0006","HT_browser_support","google/model-viewer/packages/render-fidelity-tools","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","Merge Bench","Browser emphasis and post-processing extension","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/model-viewer-effects should remain active in the Browser emphasis and post-processing extension lane and which seams should stay bounded.","effect composer integration, outline, SSAO, emphasis behavior, custom-element surface","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0007","HT_browser_support","google/model-viewer/packages/model-viewer-effects","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","Merge Bench","Browser docs and demo surface","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/modelviewer.dev should remain active in the Browser docs and demo surface lane and which seams should stay bounded.","live docs generation, snippet-to-demo coupling, sidebar and HTML generation","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0008","HT_browser_support","google/model-viewer/packages/modelviewer.dev","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner."
|
|
|
|
|
"google/model-viewer/packages/shared-assets","https://github.com/google/model-viewer/tree/main/packages/shared-assets","HyperTwist","Donor Bench","Boundary-sensitive sample-asset and test-fixture pack","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","repurpose","architecture only","Determine whether google/model-viewer/packages/shared-assets should remain active in the Browser sample-asset and fixture pack lane and which seams should stay bounded.","asset provenance, attribution terms, environment fixtures, sample models, fetch script behavior","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.","Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0009","HT_browser_support","google/model-viewer/packages/shared-assets","","","","","","","","Apache-2.0 container; mixed per-asset terms","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.","Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.","Preserve container notices and review each selected asset attribution or usage condition separately before shipping.","Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.","high","mixed-asset-whitelist-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use."
|
|
|
|
|
"pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","Merge Bench","Browser React effect-wrapper layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/react-postprocessing should remain active in the Browser React effect-wrapper layer lane and which seams should stay bounded.","React EffectComposer orchestration, selection model, wrapper ergonomics","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0010","HT_browser_support","pmndrs/react-postprocessing","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate React wrapper above pmndrs/postprocessing inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","Merge Bench","Browser 3D utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/three-stdlib should remain active in the Browser 3D utility substrate lane and which seams should stay bounded.","controls, loaders, WebXR helpers, post-processing helpers, utility exports","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0011","HT_browser_support","pmndrs/three-stdlib","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate shared utility shelf beneath the landed browser spatial owner trio; do not treat it as separately live."
|
|
|
|
|
"pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","Merge Bench","Browser math-helper substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/maath should remain active in the Browser math-helper substrate lane and which seams should stay bounded.","easing and damp functions, random helpers, geometry utilities","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0012","HT_browser_support","pmndrs/maath","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate math-helper layer inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","Donor Bench","Browser state-management substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether pmndrs/zustand should remain active in the Browser state-management substrate lane and which seams should stay bounded.","vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0013","HT_browser_support","pmndrs/zustand","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side state substrate inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","Merge Bench","Browser control-panel and parameter UI layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/leva should remain active in the Browser control-panel and parameter UI layer lane and which seams should stay bounded.","control store, schema parsing, useControls, plugin system, headless mode","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0014","HT_browser_support","pmndrs/leva","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate authoring and debug control sidecar inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","Donor Bench","Browser gesture and pointer-input substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether pmndrs/use-gesture should remain active in the Browser gesture and pointer-input substrate lane and which seams should stay bounded.","gesture controller, drag engine, pointer capture, scroll prevention, React and vanilla bindings","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0015","HT_browser_support","pmndrs/use-gesture","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser gesture and pointer-input substrate inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","Merge Bench","Browser layered-motion and explainer sidecar","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/parallax should remain active in the Browser layered-motion and explainer sidecar lane and which seams should stay bounded.","layered page-space runtime, sticky layers, scroll-driven spring behavior, scrollTo","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0016","HT_browser_support","@react-spring/parallax","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","Use directly as a bounded browser-side dependency for explainer and narrative surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate layered-motion sidecar beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","Merge Bench","Browser frame-loop and scheduling utility","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/rafz should remain active in the Browser frame-loop and scheduling utility lane and which seams should stay bounded.","phased queues, timeout scheduling, throttling, demand versus always loop control","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0017","HT_browser_support","@react-spring/rafz","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","Merge Bench","Browser animatable-component substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/animated should remain active in the Browser animatable-component substrate lane and which seams should stay bounded.","host creation, animated wrapper behavior, dependency observation, native-update fallback","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0018","HT_browser_support","@react-spring/animated","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate animatable-component package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","Donor Bench","Browser spring-runtime core","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether @react-spring/core should remain active in the Browser spring-runtime core lane and which seams should stay bounded.","controller orchestration, SpringValue runtime, useSprings lifecycle, frame advancement","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0019","HT_browser_support","@react-spring/core","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate spring-runtime core beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","Merge Bench","Browser motion utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/shared should remain active in the Browser motion utility substrate lane and which seams should stay bounded.","globals customization, frame loop, interpolation helpers, fluid observer substrate","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0020","HT_browser_support","@react-spring/shared","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
"@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","Merge Bench","Browser motion type-contract substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/types should remain active in the Browser motion type-contract substrate lane and which seams should stay bounded.","shared type contracts, animatable types, interpolation types, utility types","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0021","HT_browser_support","@react-spring/types","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","Use directly as a bounded browser-side dependency where those contracts are actually needed.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate type-contract package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live."
|
|
|
|
|
|
axiomlogicnexus