hypertwist/docs/repo_portfolio_unified_operational_v6_3.csv at e6039c53b1dd33f2d0777088511dd2d96c1fbfe4

axiomlogicnexus e6039c53b1 Close HyperTwist Phase 3R packet 3R-B

2026-05-13 05:10:16 +02:00

356 KiB

Raw Blame History

1	execution_queue_order	repo	primary_url	best_fit_project_v2	project_rank	portfolio_priority_score	execution_priority_score_v3	priority_band	taxonomy_hardened	archetype_primary	archetype_secondary	portfolio_role_v3	recommended_action_v2	repurposing_potential_v2	modification_scope_detail_v3	capability_extract	integration_realization_detail	consolidation_detail	repurpose_detail	realization_checklist	inspection_depth_recommendation	hidden_value_hypothesis	source_inspection_questions	source_code_audit_targets	coding_model_instruction_v3	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	exclusion_discipline	exclusion_reasoning_v3	confidence_v3	confidence_rationale_v3	confidence_reassessed	confidence_rationale	licensing_filter_status	bookmark_project_sections	bookmark_heading_paths_top	bookmark_description_sample	memo_signal_sample	expanded_reasoning	source_attachments	in_bookmarks	in_memo	bookmark_occurrences	memo_mentions	cluster_tag	source_audit_packet_id	category_guess_v2	reasoning	best_fit_project	category_guess	recommended_action	repurposing_potential	confidence	_repo_norm	v5_primary_eval_project	v5_runtime_project	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	project_rank_num	audit_rank_num	priority_num	phase_g_bucket	phase_g_project_stack_layer	phase_g_inclusion_status	phase_g_source_audit_priority	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_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
2	7701	HactarCE/Hyperspeedcube	https://github.com/HactarCE/Hyperspeedcube	HyperTwist	1.0	160.0	193.0	A	hypercubing / nD engine	foundation engine	simulation donor	locked core candidate	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.	HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). \| This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format	full subsystem extraction review	Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.	Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.	Audit 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.	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.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). \| This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs	HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). \| This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.	memo	False	True	0.0	6.0	HT_hyper_engine	HT_hyper_engine_0001	hypercubing / nD simulation	Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.	multi-project	hypercubing / nD simulation	integrate	direct	medium	hactarce/hyperspeedcube	HyperTwist			Original global operational v3 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.	Potentially relevant	yes	v6 unified all-project source-of-truth pack	v5_carry_forward	Existing v5 row reaffirmed or widened by v6 supplemental intake.	1.0	5	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.
3	7704	SYSTRAN/faster-whisper	https://github.com/SYSTRAN/faster-whisper	multi-project	1.0	71.0	80.0	C	voice / multimodal I/O	subsystem donor	multimodal donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.	huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services	deep source audit	Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.	Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.	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.	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.	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.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	memo mentions: 1	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.	SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.	memo	False	True	0.0	1.0	MU_misc	MU_misc_0001	voice / speech / audio	Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.	future/adjacent use	voice / speech / audio	repurpose	moderate modification	medium	systran/faster-whisper	multi-project			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		1.0	5	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.
4	7705	cubing/alg.js	https://github.com/cubing/alg.js	HyperTwist	2.0	95.0	95.0	P0	puzzle_simulation_training_donor	puzzle_simulation_training_donor	geometry_renderer_or_binding	donor bench	repurpose	architecture only	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.	HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.	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.	Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.	P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.	cubing/alg.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.	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 cubing/alg.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.	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	Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.	Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.	Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.	medium	Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.	medium	Will increase only after direct source inspection.	Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.	HyperTwist	HyperTwist		Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.	cubing/alg.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.	HyperTwist & ScriptoriumAI.txt	0	0	1.0	0.0	HT_cube_semantics	HT_cube_semantics_0002	puzzle_simulation_training_donor	Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.	HyperTwist	puzzle_simulation_training_donor	donor candidate	moderate modification	medium	cubing/alg.js	HyperTwist	supplemental_v6_not_runtime_anchored	no	v6_unified_source_of_truth	GPL-3.0-or-later	known_from_reference_material	uploaded_reference_docs	yes	hypertwist_and_scriptoriumai	HyperTwist	HyperTwist & ScriptoriumAI.txt	Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v6_supplemental_intake	New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).	2.0	1	95.0	Donor Bench	Focused restrictive clean-room donor target		P2	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.
5	7707	cubing/twisty.js	https://github.com/cubing/twisty.js	HyperTwist	2.0	95.0	95.0	P0	puzzle_simulation_training_donor	puzzle_simulation_training_donor	geometry_renderer_or_binding	donor bench	repurpose	architecture only	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.	HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.	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.	Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.	P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.	cubing/twisty.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.	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 cubing/twisty.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.	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	Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.	Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.	Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.	medium	Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.	medium	Will increase only after direct source inspection.	Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.	HyperTwist	HyperTwist		Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.	cubing/twisty.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.	HyperTwist & ScriptoriumAI.txt	0	0	1.0	0.0	HT_cube_semantics	HT_cube_semantics_0003	puzzle_simulation_training_donor	Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.	HyperTwist	puzzle_simulation_training_donor	donor candidate	moderate modification	medium	cubing/twisty.js	HyperTwist	supplemental_v6_not_runtime_anchored	no	v6_unified_source_of_truth	GPL-3.0-or-later	known_from_reference_material	uploaded_reference_docs	yes	hypertwist_and_scriptoriumai	HyperTwist	HyperTwist & ScriptoriumAI.txt	Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v6_supplemental_intake	New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).	2.0	1	95.0	Donor Bench	Focused restrictive clean-room donor target		P2	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.
6	7709	HactarCE/2x2x2x2-Scrambler	https://github.com/HactarCE/2x2x2x2-Scrambler	HyperTwist	2.0	63.0	63.0	P2	puzzle_simulation_training_donor	puzzle_simulation_training_donor	geometry_renderer_or_binding	donor bench	repurpose	architecture only	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.	HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.	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.	Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.	P2 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.	HactarCE/2x2x2x2-Scrambler may hide higher-value reusable components in its HactarCE family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.	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 HactarCE/2x2x2x2-Scrambler at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.	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	Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.	Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.	Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.	low-to-medium	Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.	low-to-medium	Will increase only after direct source inspection.	Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.	HyperTwist	HyperTwist		Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.	HactarCE/2x2x2x2-Scrambler enters the corpus through the v6 supplemental intake. It is treated as reserve bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.	HyperTwist & ScriptoriumAI.txt	0	0	1.0	0.0	HT_cube_semantics	HT_cube_semantics_0004	puzzle_simulation_training_donor	Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.	HyperTwist	puzzle_simulation_training_donor	future candidate	architecture only	low-to-medium	hactarce/2x2x2x2-scrambler	HyperTwist	supplemental_v6_not_runtime_anchored	no	v6_unified_source_of_truth	GPL-3.0	known_from_reference_material	uploaded_reference_docs	yes	hypertwist_and_scriptoriumai	HyperTwist	HyperTwist & ScriptoriumAI.txt	Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v6_supplemental_intake	New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).	2.0	3	63.0	Donor Bench	Focused restrictive clean-room donor target		P2	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.
7	7814	kkoomen/qbr	https://github.com/kkoomen/qbr	HyperTwist	2.0	158.0	191.0	A	vision / perception / AR	foundation engine	vision donor	locked core candidate	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.	kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). \| kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). \| kkoomen/qbr — MIT — Webcam CV color detection. \| poliva/cubedex, ta...	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	full subsystem extraction review	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.	Audit 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.	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.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). \| kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). \| kkoomen/qbr — MIT — Webcam CV color detection. \| poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.	kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). \| kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). \| kkoomen/qbr — MIT — Webcam CV color detection. \| poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.	memo	False	True	0.0	5.0	HT_cube_vision	HT_cube_vision_0001	computer vision / AR	Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.	multi-project	computer vision / AR	integrate	heavy modification	medium	kkoomen/qbr	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Potentially relevant	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		2.0	5	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.
8	7818	coqui-ai/TTS	https://github.com/coqui-ai/TTS	multi-project	2.0	71.0	80.0	C	voice / multimodal I/O	subsystem donor	multimodal donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.	https://github.com/coqui-ai/TTS – Coqui XTTS v2.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer	deep source audit	Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.	Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.	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.	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.	project-local anchor	base + donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	shared portfolio utility	augmenter	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	VectorShell \| HyperTwist \| ScriptoriumAI	This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	memo mentions: 1	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				https://github.com/coqui-ai/TTS – Coqui XTTS v2.	coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.	memo	False	True	0.0	1.0	MU_misc	MU_misc_0002	voice / speech / audio	Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.	future/adjacent use	voice / speech / audio	repurpose	moderate modification	medium	coqui-ai/tts	multi-project			Original global operational v3 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.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		2.0	5	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.
9	8543	vivaansinghvi07/rubix-cube-solver	https://github.com/vivaansinghvi07/rubix-cube-solver	HyperTwist	3.0	158.0	191.0	A	vision / perception / AR	foundation engine	vision donor	locked core candidate	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.	Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	full subsystem extraction review	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.	Audit 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.	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.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb	vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.	memo	False	True	0.0	10.0	HT_cube_vision	HT_cube_vision_0002	computer vision / AR	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.	HyperTwist	computer vision / AR	integrate	heavy modification	medium	vivaansinghvi07/rubix-cube-solver	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		3.0	5	158.0	Locked Parallel Foundation	Parallel foundation and reconstruction companion donor			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Normalized legacy 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.
10	8547	ggml-org/whisper.cpp	https://github.com/ggml-org/whisper.cpp	multi-project	3.0	71.0	80.0	C	voice / multimodal I/O	subsystem donor	multimodal donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.	7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer	deep source audit	Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.	Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.	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.	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.	project-local anchor	base + donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	shared portfolio utility	augmenter	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	VectorShell \| HyperTwist \| ScriptoriumAI	This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	memo mentions: 1	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.	ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.	memo	False	True	0.0	1.0	MU_misc	MU_misc_0003	voice / speech / audio	Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.	future/adjacent use	voice / speech / audio	repurpose	moderate modification	medium	ggml-org/whisper.cpp	multi-project			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		3.0	5	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.
11	11766	tao-yu/Alg-Trainer	https://github.com/tao-yu/Alg-Trainer	HyperTwist	4.0	156.0	189.0	A	cubing trainer / solver / timing	foundation engine	training donor	locked core candidate	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.	Alg-Trainer (tao-yu/Alg-Trainer) \| tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. \| tao-yu/Alg-Trainer — MIT — Multi-set alg t...	Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.	Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	full subsystem extraction review	Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.	Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	poliva/cubedex	specialized training UX donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	Lykos/cube_trainer	sampling/analytics donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	project-local first	Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				Alg-Trainer (tao-yu/Alg-Trainer) \| tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. \| tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). \| tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.	tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) \| tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. \| tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.	memo	False	True	0.0	5.0	HT_training_stack	HT_training_stack_0001	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	tao-yu/alg-trainer	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		4.0	5	156.0					permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.	implemented_live_permissive	landed_permissive_preserve	Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work.
12	11769	rhasspy/piper	https://github.com/rhasspy/piper	multi-project	4.0	71.0	80.0	C	voice / multimodal I/O	subsystem donor	multimodal donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.	rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).	Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.	Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.	Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer	deep source audit	Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.	Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.	Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.	Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.	project-local anchor	base + donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	shared portfolio utility	augmenter	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	VectorShell \| HyperTwist \| ScriptoriumAI	This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	memo mentions: 1	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).	rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.	memo	False	True	0.0	1.0	MU_misc	MU_misc_0004	voice / speech / audio	Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.	future/adjacent use	voice / speech / audio	repurpose	moderate modification	medium	rhasspy/piper	multi-project			Original global operational v3 retained	MIT code; voice artifacts reviewed separately	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		4.0	5	71.0					permissive_or_noncopyleft_known	direct_incorporation_ok	The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.	Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.	Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.	Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.	high	voice-artifact-review-required	yes	v6.3_final_source_of_truth	Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.
13	11771	cubing/cubing.js	https://github.com/cubing/cubing.js	HyperTwist	5.0	152.0	185.0	A	interface / visualization / shell surface	foundation engine	visualization donor	locked strategic donor	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.	Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.	Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.	Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions	full subsystem extraction review	Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.	Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.	Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	project-local anchor	base + donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	shared portfolio utility	augmenter	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	VectorShell \| HyperTwist \| ScriptoriumAI	This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	medium-high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.	cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.	memo	False	True	0.0	1.0	HT_cube_semantics	HT_cube_semantics_0001	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	cubing/cubing.js	HyperTwist			Original global operational v3 retained	MPL-2.0 OR GPL-3.0-or-later	known_from_reference_material	uploaded_reference_docs	yes	hypertwist_and_scriptoriumai	HyperTwist	HyperTwist & ScriptoriumAI.txt	Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward	Existing v5 row reaffirmed or widened by v6 supplemental intake.	5.0	5	152.0	Locked Strategic Donor	Boundary-sensitive classic-cubing semantics and rendering donor		P1	mixed_or_boundary_sensitive_known	bounded_sidecar_or_selective_reimplementation	The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.	Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.	Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.	Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.	high	dual-license-boundary-review	yes	v6.3_final_source_of_truth	Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.	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.
14	11848	cahidenes/rubiks-cube-solver	https://github.com/cahidenes/rubiks-cube-solver	HyperTwist	6.0	148.0	174.0	A	vision / perception / AR	foundation engine	vision donor	locked strategic donor	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.	cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. \| cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. \| Yes — we already have several strong open-source visual models for cube recognition from earlier in o...	Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.	Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	full subsystem extraction review	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.	Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	kkoomen/qbr	foundation + perception donor	Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.	vivaansinghvi07/rubix-cube-solver	perception + replay donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cubing/cubing.js	state/render backend	Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.	VectorShell \| ScriptoriumAI	VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	memo mentions: 5	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. \| cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. \| Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high	cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.	memo	False	True	0.0	5.0	HT_cube_vision	HT_cube_vision_0003	computer vision / AR	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.	HyperTwist	computer vision / AR	integrate	heavy modification	medium	cahidenes/rubiks-cube-solver	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		6.0	5	148.0	Locked Strategic Donor	Active recognition-heuristics and validation donor			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.	selected_not_live_permissive_candidate	phase0r_permissive_eval_then_implement	Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R.
15	11852	tentone/rubix-solver	https://github.com/tentone/rubix-solver	HyperTwist	7.0	148.0	174.0	A	vision / perception / AR	foundation engine	vision donor	locked strategic donor	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.	tentone/rubix-solver — MIT — OpenCV cube detection. \| Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...	Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.	Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	full subsystem extraction review	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.	Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	kkoomen/qbr	foundation + perception donor	Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.	vivaansinghvi07/rubix-cube-solver	perception + replay donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cubing/cubing.js	state/render backend	Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.	VectorShell \| ScriptoriumAI	VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	memo mentions: 7	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				tentone/rubix-solver — MIT — OpenCV cube detection. \| Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio	tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.	memo	False	True	0.0	7.0	HT_cube_vision	HT_cube_vision_0004	computer vision / AR	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.	HyperTwist	computer vision / AR	integrate	heavy modification	medium	tentone/rubix-solver	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		7.0	5	148.0	Locked Strategic Donor	Active native-CV donor and comparison bench			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.	selected_not_live_permissive_candidate	phase0r_permissive_eval_then_implement	Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R.
16	11857	Lykos/cube_trainer	https://github.com/Lykos/cube_trainer	HyperTwist	8.0	145.0	171.0	A	cubing trainer / solver / timing	foundation engine	training donor	locked strategic donor	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.	Lykos/cube_trainer — MIT — Smart-sampled training. \| CubeTrainer (Lykos/cube_trainer) \| Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.	Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.	Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	full subsystem extraction review	Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.	Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	tao-yu/Alg-Trainer	base + donor swarm	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	poliva/cubedex	specialized training UX donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	project-local first	Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	strong adjacency to identified core stack; memo mentions: 4	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				Lykos/cube_trainer — MIT — Smart-sampled training. \| CubeTrainer (Lykos/cube_trainer) \| Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.	Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.	memo	False	True	0.0	4.0	HT_training_stack	HT_training_stack_0002	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	lykos/cube_trainer	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		8.0	5	145.0	Locked Strategic Donor	Top-tier persistent training-domain donor			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.	implemented_live_permissive	landed_permissive_preserve	Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work.
17	11861	poliva/cubedex	https://github.com/poliva/cubedex	HyperTwist	9.0	145.0	171.0	A	interface / visualization / shell surface	foundation engine	visualization donor	locked strategic donor	integrate	direct	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.	poliva/cubedex — MIT — Smartcube alg trainer. \| Open source repositories and software specifically designed to drill ("hammer") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...	Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.	Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions	full subsystem extraction review	Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.	Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	project-local anchor	base + donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	shared portfolio utility	augmenter	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	cross-project transfer candidate	future merger	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	VectorShell \| HyperTwist \| ScriptoriumAI	This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	strong adjacency to identified core stack; memo mentions: 4	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				poliva/cubedex — MIT — Smartcube alg trainer. \| Open source repositories and software specifically designed to drill ("hammer") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) \| poliva/cubedex, tao-yu/A	poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.	memo	False	True	0.0	4.0	HT_training_stack	HT_training_stack_0016	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	poliva/cubedex	HyperTwist			Original global operational v3 retained	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		9.0	5	145.0	Locked Strategic Donor	Top-tier training UX and smartcube donor			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	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.
18	11865	kash/cubedesk	https://github.com/kash/cubedesk	HyperTwist	10.0	145.0	171.0	A	hypercubing / nD engine	foundation engine	simulation donor	locked strategic donor	repurpose	architecture only	Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.	AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...	Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.	Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format	full subsystem extraction review	Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.	Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.	Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.	HactarCE/Hyperspeedcube	foundation + donor	Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.	cubing/cubing.js	3D engine + notation/state donor	Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.	tao-yu/Alg-Trainer	training UX donor	Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.	VectorShell \| ScriptoriumAI	VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.	do not exclude	Keep in active merge-set and force full source audit before any demotion.	high	single-source signal; clear taxonomy; active integration value; foundation-level fit	high	memo mentions: 4	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. \| cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source	kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.	memo	False	True	0.0	4.0	HT_hyper_engine	HT_hyper_engine_0002	cubing / algorithm training	Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.	HyperTwist	hypercubing / nD simulation	integrate	direct	medium	kash/cubedesk	HyperTwist			Original global operational v3 retained	GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		10.0	5	145.0	Locked Strategic Donor	Restrictive clean-room donor target		P1	mixed_or_boundary_sensitive_known	reverse_engineer_preferred	The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.	Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.	Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.	Yes â€” this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.	high	license-contradiction-clean-room-donor	no	v6.3_final_source_of_truth	Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.	selected_not_live_clean_room_candidate	phase0r_clean_room_eval_then_model_a_model_b	Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier.
19	11869	cutelyaware/magiccube4d	https://github.com/cutelyaware/magiccube4d/tree/master	HyperTwist	11.0	122.0	137.0	A	hypercubing / nD engine	subsystem donor	simulation donor	locked strategic donor	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.	Automatically exported from code.google.com/p/magiccube4d	Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.	Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format	deep source audit	Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.	Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.	Audit 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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	explicit bookmark description available	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.	HyperTwist(1)	HyperTwist Consider	Automatically exported from code.google.com/p/magiccube4d		cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.	bookmarks	True	False	1.0	0.0	HT_hyper_engine	HT_hyper_engine_0003	hypercubing / nD simulation	Integrate primarily for HyperTwist. Its description and bookmark placement under "HyperTwist Consider" place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	cutelyaware/magiccube4d	HyperTwist			Original global operational v3 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		11.0	5	122.0	Locked Strategic Donor	Top-tier 4D interaction, history, and macro donor with attribution obligations		P1	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.
20	11873	roice3/Magic120Cell	https://github.com/roice3/Magic120Cell	HyperTwist	12.0	122.0	137.0	A	hypercubing / nD engine	subsystem donor	simulation donor	locked strategic donor	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.	4D Megaminx Analogue	Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.	Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format	deep source audit	Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.	Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.	Audit 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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	explicit bookmark description available	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.	HyperTwist(1)	HyperTwist Consider	4D Megaminx Analogue		roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.	bookmarks	True	False	1.0	0.0	HT_hyper_engine	HT_hyper_engine_0004	hypercubing / nD simulation	Integrate primarily for HyperTwist. Its description and bookmark placement under "HyperTwist Consider" place it in the hypercubing / nD simulation layer.	HyperTwist	hypercubing / nD simulation	integrate	heavy modification	medium	roice3/magic120cell	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		12.0	5	122.0	Locked Strategic Donor	Specialized 4D interaction and puzzle-UX donor		P1	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.
21	11877	roice3/MagicCube5D	https://github.com/roice3/MagicCube5D	HyperTwist	13.0	122.0	137.0	A	hypercubing / nD engine	subsystem donor	simulation donor	locked strategic donor	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.	5D Rubik's Cube Analogue	Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.	Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.	Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format	deep source audit	Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.	Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.	Audit 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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	explicit bookmark description available	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.	HyperTwist(1)	HyperTwist Consider	5D Rubik's Cube Analogue		roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.	bookmarks	True	False	1.0	0.0	HT_hyper_engine	HT_hyper_engine_0005	hypercubing / nD simulation	Integrate primarily for HyperTwist. Its description and bookmark placement under "HyperTwist Consider" place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	roice3/magiccube5d	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		13.0	5	122.0	Locked Strategic Donor	Specialized 5D cube interaction, progress, and macro donor		P1	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.
22	11881	cs0x7f/cstimer	https://github.com/cs0x7f/cstimer	HyperTwist	14.0	121.0	147.0	A	gold-standard timer benchmark	benchmark	Gold-standard timer benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	behavior and acceptance-test benchmark review	Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.	Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?	Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.	Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.	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.	exclude from donor lane	The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.	high	Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.	high	Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				cs0x7f/cstimer â€” GPL timer/training platform; keep only as the gold-standard timer benchmark.	cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.	memo	False	True	0.0	5.0	HT_timer_training	HT_timer_training_0001	Gold-standard timer benchmark	Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.	HyperTwist	Gold-standard timer benchmark	future candidate	architecture only	medium	cs0x7f/cstimer	HyperTwist			Original global operational v3 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		14.0	5	121.0	Reserve Bench	Gold-standard timer benchmark	Included	P2	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.
23	11889	aMonteSl/CodeXR	https://github.com/aMonteSl/CodeXR	HyperTwist	16.0	119.0	134.0	B	reference-only XR benchmark	benchmark	Reference-only XR benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	behavior-level benchmark review	Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.	Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?	Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.	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.	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.	exclude from donor lane	The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.	high	Source-backed dossier and license verification collapse the old donor thesis.	high	Source-backed dossier and license verification collapse the old donor thesis.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				aMonteSl/CodeXR â€” GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.	aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.	memo	False	True	0.0	3.0	HT_cube_vision	HT_cube_vision_0005	Reference-only XR benchmark	Reference-only XR benchmark for HyperTwist; not a donor lane.	HyperTwist	Reference-only XR benchmark	future candidate	architecture only	medium	amontesl/codexr	HyperTwist			Original global operational v3 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.	Potentially relevant	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		16.0	5	119.0	Reserve Bench	Reference-only XR benchmark	Included	P3	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.
24	11893	brianpeiris/RiftSketch	https://github.com/brianpeiris/RiftSketch	HyperTwist	17.0	119.0	134.0	B	vision / perception / AR	subsystem donor	vision donor	Reserve Bench	future candidate	architecture only	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.	brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch \| brianpeiris/RiftSketch — MIT — WebVR live coding. \| poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	deep source audit	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	memo mentions: 3	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch \| brianpeiris/RiftSketch — MIT — WebVR live coding. \| poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.	brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.	memo	False	True	0.0	3.0	HT_cube_vision	HT_cube_vision_0006	cubing / algorithm training	Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.	multi-project	computer vision / AR	integrate	heavy modification	medium	brianpeiris/riftsketch	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Potentially relevant	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		17.0	5	119.0	Reserve Bench	XR interaction and spatial-UI bench			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.
25	11897	abunickabhi/5style-Trainer	https://github.com/abunickabhi/5style-Trainer	HyperTwist	18.0	118.0	133.0	B	cubing trainer / solver / timing	subsystem donor	training donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.	abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). \| abunickabhi/5style-Trainer — MIT (BLD extension).	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	deep source audit	Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.	Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit 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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	strong adjacency to identified core stack; memo mentions: 2	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). \| abunickabhi/5style-Trainer — MIT (BLD extension).	abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.	memo	False	True	0.0	2.0	HT_training_stack	HT_training_stack_0006	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	direct	medium	abunickabhi/5style-trainer	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		18.0	5	118.0	Donor Bench	Focused advanced-training donor			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Normalized legacy 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.
26	11900	MathewKJ2048/Rubiks-cube-simulator	https://github.com/MathewKJ2048/Rubiks-cube-simulator	HyperTwist	19.0	118.0	133.0	B	clean-room simulator benchmark	benchmark	Clean-room simulator benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	clean-room benchmark review	Hidden value sits in text-command grammar, move-history logging, and timed step playback.	Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?	Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.	Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.	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.	exclude from donor lane	The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.	high	The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.	high	The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				MathewKJ2048/Rubiks-cube-simulator â€” GPL-3.0 simulator; keep only as a clean-room simulator benchmark.	MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.	memo	False	True	0.0	2.0	HT_training_clean_room	HT_training_clean_room_0004	Clean-room simulator benchmark	Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.	HyperTwist	Clean-room simulator benchmark	future candidate	architecture only	medium	mathewkj2048/rubiks-cube-simulator	HyperTwist			Original global operational v3 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		19.0	5	118.0	Reserve Bench	Clean-room simulator benchmark	Included	P3	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.
27	11903	NuiLab/code-vr	https://github.com/NuiLab/code-vr	HyperTwist	20.0	118.0	133.0	B	vision / perception / AR	subsystem donor	vision donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.	NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. \| poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	deep source audit	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	memo mentions: 2	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. \| poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.	NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.	memo	False	True	0.0	2.0	HT_cube_vision	HT_cube_vision_0007	cubing / algorithm training	Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.	multi-project	computer vision / AR	integrate	heavy modification	medium	nuilab/code-vr	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Potentially relevant	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		20.0	5	118.0	Donor Bench	XR pedagogy and code-to-scene representation donor		P2	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.
28	11906	ShellPuppy/RCube	https://github.com/ShellPuppy/RCube	HyperTwist	21.0	118.0	133.0	B	large-N solver benchmark	benchmark	Large-N solver benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	algorithm benchmark review	Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.	Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?	Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.	Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.	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.	exclude from donor lane	The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.	high	Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.	high	Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				ShellPuppy/RCube â€” GPL large-N cube solver; keep only as a large-N solver benchmark.	ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.	memo	False	True	0.0	2.0	HT_solver_oracles	HT_solver_oracles_0001	Large-N solver benchmark	Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.	HyperTwist	Large-N solver benchmark	future candidate	architecture only	medium	shellpuppy/rcube	HyperTwist			Original global operational v3 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		21.0	5	118.0	Reserve Bench	Large-N solver benchmark	Included	P3	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.
29	11909	brownan/Rubiks-Cube-Solver	https://github.com/brownan/Rubiks-Cube-Solver	HyperTwist	22.0	118.0	133.0	B	cubing trainer / solver / timing	subsystem donor	training donor	Reserve Bench	future candidate	architecture only	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.	brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. \| brownan/Rubiks-Cube-Solver — GPL-3.0.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	deep source audit	Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.	Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit 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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	memo mentions: 2	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. \| brownan/Rubiks-Cube-Solver — GPL-3.0.	brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.	memo	False	True	0.0	2.0	HT_training_stack	HT_training_stack_0007	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	brownan/rubiks-cube-solver	HyperTwist			Original global operational v3 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		22.0	5	118.0	Reserve Bench	Benchmark oracle and clean-room optimal-solver candidate		P2	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.
30	11915	newyork-anthonyng/rubiks-cross-trainer	https://github.com/newyork-anthonyng/rubiks-cross-trainer	HyperTwist	24.0	118.0	133.0	B	cubing trainer / solver / timing	subsystem donor	training donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.	newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). \| newyork-anthonyng/rubiks-cross-trainer — MIT.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	deep source audit	Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.	Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit 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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	memo mentions: 2	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). \| newyork-anthonyng/rubiks-cross-trainer — MIT.	newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.	memo	False	True	0.0	2.0	HT_training_stack	HT_training_stack_0008	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	newyork-anthonyng/rubiks-cross-trainer	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		24.0	5	118.0	Donor Bench	Focused donor			permissive_or_noncopyleft_known	direct_incorporation_ok	This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.	Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.	Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.	Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.	high	strategic-or-implemented-component	yes	v6.3_final_source_of_truth	Normalized legacy 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.
31	11918	vwcwong/CubeSim	https://github.com/vwcwong/CubeSim	HyperTwist	25.0	118.0	133.0	B	clean-room state/history benchmark	benchmark	Clean-room state/history benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: cleaner domain architecture for simulator state/history separation, parser/scramble modules, and replay/history behavior suitable for clean-room reimplementation.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	clean-room benchmark review	Hidden value sits in state/history separation, parser/scramble modularity, and replay-oriented architecture.	Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?	Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.	Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.	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.	exclude from donor lane	The repo is GPL simulator code and should remain only as a clean-room state/history benchmark.	high	The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.	high	The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				vwcwong/CubeSim â€” GPL simulator; keep only as a clean-room state/history benchmark.	vwcwong/CubeSim is retained only as a clean-room state/history benchmark. Its value is architectural and behavioral, not donor code.	memo	False	True	0.0	2.0	HT_training_clean_room	HT_training_clean_room_0005	Clean-room state/history benchmark	Clean-room state/history benchmark for HyperTwist; retained for behavior extraction only.	HyperTwist	Clean-room state/history benchmark	future candidate	architecture only	medium	vwcwong/cubesim	HyperTwist			Original global operational v3 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		25.0	5	118.0	Reserve Bench	Clean-room state/history benchmark	Included	P3	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.
32	11921	AviKaufman/Rubix-cube-trainer	https://github.com/AviKaufman/Rubix-cube-trainer	HyperTwist	26.0	117.0	132.0	B	clean-room pedagogy benchmark	benchmark	Clean-room pedagogy benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: beginner-method teaching flow, step guidance, and tutorial-state behavior worth preserving through a clean-room spec.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	clean-room benchmark review	Hidden value sits in beginner-method pedagogy flow, guidance cadence, and tutorial-state transitions.	Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?	Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.	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.	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.	exclude from donor lane	The repo is explicitly all-rights-reserved and should remain only as a clean-room pedagogy benchmark.	high	The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.	high	The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				AviKaufman/Rubix-cube-trainer â€” all rights reserved; keep only as a clean-room pedagogy benchmark.	AviKaufman/Rubix-cube-trainer is retained only as a clean-room pedagogy benchmark. Its value is in teaching flow and tutorial behavior, not donor code.	memo	False	True	0.0	1.0	HT_training_clean_room	HT_training_clean_room_0003	Clean-room pedagogy benchmark	Clean-room pedagogy benchmark for HyperTwist; retained for behavior extraction only.	HyperTwist	Clean-room pedagogy benchmark	future candidate	architecture only	medium	avikaufman/rubix-cube-trainer	HyperTwist			Original global operational v3 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		26.0	5	117.0	Reserve Bench	Clean-room pedagogy benchmark	Included	P3	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.
33	11924	alinen/cube	https://github.com/alinen/cube	HyperTwist	27.0	117.0	132.0	B	clean-room planner benchmark	benchmark	Clean-room planner benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: guided lesson flow, cube-state handling, and bounded planner/search behavior suitable for first-party clean-room reimplementation.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	clean-room benchmark review	Hidden value sits in bounded planner/search flow and guided lesson state transitions.	Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?	Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.	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.	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.	exclude from donor lane	The repo has no explicit license visible and should remain only as a clean-room planner benchmark.	medium	The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.	medium	The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				alinen/cube â€” no explicit license visible; keep only as a clean-room planner benchmark.	alinen/cube is retained only as a clean-room planner benchmark. Its useful value is behavioral and architectural, not donor-grade.	memo	False	True	0.0	1.0	HT_training_clean_room	HT_training_clean_room_0001	Clean-room planner benchmark	Clean-room planner benchmark for HyperTwist; retained for behavior extraction only.	HyperTwist	Clean-room planner benchmark	future candidate	architecture only	medium	alinen/cube	HyperTwist			Original global operational v3 retained	no explicit license visible	pending_repo_license_audit	not_resolved_from_uploaded_materials	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		27.0	5	117.0	Reserve Bench	Clean-room planner benchmark	Included	P3	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.
34	11927	ambisinister/blindsolve	https://github.com/ambisinister/blindsolve	HyperTwist	28.0	117.0	132.0	B	clean-room BLD memo benchmark	benchmark	Clean-room BLD memo benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: narrow memo-practice behavior and BLD training flow worth preserving through a clean-room spec.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	clean-room benchmark review	Hidden value sits in narrow memo-practice flow and user-feedback behavior.	Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?	Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.	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.	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.	exclude from donor lane	The repo has no explicit license visible and does not justify donor treatment; retain only as a clean-room memo benchmark.	medium	The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.	medium	The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				ambisinister/blindsolve â€” no explicit license visible; keep only as a clean-room BLD memo benchmark.	ambisinister/blindsolve is retained only as a clean-room BLD memo benchmark. Its value is in a narrow behavior slice, not in donor code.	memo	False	True	0.0	1.0	HT_training_clean_room	HT_training_clean_room_0002	Clean-room BLD memo benchmark	Clean-room BLD memo benchmark for HyperTwist; retained for behavior extraction only.	HyperTwist	Clean-room BLD memo benchmark	future candidate	architecture only	medium	ambisinister/blindsolve	HyperTwist			Original global operational v3 retained	no explicit license visible	pending_repo_license_audit	not_resolved_from_uploaded_materials	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		28.0	5	117.0	Reserve Bench	Clean-room BLD memo benchmark	Included	P3	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.
35	11930	efrantar/rob-twophase	https://github.com/efrantar/rob-twophase	HyperTwist	29.0	117.0	132.0	B	solver oracle / robot-metric benchmark	benchmark	Solver oracle and robot-metric benchmark	Reserve Bench	future candidate	architecture only	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.	Benchmark-only retained value: correctness oracle, robot/axial-metric comparisons, multiple-solution search expectations, and pruning-table performance baselines.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	oracle benchmark review	Hidden value sits in metric handling, pruning-table organization, CLI oracle behavior, and multi-solution search expectations.	Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?	Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.	Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.	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.	exclude from donor lane	The repo is GPL solver code and should remain only as a correctness/performance oracle and robot-metric benchmark.	high	Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.	high	Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				efrantar/rob-twophase â€” GPL two-phase solver; keep only as solver oracle and robot-metric benchmark.	efrantar/rob-twophase remains valuable because it is a strong correctness/performance oracle with robot-metric coverage. That value is benchmark authority, not donor code.	memo	False	True	0.0	1.0	HT_solver_oracles	HT_solver_oracles_0002	Solver oracle and robot-metric benchmark	Solver oracle and robot-metric benchmark for HyperTwist; retained for acceptance testing, not donor use.	HyperTwist	Solver oracle and robot-metric benchmark	future candidate	architecture only	medium	efrantar/rob-twophase	HyperTwist			Original global operational v3 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		29.0	5	117.0	Reserve Bench	Solver oracle and robot-metric benchmark	Included	P2	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.
36	11933	onionhoney/roux-trainers	https://github.com/onionhoney/roux-trainers	HyperTwist	30.0	117.0	132.0	B	method-specific training donor	restrictive donor	clean-room donor	donor bench	repurpose	architecture only	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.	Focused restrictive clean-room donor target. Retain the stage-specific training modes, solver-backed analyzer behavior, recognition masking, favorites/batch-drill flow, and 2D/3D training visualization ideas through Model A / Model B separation.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	deep source audit	Hidden value sits in state-machine-driven training flows, solver-backed analyzer behavior, recognition masking, favorites persistence, and batch-drill mechanics.	Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?	Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.	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.	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.	exclude from direct code use, keep as clean-room donor	The repo is GPLv3 and too method-specific for direct incorporation, but it still contains real training/analyzer subsystem value worth preserving through a clean-room donor path.	high	The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.	high	The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				onionhoney/roux-trainers â€” GPLv3 Roux trainer; keep as a focused restrictive clean-room donor, not direct donor code.	onionhoney/roux-trainers remains valuable because it contains stage-specific training-state machines, solver-backed analyzer modes, recognition masking, and batch-drill patterns. That value should flow through a clean-room donor path, not direct incorporation.	memo	False	True	0.0	1.0	HT_training_clean_room	HT_training_clean_room_0006	Focused restrictive clean-room donor target	Focused restrictive clean-room donor target for HyperTwist; stronger than a passive benchmark, but still not direct donor code.	HyperTwist	Focused restrictive clean-room donor target	repurpose	architecture only	medium	onionhoney/roux-trainers	HyperTwist			Original global operational v3 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		30.0	5	117.0	Donor Bench	Focused restrictive clean-room donor target	Included	P2	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.
37	11936	yakupbilen/drl-rubiks-cube	https://github.com/yakupbilen/drl-rubiks-cube	HyperTwist	31.0	117.0	132.0	B	vision / perception / AR	subsystem donor	vision donor	Reserve Bench	future candidate	architecture only	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.	yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	deep source audit	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	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.	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.	exclude from standalone? no	Not necessarily the final base, but keep as an active subsystem candidate or major donor.	medium	single-source signal; clear taxonomy; active integration value	medium	memo mentions: 1	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.	yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.	memo	False	True	0.0	1.0	HT_cube_vision	HT_cube_vision_0008	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	yakupbilen/drl-rubiks-cube	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		31.0	5	117.0	Reserve Bench	Search/training systems bench			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.
38	11939	Hypercubers/hypercubing.xyz	https://github.com/Hypercubers/hypercubing.xyz	HyperTwist	32.0	92.0	101.0	C	hypercubing / nD engine	subsystem donor	simulation donor	locked strategic donor	repurpose	moderate modification	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.	Website for the Hypercubing community	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format	deep source audit	Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.	Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.	Audit 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.	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.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	explicit bookmark description available	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.	HyperTwist(1)	HyperTwist Consider	Website for the Hypercubing community		Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.	bookmarks	True	False	1.0	0.0	HT_hyper_engine	HT_hyper_engine_0006	hypercubing / nD simulation	Integrate primarily for HyperTwist. Its description and bookmark placement under "HyperTwist Consider" place it in the hypercubing / nD simulation layer.	HyperTwist	hypercubing / nD simulation	integrate	heavy modification	medium	hypercubers/hypercubing.xyz	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		32.0	5	92.0	Locked Strategic Donor	Knowledge and curriculum donor		P1	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.
39	11945	Aarav2709/KubeTimr	https://github.com/Aarav2709/KubeTimr	HyperTwist	34.0	88.0	97.0	C	cubing trainer / solver / timing	subsystem donor	training donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.	Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. \| Aarav2709/KubeTimr — MIT — Offline timer.	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks	deep source audit	Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.	Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit 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.	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.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium	single-source signal; clear taxonomy; mostly donor/reference role	medium	strong adjacency to identified core stack; memo mentions: 2	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.				Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. \| Aarav2709/KubeTimr — MIT — Offline timer.	Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.	memo	False	True	0.0	2.0	HT_training_stack	HT_training_stack_0015	cubing / algorithm training	Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	aarav2709/kubetimr	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		34.0	5	88.0	Donor Bench	Focused subsystem donor			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.
40	11951	roice3/MagicTile	https://github.com/roice3/MagicTile	HyperTwist	36.0	88.0	97.0	C	infra / runtime / observability / integration	subsystem donor	integration utility	locked strategic donor	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.	Non-euclidean Rubik's Cube Analogues	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API	deep source audit	Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.	Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.	Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.	Audit 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.	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.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	explicit bookmark description available	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.	HyperTwist(1)	HyperTwist Consider	Non-euclidean Rubik's Cube Analogues		roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.	bookmarks	True	False	1.0	0.0	HT_hyper_engine	HT_hyper_engine_0007	cubing / algorithm training	Integrate primarily for HyperTwist. Its description and bookmark placement under "HyperTwist Consider" place it in the cubing / algorithm training layer.	HyperTwist	cubing / algorithm training	integrate	moderate modification	medium	roice3/magictile	HyperTwist			Original global operational v3 retained	MIT	known_from_reference_material	uploaded_reference_docs	no				Supplemental intake references are advisory only; v6 adjudication remains the source of truth.	Usually indirect	yes	v6 unified all-project source-of-truth pack	v5_carry_forward		36.0	5	88.0	Locked Strategic Donor	Top-tier non-Euclidean geometry and topology donor		P1	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.
41	11967	PostHog/posthog	https://github.com/PostHog/posthog	HyperTwist	41.0	72.0	81.0	C	telemetry / replay / feature governance	subsystem donor	telemetry donor	donor bench	repurpose	moderate modification	Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.	🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...	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.	Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter	deep source audit	Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.	Inspect 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.	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.	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.	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.	exclude from core, keep as donor	Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.	medium-low	single-source signal; clear taxonomy; mostly donor/reference role	medium	explicit bookmark description available	Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.	HyperTwist(1)	HyperTwist Consider	🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.		PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.	bookmarks	True	False	1.0	0.0	HT_control_plane	HT_control_plane_0001	cloud / infra / observability / api	Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.	HyperTwist	telemetry / replay / feature governance	repurpose	moderate modification	medium	posthog/posthog	HyperTwist			Original global operational v3 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		41.0	5	72.0		Telemetry / replay / feature-governance donor			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.
42		met4citizen/TalkingHead	https://github.com/met4citizen/TalkingHead	HyperTwist					interface / visualization / shell surface	subsystem donor	interface donor	donor bench	repurpose	moderate modification	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 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.				Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.	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.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0001	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	met4citizen/talkinghead					MIT	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser embodied coach surface	Included	P2	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.	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.
43		apache/echarts	https://github.com/apache/echarts	HyperTwist					analytics / visualization / reporting	subsystem donor	interface donor	donor bench	repurpose	moderate modification	Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.		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.				Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.	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.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0002	analytics / visualization / reporting	Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.	HyperTwist	analytics / visualization / reporting	repurpose	moderate modification	medium	apache/echarts					Apache-2.0	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser analytics and reporting surface	Included	P2	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.	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.
44		ecomfe/echarts-gl	https://github.com/ecomfe/echarts-gl	HyperTwist					interface / visualization / shell surface	subsystem donor	visualization donor	merge bench	integrate	moderate modification	Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.		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.				Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.	Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0003	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	ecomfe/echarts-gl					BSD-3-Clause	known_from_reference_material	uploaded_reference_docs														Merge Bench	Browser 3D analytics and explainer surface	Included	P3	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 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.
45		KhronosGroup/glTF-Sample-Viewer	https://github.com/KhronosGroup/glTF-Sample-Viewer	HyperTwist					interface / visualization / shell surface	subsystem donor	viewer donor	donor bench	repurpose	moderate modification	Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.		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.				Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.	Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0004	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	khronosgroup/gltf-sample-viewer					Apache-2.0	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser asset validation and viewer surface	Included	P3	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 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.
46		google/model-viewer	https://github.com/google/model-viewer	HyperTwist					interface / visualization / shell surface	subsystem donor	viewer donor	donor bench	repurpose	moderate modification	Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.		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.				Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.	Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0005	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	google/model-viewer					Apache-2.0	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser 3D presentation and inspection surface	Included	P2	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.	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.
47		mrdoob/three.js	https://github.com/mrdoob/three.js	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	donor bench	repurpose	moderate modification	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 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.				Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.	Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0006	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	mrdoob/three.js					MIT	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser 3D substrate	Included	P2	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.
48		pmndrs/postprocessing	https://github.com/pmndrs/postprocessing	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.		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.				Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.	Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0007	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	pmndrs/postprocessing					Zlib	known_from_reference_material	uploaded_reference_docs														Merge Bench	Browser post-processing substrate	Included	P3	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.
49		pmndrs/react-three-fiber	https://github.com/pmndrs/react-three-fiber	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	donor bench	repurpose	moderate modification	Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.		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.				Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.	Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0008	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	pmndrs/react-three-fiber					MIT	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser React 3D substrate	Included	P2	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.
50		pmndrs/drei	https://github.com/pmndrs/drei	HyperTwist					interface / visualization / shell surface	subsystem donor	interface donor	merge bench	integrate	moderate modification	Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.		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.				Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.	Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0009	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	pmndrs/drei					MIT	known_from_reference_material	uploaded_reference_docs														Merge Bench	Browser 3D helper and abstraction layer	Included	P3	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.
51		pmndrs/xr	https://github.com/pmndrs/xr	HyperTwist					interface / visualization / shell surface	subsystem donor	interaction donor	donor bench	repurpose	moderate modification	Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.		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.				Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.	Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0010	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	pmndrs/xr					MIT	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser XR and immersive UI substrate	Included	P2	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.
52		pmndrs/uikit	https://github.com/pmndrs/uikit	HyperTwist					interface / visualization / shell surface	subsystem donor	interface donor	donor bench	repurpose	moderate modification	Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.		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.				Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.	Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0011	browser / 3D / XR / presentation	Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.	HyperTwist	browser / 3D / XR / presentation	repurpose	moderate modification	medium	pmndrs/uikit					MIT	known_from_reference_material	uploaded_reference_docs														Donor Bench	Browser spatial UI surface	Included	P2	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.
53		pmndrs/react-spring	https://github.com/pmndrs/react-spring	HyperTwist					interface / visualization / shell surface	subsystem donor	interaction donor	merge bench	integrate	moderate modification	Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.		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.				Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.	Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host 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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_surface	HT_browser_surface_0012	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	pmndrs/react-spring					MIT	known_from_reference_material	uploaded_reference_docs														Merge Bench	Browser motion and animation layer	Included	P3	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.
54		screenpipe/screenpipe	https://github.com/screenpipe/screenpipe	HyperTwist					capture / replay / support-plane	subsystem donor	support donor	donor bench	repurpose	moderate modification	Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.		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.				the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.	Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_support_sidecars	HT_support_sidecars_0001	support plane / capture / replay	Repurpose selectively for HyperTwist. Its source-backed role is 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.	HyperTwist	support plane / capture / replay	repurpose	moderate modification	medium	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				Donor Bench	Support-plane capture, history, and replay sidecar	Included	P2	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.
55		remotion-dev/remotion	https://github.com/remotion-dev/remotion	HyperTwist					media / rendering / export	subsystem donor	media donor	donor bench	repurpose	moderate modification	Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.		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.				the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.	Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_support_sidecars	HT_support_sidecars_0002	media / rendering / export	Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.	HyperTwist	media / rendering / export	repurpose	moderate modification	medium	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				Donor Bench	Commercially licensed media-export and explainer sidecar	Included	P3	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.
56		ecomfe/zrender	https://github.com/ecomfe/zrender	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.	Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0001	browser / 2D / visualization	Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.	HyperTwist	browser / 2D / visualization	integrate	moderate modification	medium	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				Merge Bench	Browser 2D render substrate	Included	P3	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 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.
57		pissang/claygl	https://github.com/pissang/claygl	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.	Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0002	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser WebGL substrate	Included	P3	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.
58		pissang/clay-viewer	https://github.com/pissang/clay-viewer	HyperTwist					interface / visualization / shell surface	subsystem donor	viewer donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.	Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0003	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser viewer and editor sidecar	Included	P3	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.
59		KhronosGroup/glTF-Sample-Renderer	https://github.com/KhronosGroup/glTF-Sample-Renderer	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.	Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0004	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser asset renderer substrate	Included	P3	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 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.
60		google/model-viewer/packages/space-opera	https://github.com/google/model-viewer/tree/main/packages/space-opera	HyperTwist					interface / visualization / shell surface	subsystem donor	editor donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.	Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0005	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser asset editor and inspection surface	Included	P3	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 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.
61		google/model-viewer/packages/render-fidelity-tools	https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools	HyperTwist					analytics / visualization / reporting	subsystem donor	qa donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.	Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0006	browser / QA / visual regression	Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.	HyperTwist	browser / QA / visual regression	integrate	moderate modification	medium	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				Merge Bench	Browser fidelity QA harness	Included	P3	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 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.
62		google/model-viewer/packages/model-viewer-effects	https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects	HyperTwist					interface / visualization / shell surface	subsystem donor	effect donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.	Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0007	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser emphasis and post-processing extension	Included	P3	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 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.
63		google/model-viewer/packages/modelviewer.dev	https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev	HyperTwist					interface / visualization / shell surface	subsystem donor	docs donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.	Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0008	documentation / demos / examples	Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.	HyperTwist	documentation / demos / examples	integrate	moderate modification	medium	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				Merge Bench	Browser docs and demo surface	Included	P4	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 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.
64		google/model-viewer/packages/shared-assets	https://github.com/google/model-viewer/tree/main/packages/shared-assets	HyperTwist					asset / fixture / sample pack	subsystem donor	fixture donor	donor bench	repurpose	architecture only	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.	Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0009	asset / fixture / sample pack	Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.	HyperTwist	asset / fixture / sample pack	integrate	moderate modification	medium	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				Donor Bench	Boundary-sensitive sample-asset and test-fixture pack	Included	P3	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.
65		pmndrs/react-postprocessing	https://github.com/pmndrs/react-postprocessing	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.	Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0010	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser React effect-wrapper layer	Included	P4	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.
66		pmndrs/three-stdlib	https://github.com/pmndrs/three-stdlib	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.	Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0011	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	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				Merge Bench	Browser 3D utility substrate	Included	P4	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.
67		pmndrs/maath	https://github.com/pmndrs/maath	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.	Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0012	browser / utilities / math	Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.	HyperTwist	browser / utilities / math	integrate	moderate modification	medium	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				Merge Bench	Browser math-helper substrate	Included	P4	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.
68		pmndrs/zustand	https://github.com/pmndrs/zustand	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	donor bench	repurpose	moderate modification	Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.		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.				the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.	Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0013	browser / state / interaction	Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.	HyperTwist	browser / state / interaction	repurpose	moderate modification	medium	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				Donor Bench	Browser state-management substrate	Included	P3	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.
69		pmndrs/leva	https://github.com/pmndrs/leva	HyperTwist					interface / visualization / shell surface	subsystem donor	interface donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.	Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0014	browser / state / interaction	Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.	HyperTwist	browser / state / interaction	integrate	moderate modification	medium	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				Merge Bench	Browser control-panel and parameter UI layer	Included	P4	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.
70		pmndrs/use-gesture	https://github.com/pmndrs/use-gesture	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	donor bench	repurpose	moderate modification	Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.		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.				the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.	Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0015	browser / state / interaction	Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.	HyperTwist	browser / state / interaction	repurpose	moderate modification	medium	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				Donor Bench	Browser gesture and pointer-input substrate	Included	P3	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.
71		@react-spring/parallax	https://github.com/pmndrs/react-spring/tree/main/packages/parallax	HyperTwist					interface / visualization / shell surface	subsystem donor	interface donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.	Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0016	browser / 3D / XR / presentation	Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.	HyperTwist	browser / 3D / XR / presentation	integrate	moderate modification	medium	@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				Merge Bench	Browser layered-motion and explainer sidecar	Included	P4	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.
72		@react-spring/rafz	https://github.com/pmndrs/react-spring/tree/main/packages/rafz	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.	Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0017	browser / utilities / scheduling	Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.	HyperTwist	browser / utilities / scheduling	integrate	moderate modification	medium	@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				Merge Bench	Browser frame-loop and scheduling utility	Included	P4	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.
73		@react-spring/animated	https://github.com/pmndrs/react-spring/tree/main/packages/animated	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.	Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0018	browser / utilities / animation	Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.	HyperTwist	browser / utilities / animation	integrate	moderate modification	medium	@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				Merge Bench	Browser animatable-component substrate	Included	P4	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.
74		@react-spring/core	https://github.com/pmndrs/react-spring/tree/main/packages/core	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	donor bench	repurpose	moderate modification	Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.		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.				the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.	Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0019	browser / utilities / animation	Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.	HyperTwist	browser / utilities / animation	repurpose	moderate modification	medium	@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				Donor Bench	Browser spring-runtime core	Included	P3	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.
75		@react-spring/shared	https://github.com/pmndrs/react-spring/tree/main/packages/shared	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.	Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0020	browser / utilities / animation	Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.	HyperTwist	browser / utilities / animation	integrate	moderate modification	medium	@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				Merge Bench	Browser motion utility substrate	Included	P4	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.
76		@react-spring/types	https://github.com/pmndrs/react-spring/tree/main/packages/types	HyperTwist					interface / visualization / shell surface	subsystem donor	dependency donor	merge bench	integrate	moderate modification	Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.		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.				the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.	Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.	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.														medium	Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.	medium	Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.												HT_browser_support	HT_browser_support_0021	browser / utilities / animation	Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.	HyperTwist	browser / utilities / animation	integrate	moderate modification	medium	@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				Merge Bench	Browser motion type-contract substrate	Included	P4	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.

356 KiB Raw Blame History Unescape Escape

356 KiB

Raw Blame History