From 22b76a48c563f30c80d5738ee36d8a279d5cdbe0 Mon Sep 17 00:00:00 2001
From: axiomlogicnexus <axiomlogicinq@gmail.com>
Date: Wed, 27 May 2026 23:35:04 +0200
Subject: [PATCH] Align higher-dimensional owner row source truth

---
 ...Y_OWNER_ROW_SOURCE_ALIGNMENT_2026-05-27.md | 69 +++++++++++++++++++
 ...epo_portfolio_unified_operational_v6_3.csv |  6 +-
 docs/repo_portfolio_unified_phase_g_v6_3.csv  |  6 +-
 ...po_portfolio_unified_source_audit_v6_3.csv | 12 ++--
 4 files changed, 81 insertions(+), 12 deletions(-)
 create mode 100644 docs/HYPERTWIST_HIGHER_DIMENSIONAL_FAMILY_OWNER_ROW_SOURCE_ALIGNMENT_2026-05-27.md

diff --git a/docs/HYPERTWIST_HIGHER_DIMENSIONAL_FAMILY_OWNER_ROW_SOURCE_ALIGNMENT_2026-05-27.md b/docs/HYPERTWIST_HIGHER_DIMENSIONAL_FAMILY_OWNER_ROW_SOURCE_ALIGNMENT_2026-05-27.md
new file mode 100644
index 0000000..ad990b0
--- /dev/null
+++ b/docs/HYPERTWIST_HIGHER_DIMENSIONAL_FAMILY_OWNER_ROW_SOURCE_ALIGNMENT_2026-05-27.md
@@ -0,0 +1,69 @@
+# HyperTwist Higher-Dimensional Family Owner Row Source Alignment - 2026-05-27
+
+## Status
+
+This document is the row-source truth alignment note for the already-landed
+higher-dimensional permissive owner rows in HyperTwist.
+
+It answers one narrow question:
+
+- after the later live-state and family-hierarchy reconciliations landed, do
+  the `v6.3` source-pack rows still speak about `roice3/MagicTile`,
+  `roice3/Magic120Cell`, and `roice3/MagicCube5D` as donor extraction
+  candidates instead of already-landed first-party owner lanes
+
+Result:
+
+- yes, all three live permissive source-pack rows still carried donor-era
+  extraction, merger-swarm, and promotion/demotion framing
+- the operator board, feature canon, and license tracker were already correct
+- the needed fix is row-source alignment only
+- no product code, live ownership, or roadmap routing changed from this pass
+
+## Affected live owner rows
+
+- `roice3/MagicTile`
+- `roice3/Magic120Cell`
+- `roice3/MagicCube5D`
+
+## Required row-source posture
+
+For these rows the source pack must now say:
+
+- `MagicTile` is already landed for the bounded tiling topology,
+  geometry-family, transform-aware macro remapping, reverse/setup-move
+  playback-tag, and macro-XML compatibility slices
+- `MagicTile` broader WinForms/OpenTK host-shell ownership remains deferred
+- `Magic120Cell` is already landed for the bounded `120-cell` family
+  runtime-profile and persistence slice beneath the retained
+  `Hyperspeedcube` runtime anchor
+- `MagicCube5D` is already landed for the bounded `5D` family runtime-profile
+  and persistence slice beneath the retained `Hyperspeedcube` runtime anchor
+- future work starts from owned HyperTwist surfaces and landed packet
+  authority, not donor promotion or merger routing
+
+## Source basis
+
+- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
+- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
+- `C:\HyperTwist\docs\repo_portfolio_unified_operational_v6_3.csv`
+- `C:\HyperTwist\docs\repo_portfolio_unified_phase_g_v6_3.csv`
+- `C:\HyperTwist\docs\repo_portfolio_unified_source_audit_v6_3.csv`
+
+## Alignment rule
+
+For each affected live row:
+
+- replace donor-extraction realization language with preserve-and-owned-widen
+  language
+- remove merger-swarm routing and cross-project donor-transfer framing
+- replace source-audit goals with owner-boundary validation and owned widening
+  criteria
+- keep current live-state and reset-lane values unchanged
+
+## Final call
+
+These rows are not waiting to be integrated.
+
+They are already integrated for their current justified slices, and the row
+source pack must now describe them that way.
diff --git a/docs/repo_portfolio_unified_operational_v6_3.csv b/docs/repo_portfolio_unified_operational_v6_3.csv
index 22939fd..b9092e9 100644
--- a/docs/repo_portfolio_unified_operational_v6_3.csv
+++ b/docs/repo_portfolio_unified_operational_v6_3.csv
@@ -17,8 +17,8 @@
 "11861","poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","9.0","145.0","171.0","A","restrictive smartcube practice and review comparison context","comparison context","smartcube practice and review shell","restrictive comparison context","integrate","direct","Retain the repo only as restrictive comparison context. Preserve smartcube-aware practice-shell, review or SRS UX, recognition-versus-execution timing presentation, and local stats-history comparison value while excluding owner, donor, or default clean-room-next assumptions.","Comparison-only retained value: smartcube-aware practice-shell behavior, review and SRS UX, recognition-versus-execution timing presentation, and local stats-history comparison context.","Keep only as restrictive comparison context for smartcube-aware practice-shell behavior, review or SRS UX, recognition-versus-execution timing presentation, and local stats-history comparison; do not treat it as a live owner or a default clean-room next row.","Keep behind the landed KubeTimr timer owner, CubeDesk trainer-session owner, broader training foundations, and current first-party training and review-plan owners. Reopen only if a narrower first-party practice or review gap is explicitly proven.","Repurpose here means: preserve comparison context for practice-shell, review, timing-presentation, and local stats-history behavior only.","Capture comparison-only practice-shell and review behaviors; define explicit do-not-open-clean-room-by-default guardrails; record the stronger landed owners that already cover adjacent scope","comparison-context review","Retained value sits in smartcube-aware practice-shell, review, and timing-presentation comparison behavior rather than donor-grade owner surfaces.","Which smartcube-aware practice-shell, review or SRS, timing-presentation, and local stats-history behaviors remain useful only as restrictive comparison context beneath the landed owners?","Inspect practice-shell behavior, review or SRS UX, recognition-versus-execution timing presentation, and local stats-history surfaces as comparison material only.","Audit poliva/cubedex only as restrictive comparison context for HyperTwist. Do not recommend donor promotion or a default clean-room start. Extract only the bounded comparison behaviors that remain useful beneath the landed timer, trainer-session, and training-stack owners.","","","","","","","","","","Restrictive comparison only","Retain only as restrictive comparison, oracle, acceptance-test, or planning input beneath the landed owners.","do not exclude","The repo remains restrictive comparison context only and should not be treated as a live owner or default clean-room next row.","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 - restrictive smartcube practice and review comparison context only; do not reopen donor or default clean-room treatment.","poliva/cubedex is retained only as restrictive comparison context. Its remaining value is in smartcube-aware practice-shell, review, timing-presentation, and local stats-history comparison behavior, not live owner or donor code.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0016","Restrictive smartcube practice and review comparison context","Restrictive smartcube practice and review comparison context for HyperTwist; retained for bounded comparison only.","HyperTwist","Restrictive smartcube practice and review comparison context","integrate","moderate modification","medium","poliva/cubedex","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","9.0","5","145.0","Locked Strategic Donor","Restrictive smartcube practice and review comparison context","","","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible in the current checked mirror. Retain this repo only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison; implement any strategically necessary behavior only from scrubbed first-party specifications if a narrower gap is later proven.","Reference only: restrictive comparison context for smartcube-aware practice-shell, review, timing-presentation, and local stats-history behavior; do not plan direct incorporation or default clean-room reopening.","Do not incorporate source directly without a confirmed license grant.","Yes - this is the preferred path if a narrower smartcube practice/review slice later proves strategically necessary.","medium","no-license-clean-room-benchmark","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Phase 1R plus the 2026-05-27 smartcube practice/review/SRS hierarchy clarification are closed. Retain only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS UX, recognition-versus-execution timing presentation, and local stats/history comparison; do not treat it as a live owner or a default clean-room next row."
 "11865","kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","10.0","145.0","171.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked strategic donor","repurpose","architecture only","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source","kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.","memo","False","True","0.0","4.0","HT_hyper_engine","HT_hyper_engine_0002","cubing / algorithm training","Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.","HyperTwist","hypercubing / nD simulation","integrate","direct","medium","kash/cubedesk","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","10.0","5","145.0","Locked Strategic Donor","Restrictive clean-room donor target","","P1","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","implemented_live_clean_room_verified","landed_clean_room_preserve","Later clean-room sequence closed through Bound 5. Preserve as the landed first-party trainer-session coupling, session-domain, analytics-panel, integrated smart-device workflow, publication/entitlement, and local social challenge owner lane; start future widening from first-party owner surfaces, REPO_LICENSE_TRACKING.md, MODEL_B_SOURCE_ACCESS_BOUNDARY.md, and the scrubbed Model A handoff; never from the restrictive mirror."
 "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.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-B closed. Preserve as the landed attributed legacy 4D interaction, history, macro, topology-reference, and provenance-boundary lane beneath the Hyperspeedcube anchor; start future widening from the live-lane audit, then Phase 4R-B, then REPO_LICENSE_TRACKING.md."
-"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.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
-"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.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
+"11873","roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","12.0","122.0","137.0","A","implemented 120-cell family runtime owner","implemented owner","specialized 120-cell family owner","landed bounded family owner","integrate","direct","This row is already live for its current justified slice. Preserve the landed 120-cell family runtime-profile and persistence boundary beneath the retained Hyperspeedcube runtime anchor, and widen only through owned HyperTwist work.","Landed owner value: 120-cell family runtime-profile and persistence boundary already live in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor.","Preserve as the landed first-party 120-cell family owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-I packet; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner for the landed 120-cell family slice. Keep Hyperspeedcube as the retained runtime anchor and MagicTile as broader family context, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed 120-cell family owner lane, not subsystem harvesting from an external candidate queue.","Validate current first-party owner boundaries; identify narrower owned widening targets only if needed; preserve existing 120-cell runtime-profile and persistence contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed owner boundaries and future owned widening targets, not donor extraction.","Which remaining 120-cell family runtime or persistence gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-I packet beneath the retained Hyperspeedcube anchor?","Inspect current first-party 120-cell family runtime-profile and persistence boundary, the retained Hyperspeedcube anchor relation, retained broader MagicTile family context, and unresolved owned widening targets only.","Audit roice3/Magic120Cell only as an already-landed permissive family owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist for its bounded 120-cell family slice. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","do not exclude","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","high","single-source signal; clear taxonomy; active integration value; bounded specialized-family fit","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 already landed for its current justified 120-cell family runtime-profile and persistence slice beneath the retained Hyperspeedcube runtime anchor. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0004","Implemented 120-cell family runtime owner","Landed 120-cell family owner lane for HyperTwist; validate boundaries and widen only through owned first-party work beneath the retained Hyperspeedcube runtime anchor.","HyperTwist","Implemented 120-cell family runtime owner","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","Implemented 120-cell family runtime owner lane","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified 120-cell family runtime slice is already implemented in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party 120-cell family owner surfaces plus landed packet authority beneath the retained Hyperspeedcube anchor.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-specialized-family-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
+"11877","roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","13.0","122.0","137.0","A","implemented 5D family runtime owner","implemented owner","specialized 5D family owner","landed bounded family owner","integrate","direct","This row is already live for its current justified slice. Preserve the landed 5D family runtime-profile and persistence boundary beneath the retained Hyperspeedcube runtime anchor, and widen only through owned HyperTwist work.","Landed owner value: 5D family runtime-profile and persistence boundary already live in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor.","Preserve as the landed first-party 5D family owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-J packet; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner for the landed 5D family slice. Keep Hyperspeedcube as the retained runtime anchor and MagicTile as broader family context, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed 5D family owner lane, not subsystem harvesting from an external candidate queue.","Validate current first-party owner boundaries; identify narrower owned widening targets only if needed; preserve existing 5D runtime-profile and persistence contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed owner boundaries and future owned widening targets, not donor extraction.","Which remaining 5D family runtime or persistence gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-J packet beneath the retained Hyperspeedcube anchor?","Inspect current first-party 5D family runtime-profile and persistence boundary, the retained Hyperspeedcube anchor relation, retained broader MagicTile family context, and unresolved owned widening targets only.","Audit roice3/MagicCube5D only as an already-landed permissive family owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist for its bounded 5D family slice. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","do not exclude","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","high","single-source signal; clear taxonomy; active integration value; bounded specialized-family fit","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 already landed for its current justified 5D family runtime-profile and persistence slice beneath the retained Hyperspeedcube runtime anchor. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0005","Implemented 5D family runtime owner","Landed 5D family owner lane for HyperTwist; validate boundaries and widen only through owned first-party work beneath the retained Hyperspeedcube runtime anchor.","HyperTwist","Implemented 5D family runtime owner","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","Implemented 5D family runtime owner lane","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified 5D family runtime slice is already implemented in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party 5D family owner surfaces plus landed packet authority beneath the retained Hyperspeedcube runtime anchor.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-specialized-family-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
 "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.","Capture bounded benchmark or oracle behaviors; define acceptance criteria or clean-room-later planning boundaries; record explicit do-not-incorporate guardrails","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.","","","","","","","","","","Reference only","Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later 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."
 "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.","Confirm discard basis; record stronger surviving rows; preserve only historical comparison notes if a future operator needs context","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.","","","","","","","","","","Historical comparison only","Retain only as discarded historical comparison context; do not plan donor, merge, or clean-room reopening from this row.","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."
 "11893","brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","17.0","119.0","134.0","B","reference-only immersive live-coding benchmark","benchmark","immersive live-coding shell","Reserve Bench","future candidate","architecture only","Retain the interaction shell only as historical comparison context. For this repo class, preserve live sketch-loop, world-space monitor/text-area placement, and WebXR scene-update patterns as design reference while excluding donor, calibration, or product-shell assumptions.","Benchmark-only retained value: immersive live-coding, world-space monitor, text-entry, and real-time scene-update patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.","Keep in permissive/reference custody. Use only as a benchmark for immersive live-coding, world-space text-entry, and live scene-update interaction ideas; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated live-coding, world-space monitor, and text-entry interaction ideas into first-party browser/XR surfaces without inheriting the product shell.","Repurpose here means: abstract live-coding loop, text-entry, world-space monitor, and scene-update interaction ideas into first-party browser/XR surfaces without reusing source.","Confirm discard basis; record stronger surviving rows; preserve only historical comparison notes if a future operator needs context","behavior-level benchmark review","Hidden value sits in the live sketch loop, world-space monitor/text-area choreography, and immediate scene-update behavior rather than in any retained HyperTwist owner subsystem.","Which live-coding, world-space monitor, text-area, and real-time scene-update patterns are reusable at the behavior level without inheriting the WebXR live-coding shell or reopening an off-topic product lane?","Inspect README/docs, sketch loop, dynamic code execution, local sketch persistence, text-area/monitor composition, WebXR session entry, and scene interception as benchmark material only.","Audit brianpeiris/RiftSketch only as a reference-only immersive live-coding benchmark for HyperTwist. Do not recommend direct incorporation. Extract live-coding loop, world-space monitor, text-entry, and scene-update interaction ideas only.","","","","","","","","","","Historical comparison only","Retain only as discarded historical comparison context; do not plan donor, merge, or clean-room reopening from this row.","exclude from standalone? no","The repo is a niche MIT WebXR live-coding shell and materially off-mission for HyperTwist; retain only as a reference benchmark.","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 - MIT WebXR live-coding shell; keep only as a reference-only immersive live-coding benchmark for interaction ideas.","brianpeiris/RiftSketch is retained only as a reference-only immersive live-coding benchmark. It is a legitimate WebXR live-coding shell, but its product identity is off-topic and its value is limited to interaction ideas rather than donor code.","memo","False","True","0.0","3.0","HT_cube_vision","HT_cube_vision_0006","Reference-only immersive live-coding benchmark","Reference-only immersive live-coding benchmark for HyperTwist; not a donor lane.","HyperTwist","Reference-only immersive live-coding benchmark","future candidate","architecture only","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","Reference-only immersive live-coding benchmark","Included","P3","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, world-space monitor, and text-entry interaction 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; its immersive live-coding value is off-topic and already superseded by stronger retained browser/XR, capture, and export rows."
@@ -37,7 +37,7 @@
 "11936","yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","31.0","117.0","132.0","B","learned heuristic search / offline solver experimentation","research benchmark","solver experimentation benchmark","research benchmark","future candidate","architecture only","Retain the valuable internal research engine, but keep it below live product ownership. For this repo class, preserve sticker-state transition encoding, ADI state generation, batched neural search, and offline experiment loops while excluding camera UX, PyQt shell behavior, and near-term product runtime assumptions.","Benchmark-only retained value: 54-sticker transition encoding, ADI training-state generation, batched neural A* search, and compact value-network experimentation worth preserving as research reference.","Keep only as a research benchmark. Use it to shape first-party learned heuristic search, ADI state-generation, and offline solver experimentation if HyperTwist ever opens that lane; do not treat it as a live camera, calibration, recognition, or product-shell donor.","Keep behind the landed qbr and rubix-cube-solver recognition owners and behind the retained brownan/efrantar solver-oracle owners. Revisit only if HyperTwist intentionally opens a first-party ML search or offline experimentation lane.","Repurpose here means: mine cube-state transition encoding, ADI target-generation loops, batched heuristic-search experiments, and small value-network research rather than camera UX or product shell behavior.","Capture bounded benchmark or oracle behaviors; define acceptance criteria or clean-room-later planning boundaries; record explicit do-not-incorporate guardrails","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 cube-state encoding; move-transition tables; ADI state generation; batched A* evaluation; value-network shape; offline training loop; and experiment boundaries. Explicitly exclude camera/perception shell claims from owner judgment.","Inspect README/docs, cube-state model, move-transition tables, search loop, ADI generation, network architecture, training scripts, and experiment configuration. Look for reusable search research primitives rather than camera UX, PyQt shell flows, or live perception assumptions.","Audit yakupbilen/drl-rubiks-cube as a learned-search and offline experimentation benchmark for HyperTwist. Do not stop at README-level claims. Inspect cube-state encoding, move-transition tables, ADI generation, batched neural A* search, value-network shape, and experiment loops. Decide whether the repo remains a non-live research benchmark and identify only those primitives that would matter if a future first-party ML search lane is intentionally opened. Do not treat camera UX or PyQt shell behavior as owner evidence.","","","","","","","","","","Reference only","Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later planning input.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; retained research value; not a live owner lane","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","solver research / experimentation","Retain only as an MIT research benchmark for learned heuristic search, ADI state generation, and offline solver experimentation. Its strongest current value is research logic, not live perception or product shell ownership.","HyperTwist","solver research / experimentation","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."
 "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."
 "11945","Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","34.0","88.0","97.0","C","implemented timer substrate owner","implemented owner","timer substrate owner","landed subsystem owner","repurpose","moderate modification","This row is already live for its current justified slices. Preserve the landed local timer lifecycle, inspection, split capture and editing, session stats, local persistence, and timer-scoped replay boundaries, and widen only through owned HyperTwist work.","Landed owner value: timer lifecycle, inspection, split capture and editing, session stats, local persistence, and timer-scoped replay posture already live in first-party HyperTwist code.","Preserve as the landed first-party timer substrate owner lane. Start any future widening from owned HyperTwist surfaces, the timer implementation packet, FEATURE_REGISTRY, ROADMAP, and REPO_LICENSE_TRACKING; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner. Keep cstimer as the retained restrictive oracle, cubing/qqTimer as legacy reference, and CubeDesk as adjacent live trainer-session and smart-device workflow composition rather than donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed timer substrate owner lane, not external donor harvesting.","Validate current first-party timer owner boundaries; identify narrower owned widening targets only if needed; preserve timer lifecycle, inspection, splits, persistence, stats, and timer-scoped replay contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed timer owner boundaries and future owned widening targets, not donor extraction.","Which remaining timer-substrate gaps, if any, are not already covered by the landed HyperTwist code and the KubeTimr implementation packet?","Inspect current first-party timer owner boundaries, landed packet scope, retained timer oracle and reference rows, and unresolved owned widening targets only.","Audit Aarav2709/KubeTimr only as an already-landed permissive owner lane for HyperTwist. Validate current timer owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","exclude from core, keep as donor","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","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 - landed first-party timer substrate owner lane; future work starts from owned HyperTwist surfaces and landed packets.","Aarav2709/KubeTimr is already landed for its current justified timer lifecycle, inspection, split, persistence, stats, and timer-scoped replay slices. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0015","Implemented timer substrate owner","Landed timer substrate owner lane for HyperTwist; validate boundaries and widen only through owned first-party work.","HyperTwist","Implemented timer substrate owner","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","Implemented timer substrate owner lane","","","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.","Already landed: start from first-party owner surfaces and landed packet authority, not donor-transfer framing.","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."
-"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.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
+"11951","roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","36.0","88.0","97.0","C","implemented non-Euclidean topology and macro owner","implemented owner","non-Euclidean topology owner","landed bounded topology owner","integrate","direct","This row is already live for its current justified slices. Preserve the landed tiling topology, geometry-family contract, transform-aware macro remapping, reverse/setup-move playback tags, and macro XML compatibility boundary, and widen only through owned HyperTwist work while the broader host-shell remainder stays deferred.","Landed owner value: tiling topology, geometry-family contract, transform-aware macro remapping, reverse/setup-move playback tags, and macro XML compatibility boundary already live in first-party HyperTwist code.","Preserve as the landed first-party MagicTile owner lane for bounded topology and transform-aware macro surfaces. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-D/T packets; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner for the landed MagicTile topology and macro slices. Keep the broader MagicTile host-shell remainder, Hyperspeedcube, and the specialized Magic120Cell and MagicCube5D families as deferred or adjacent context, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed MagicTile owner lane, not subsystem harvesting from an external candidate queue.","Validate current first-party owner boundaries; identify narrower owned widening targets only if needed; preserve existing topology, geometry-family, transform-aware macro, reverse/setup-move, and macro XML contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed owner boundaries and future owned widening targets, not donor extraction.","Which remaining non-Euclidean topology, transform-aware macro, or host-shell remainder gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-D/T packets?","Inspect current first-party topology and geometry-family boundaries, transform-aware macro remapping and macro XML compatibility boundaries, the deferred broader MagicTile host-shell remainder, and unresolved owned widening targets only.","Audit roice3/MagicTile only as an already-landed permissive owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist for its bounded topology and macro slices. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","do not exclude","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","high","single-source signal; clear taxonomy; active integration value; bounded landed owner lane","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 already landed for its current justified tiling topology, geometry-family, transform-aware macro remapping, reverse/setup-move playback-tag, and macro XML compatibility slices. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0007","Implemented non-Euclidean topology and macro owner","Landed non-Euclidean topology owner lane for HyperTwist; validate boundaries and widen only through owned first-party work while the broader host-shell remainder stays deferred.","HyperTwist","Implemented non-Euclidean topology and macro owner","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","Implemented non-Euclidean topology and macro owner lane","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified topology and transform-aware macro slice is already implemented in first-party HyperTwist code. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party topology and macro owner surfaces plus landed packet authority, and keep the broader host-shell remainder deferred unless a later owned widening is justified.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-bounded-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
 "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.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-D closed. Preserve as the landed first-party control-plane telemetry, replay-diagnostic, scheduled-change, early-access, and explicit root-MIT-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-D, then REPO_LICENSE_TRACKING.md; keep the explicit ee/ exclusion and mixed-license subtree boundary visible."
 "","met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","","","","","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.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md."
 "","apache/echarts","https://github.com/apache/echarts","HyperTwist","","","","","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.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md."
diff --git a/docs/repo_portfolio_unified_phase_g_v6_3.csv b/docs/repo_portfolio_unified_phase_g_v6_3.csv
index 9608bc7..36e632b 100644
--- a/docs/repo_portfolio_unified_phase_g_v6_3.csv
+++ b/docs/repo_portfolio_unified_phase_g_v6_3.csv
@@ -17,8 +17,8 @@
 "10.0","poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","9.0","145.0","171.0","A","restrictive smartcube practice and review comparison context","comparison context","smartcube practice and review shell","restrictive comparison context","integrate","direct","Retain the repo only as restrictive comparison context. Preserve smartcube-aware practice-shell, review or SRS UX, recognition-versus-execution timing presentation, and local stats-history comparison value while excluding owner, donor, or default clean-room-next assumptions.","Comparison-only retained value: smartcube-aware practice-shell behavior, review and SRS UX, recognition-versus-execution timing presentation, and local stats-history comparison context.","Keep only as restrictive comparison context for smartcube-aware practice-shell behavior, review or SRS UX, recognition-versus-execution timing presentation, and local stats-history comparison; do not treat it as a live owner or a default clean-room next row.","Keep behind the landed KubeTimr timer owner, CubeDesk trainer-session owner, broader training foundations, and current first-party training and review-plan owners. Reopen only if a narrower first-party practice or review gap is explicitly proven.","Repurpose here means: preserve comparison context for practice-shell, review, timing-presentation, and local stats-history behavior only.","Capture comparison-only practice-shell and review behaviors; define explicit do-not-open-clean-room-by-default guardrails; record the stronger landed owners that already cover adjacent scope","comparison-context review","Retained value sits in smartcube-aware practice-shell, review, and timing-presentation comparison behavior rather than donor-grade owner surfaces.","Which smartcube-aware practice-shell, review or SRS, timing-presentation, and local stats-history behaviors remain useful only as restrictive comparison context beneath the landed owners?","Inspect practice-shell behavior, review or SRS UX, recognition-versus-execution timing presentation, and local stats-history surfaces as comparison material only.","Audit poliva/cubedex only as restrictive comparison context for HyperTwist. Do not recommend donor promotion or a default clean-room start. Extract only the bounded comparison behaviors that remain useful beneath the landed timer, trainer-session, and training-stack owners.","","","","","","","","","","Restrictive comparison only","Retain only as restrictive comparison, oracle, acceptance-test, or planning input beneath the landed owners.","do not exclude","The repo remains restrictive comparison context only and should not be treated as a live owner or default clean-room next row.","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 - restrictive smartcube practice and review comparison context only; do not reopen donor or default clean-room treatment.","poliva/cubedex is retained only as restrictive comparison context. Its remaining value is in smartcube-aware practice-shell, review, timing-presentation, and local stats-history comparison behavior, not live owner or donor code.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0016","Restrictive smartcube practice and review comparison context","Restrictive smartcube practice and review comparison context for HyperTwist; retained for bounded comparison only.","HyperTwist","Restrictive smartcube practice and review comparison context","integrate","moderate modification","medium","poliva/cubedex","1.0","Locked Strategic Donor","3.0","Restrictive smartcube trainer shell with bounded comparison value but no surviving live-owner or default clean-room-next posture.","Restrictive smartcube practice and review comparison context","Included","P1","Keep in canon only as restrictive comparison context beneath the landed timer, trainer-session, and training-stack owners.","2.0","5.0","3.0","11861.0","116.0","","poliva/cubedex","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","9.0","2","3.0","145.0","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible in the current checked mirror. Retain this repo only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison; implement any strategically necessary behavior only from scrubbed first-party specifications if a narrower gap is later proven.","Reference only: restrictive comparison context for smartcube-aware practice-shell, review, timing-presentation, and local stats-history behavior; do not plan direct incorporation or default clean-room reopening.","Do not incorporate source directly without a confirmed license grant.","Yes - this is the preferred path if a narrower smartcube practice/review slice later proves strategically necessary.","medium","no-license-clean-room-benchmark","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Phase 1R plus the 2026-05-27 smartcube practice/review/SRS hierarchy clarification are closed. Retain only as restrictive comparison context for smartcube-aware practice-shell behavior, review/SRS UX, recognition-versus-execution timing presentation, and local stats/history comparison; do not treat it as a live owner or a default clean-room next row."
 "9.0","kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","10.0","145.0","171.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked strategic donor","repurpose","architecture only","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source","kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.","memo","False","True","0.0","4.0","HT_hyper_engine","HT_hyper_engine_0002","cubing / algorithm training","Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.","HyperTwist","hypercubing / nD simulation","integrate","direct","medium","kash/cubedesk","1.0","Locked Strategic Donor","3.0","Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.","Restrictive clean-room donor target","Included","P1","Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.","2.0","5.0","3.0","11865.0","117.0","","kash/cubedesk","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","10.0","2","3.0","145.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","implemented_live_clean_room_verified","landed_clean_room_preserve","Later clean-room sequence closed through Bound 5. Preserve as the landed first-party trainer-session coupling, session-domain, analytics-panel, integrated smart-device workflow, publication/entitlement, and local social challenge owner lane; start future widening from first-party owner surfaces, REPO_LICENSE_TRACKING.md, MODEL_B_SOURCE_ACCESS_BOUNDARY.md, and the scrubbed Model A handoff; never from the restrictive mirror."
 "12.0","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","1.0","Locked Strategic Donor","5.0","Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.","Top-tier 4D interaction, history, and macro donor with attribution obligations","Included","P1","Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.","2.0","3.0","3.0","11871.0","118.0","","cutelyaware/magiccube4d","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","11.0","3","5.0","122.0","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.","Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.","Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.","medium","custom-license-attribution-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-B closed. Preserve as the landed attributed legacy 4D interaction, history, macro, topology-reference, and provenance-boundary lane beneath the Hyperspeedcube anchor; start future widening from the live-lane audit, then Phase 4R-B, then REPO_LICENSE_TRACKING.md."
-"13.0","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","1.0","Locked Strategic Donor","5.0","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Specialized 4D interaction and puzzle-UX donor","Included","P1","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","2.0","3.0","3.0","11875.0","119.0","","roice3/magic120cell","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","12.0","3","5.0","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
-"14.0","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","1.0","Locked Strategic Donor","5.0","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Specialized 5D cube interaction, progress, and macro donor","Included","P1","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","2.0","3.0","3.0","11879.0","120.0","","roice3/magiccube5d","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","13.0","3","5.0","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
+"13.0","roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","12.0","122.0","137.0","A","implemented 120-cell family runtime owner","implemented owner","specialized 120-cell family owner","landed bounded family owner","integrate","direct","This row is already live for its current justified slice. Preserve the landed 120-cell family runtime-profile and persistence boundary beneath the retained Hyperspeedcube runtime anchor, and widen only through owned HyperTwist work.","Landed owner value: 120-cell family runtime-profile and persistence boundary already live in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor.","Preserve as the landed first-party 120-cell family owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-I packet; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner for the landed 120-cell family slice. Keep Hyperspeedcube as the retained runtime anchor and MagicTile as broader family context, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed 120-cell family owner lane, not subsystem harvesting from an external candidate queue.","Validate current first-party owner boundaries; identify narrower owned widening targets only if needed; preserve existing 120-cell runtime-profile and persistence contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed owner boundaries and future owned widening targets, not donor extraction.","Which remaining 120-cell family runtime or persistence gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-I packet beneath the retained Hyperspeedcube anchor?","Inspect current first-party 120-cell family runtime-profile and persistence boundary, the retained Hyperspeedcube anchor relation, retained broader MagicTile family context, and unresolved owned widening targets only.","Audit roice3/Magic120Cell only as an already-landed permissive family owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist for its bounded 120-cell family slice. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","do not exclude","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","high","single-source signal; clear taxonomy; active integration value; bounded specialized-family fit","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 already landed for its current justified 120-cell family runtime-profile and persistence slice beneath the retained Hyperspeedcube runtime anchor. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0004","Implemented 120-cell family runtime owner","Landed 120-cell family owner lane for HyperTwist; validate boundaries and widen only through owned first-party work beneath the retained Hyperspeedcube runtime anchor.","HyperTwist","Implemented 120-cell family runtime owner","integrate","heavy modification","medium","roice3/magic120cell","1.0","Locked Strategic Donor","5.0","Already-landed 120-cell family owner row for bounded runtime-profile and persistence families beneath the retained Hyperspeedcube anchor; no donor thesis remains for the current slice.","Implemented 120-cell family runtime owner lane","Included","P1","Keep in canon as an already-landed first-party 120-cell family owner lane and route all future work through owned widening beneath the retained Hyperspeedcube runtime anchor.","2.0","3.0","3.0","11875.0","119.0","","roice3/magic120cell","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","12.0","3","5.0","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified 120-cell family runtime slice is already implemented in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party 120-cell family owner surfaces plus landed packet authority beneath the retained Hyperspeedcube anchor.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-specialized-family-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
+"14.0","roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","13.0","122.0","137.0","A","implemented 5D family runtime owner","implemented owner","specialized 5D family owner","landed bounded family owner","integrate","direct","This row is already live for its current justified slice. Preserve the landed 5D family runtime-profile and persistence boundary beneath the retained Hyperspeedcube runtime anchor, and widen only through owned HyperTwist work.","Landed owner value: 5D family runtime-profile and persistence boundary already live in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor.","Preserve as the landed first-party 5D family owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-J packet; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner for the landed 5D family slice. Keep Hyperspeedcube as the retained runtime anchor and MagicTile as broader family context, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed 5D family owner lane, not subsystem harvesting from an external candidate queue.","Validate current first-party owner boundaries; identify narrower owned widening targets only if needed; preserve existing 5D runtime-profile and persistence contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed owner boundaries and future owned widening targets, not donor extraction.","Which remaining 5D family runtime or persistence gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-J packet beneath the retained Hyperspeedcube anchor?","Inspect current first-party 5D family runtime-profile and persistence boundary, the retained Hyperspeedcube anchor relation, retained broader MagicTile family context, and unresolved owned widening targets only.","Audit roice3/MagicCube5D only as an already-landed permissive family owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist for its bounded 5D family slice. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","do not exclude","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","high","single-source signal; clear taxonomy; active integration value; bounded specialized-family fit","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 already landed for its current justified 5D family runtime-profile and persistence slice beneath the retained Hyperspeedcube runtime anchor. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0005","Implemented 5D family runtime owner","Landed 5D family owner lane for HyperTwist; validate boundaries and widen only through owned first-party work beneath the retained Hyperspeedcube runtime anchor.","HyperTwist","Implemented 5D family runtime owner","integrate","moderate modification","medium","roice3/magiccube5d","1.0","Locked Strategic Donor","5.0","Already-landed 5D family owner row for bounded runtime-profile and persistence families beneath the retained Hyperspeedcube anchor; no donor thesis remains for the current slice.","Implemented 5D family runtime owner lane","Included","P1","Keep in canon as an already-landed first-party 5D family owner lane and route all future work through owned widening beneath the retained Hyperspeedcube runtime anchor.","2.0","3.0","3.0","11879.0","120.0","","roice3/magiccube5d","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","13.0","3","5.0","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified 5D family runtime slice is already implemented in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party 5D family owner surfaces plus landed packet authority beneath the retained Hyperspeedcube runtime anchor.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-specialized-family-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
 "11.0","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.","Capture bounded benchmark or oracle behaviors; define acceptance criteria or clean-room-later planning boundaries; record explicit do-not-incorporate guardrails","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.","","","","","","","","","","Reference only","Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later 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","1.0","Reserve Bench","3.0","GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.","Gold-standard timer benchmark","Included","P2","Keep in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.","2.0","5.0","3.0","11881.0","121.0","","cs0x7f/cstimer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","14.0","2","3.0","121.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.","high","gpl-timer-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle."
 "16.0","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.","Confirm discard basis; record stronger surviving rows; preserve only historical comparison notes if a future operator needs context","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.","","","","","","","","","","Historical comparison only","Retain only as discarded historical comparison context; do not plan donor, merge, or clean-room reopening from this row.","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/code-xr","1.0","Reserve Bench","5.0","GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.","Reference-only XR benchmark","Included","P3","Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.","2.0","3.0","3.0","11890.0","3226.0","","amontesl/codexr","HyperTwist","","","","","","","","","","Original global Phase G v4 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","","v6_unified_source_of_truth_pack","16.0","3","5.0","119.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-reference-only-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows."
 "17.0","brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","17.0","119.0","134.0","B","reference-only immersive live-coding benchmark","benchmark","immersive live-coding shell","Reserve Bench","future candidate","architecture only","Retain the interaction shell only as historical comparison context. For this repo class, preserve live sketch-loop, world-space monitor/text-area placement, and WebXR scene-update patterns as design reference while excluding donor, calibration, or product-shell assumptions.","Benchmark-only retained value: immersive live-coding, world-space monitor, text-entry, and real-time scene-update patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.","Keep in permissive/reference custody. Use only as a benchmark for immersive live-coding, world-space text-entry, and live scene-update interaction ideas; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated live-coding, world-space monitor, and text-entry interaction ideas into first-party browser/XR surfaces without inheriting the product shell.","Repurpose here means: abstract live-coding loop, text-entry, world-space monitor, and scene-update interaction ideas into first-party browser/XR surfaces without reusing source.","Confirm discard basis; record stronger surviving rows; preserve only historical comparison notes if a future operator needs context","behavior-level benchmark review","Hidden value sits in the live sketch loop, world-space monitor/text-area choreography, and immediate scene-update behavior rather than in any retained HyperTwist owner subsystem.","Which live-coding, world-space monitor, text-area, and real-time scene-update patterns are reusable at the behavior level without inheriting the WebXR live-coding shell or reopening an off-topic product lane?","Inspect README/docs, sketch loop, dynamic code execution, local sketch persistence, text-area/monitor composition, WebXR session entry, and scene interception as benchmark material only.","Audit brianpeiris/RiftSketch only as a reference-only immersive live-coding benchmark for HyperTwist. Do not recommend direct incorporation. Extract live-coding loop, world-space monitor, text-entry, and scene-update interaction ideas only.","","","","","","","","","","Historical comparison only","Retain only as discarded historical comparison context; do not plan donor, merge, or clean-room reopening from this row.","exclude from standalone? no","The repo is a niche MIT WebXR live-coding shell and materially off-mission for HyperTwist; retain only as a reference benchmark.","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 - MIT WebXR live-coding shell; keep only as a reference-only immersive live-coding benchmark for interaction ideas.","brianpeiris/RiftSketch is retained only as a reference-only immersive live-coding benchmark. It is a legitimate WebXR live-coding shell, but its product identity is off-topic and its value is limited to interaction ideas rather than donor code.","memo","False","True","0.0","3.0","HT_cube_vision","HT_cube_vision_0006","Reference-only immersive live-coding benchmark","Reference-only immersive live-coding benchmark for HyperTwist; not a donor lane.","HyperTwist","Reference-only immersive live-coding benchmark","future candidate","architecture only","medium","brianpeiris/riftsketch","1.0","Reserve Bench","5.0","Useful MIT WebXR live-coding and world-space monitor benchmark for immersive tooling patterns, but explicitly off-topic to HyperTwist's retained product scope.","Reference-only immersive live-coding benchmark","Included","P3","Keep in canon only as a reference-only immersive live-coding benchmark; its value is in live-coding, world-space monitor, text-entry, and scene-update ideas, not donor code.","2.0","3.0","3.0","11894.0","3227.0","","brianpeiris/riftsketch","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","17.0","3","5.0","119.0","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.","Reference only: discarded historical comparison context for immersive live-coding, world-space monitor, and text-entry interaction 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; its immersive live-coding value is off-topic and already superseded by stronger retained browser/XR, capture, and export rows."
@@ -37,7 +37,7 @@
 "31.0","yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","31.0","117.0","132.0","B","learned heuristic search / offline solver experimentation","research benchmark","solver experimentation benchmark","research benchmark","future candidate","architecture only","Retain the valuable internal research engine, but keep it below live product ownership. For this repo class, preserve sticker-state transition encoding, ADI state generation, batched neural search, and offline experiment loops while excluding camera UX, PyQt shell behavior, and near-term product runtime assumptions.","Benchmark-only retained value: 54-sticker transition encoding, ADI training-state generation, batched neural A* search, and compact value-network experimentation worth preserving as research reference.","Keep only as a research benchmark. Use it to shape first-party learned heuristic search, ADI state-generation, and offline solver experimentation if HyperTwist ever opens that lane; do not treat it as a live camera, calibration, recognition, or product-shell donor.","Keep behind the landed qbr and rubix-cube-solver recognition owners and behind the retained brownan/efrantar solver-oracle owners. Revisit only if HyperTwist intentionally opens a first-party ML search or offline experimentation lane.","Repurpose here means: mine cube-state transition encoding, ADI target-generation loops, batched heuristic-search experiments, and small value-network research rather than camera UX or product shell behavior.","Capture bounded benchmark or oracle behaviors; define acceptance criteria or clean-room-later planning boundaries; record explicit do-not-incorporate guardrails","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 cube-state encoding; move-transition tables; ADI state generation; batched A* evaluation; value-network shape; offline training loop; and experiment boundaries. Explicitly exclude camera/perception shell claims from owner judgment.","Inspect README/docs, cube-state model, move-transition tables, search loop, ADI generation, network architecture, training scripts, and experiment configuration. Look for reusable search research primitives rather than camera UX, PyQt shell flows, or live perception assumptions.","Audit yakupbilen/drl-rubiks-cube as a learned-search and offline experimentation benchmark for HyperTwist. Do not stop at README-level claims. Inspect cube-state encoding, move-transition tables, ADI generation, batched neural A* search, value-network shape, and experiment loops. Decide whether the repo remains a non-live research benchmark and identify only those primitives that would matter if a future first-party ML search lane is intentionally opened. Do not treat camera UX or PyQt shell behavior as owner evidence.","","","","","","","","","","Reference only","Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later planning input.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; retained research value; not a live owner lane","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","solver research / experimentation","Retain only as an MIT research benchmark for learned heuristic search, ADI state generation, and offline solver experimentation. Its strongest current value is research logic, not live perception or product shell ownership.","HyperTwist","solver research / experimentation","integrate","moderate modification","medium","yakupbilen/drl-rubiks-cube","1.0","Reserve Bench","5.0","Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.","Search/training systems bench","Included","P2","yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","3.0","3.0","11937.0","133.0","","yakupbilen/drl-rubiks-cube","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","31.0","3","5.0","117.0","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.","Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation."
 "32.0","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","1.0","Locked Strategic Donor","4.0","MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.","Knowledge and curriculum donor","Included","P1","Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.","2.0","2.0","2.0","11938.0","134.0","Thin-fit assignment; verify project mapping during source audit","hypercubers/hypercubing.xyz","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","32.0","3","4.0","92.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.","Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.","high","permissive-knowledge-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md."
 "34.0","Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","34.0","88.0","97.0","C","implemented timer substrate owner","implemented owner","timer substrate owner","landed subsystem owner","repurpose","moderate modification","This row is already live for its current justified slices. Preserve the landed local timer lifecycle, inspection, split capture and editing, session stats, local persistence, and timer-scoped replay boundaries, and widen only through owned HyperTwist work.","Landed owner value: timer lifecycle, inspection, split capture and editing, session stats, local persistence, and timer-scoped replay posture already live in first-party HyperTwist code.","Preserve as the landed first-party timer substrate owner lane. Start any future widening from owned HyperTwist surfaces, the timer implementation packet, FEATURE_REGISTRY, ROADMAP, and REPO_LICENSE_TRACKING; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner. Keep cstimer as the retained restrictive oracle, cubing/qqTimer as legacy reference, and CubeDesk as adjacent live trainer-session and smart-device workflow composition rather than donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed timer substrate owner lane, not external donor harvesting.","Validate current first-party timer owner boundaries; identify narrower owned widening targets only if needed; preserve timer lifecycle, inspection, splits, persistence, stats, and timer-scoped replay contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed timer owner boundaries and future owned widening targets, not donor extraction.","Which remaining timer-substrate gaps, if any, are not already covered by the landed HyperTwist code and the KubeTimr implementation packet?","Inspect current first-party timer owner boundaries, landed packet scope, retained timer oracle and reference rows, and unresolved owned widening targets only.","Audit Aarav2709/KubeTimr only as an already-landed permissive owner lane for HyperTwist. Validate current timer owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","exclude from core, keep as donor","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","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 - landed first-party timer substrate owner lane; future work starts from owned HyperTwist surfaces and landed packets.","Aarav2709/KubeTimr is already landed for its current justified timer lifecycle, inspection, split, persistence, stats, and timer-scoped replay slices. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0015","Implemented timer substrate owner","Landed timer substrate owner lane for HyperTwist; validate boundaries and widen only through owned first-party work.","HyperTwist","Implemented timer substrate owner","integrate","moderate modification","medium","aarav2709/kubetimr","1.0","Donor Bench","4.0","Already-landed timer owner row for bounded lifecycle, inspection, split, persistence, stats, and timer-scoped replay families; no donor thesis remains for the current slice.","Implemented timer substrate owner lane","Included","P2","Keep in canon as an already-landed first-party timer owner lane and route all future work through owned widening.","2.0","3.0","2.0","11944.0","135.0","","aarav2709/kubetimr","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","34.0","3","4.0","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Already landed: start from first-party owner surfaces and landed packet authority, not donor-transfer framing.","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."
-"36.0","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","1.0","Locked Strategic Donor","4.0","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Top-tier non-Euclidean geometry and topology donor","Included","P1","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","2.0","2.0","2.0","11950.0","136.0","Thin-fit assignment; verify project mapping during source audit","roice3/magictile","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","36.0","3","4.0","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
+"36.0","roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","36.0","88.0","97.0","C","implemented non-Euclidean topology and macro owner","implemented owner","non-Euclidean topology owner","landed bounded topology owner","integrate","direct","This row is already live for its current justified slices. Preserve the landed tiling topology, geometry-family contract, transform-aware macro remapping, reverse/setup-move playback tags, and macro XML compatibility boundary, and widen only through owned HyperTwist work while the broader host-shell remainder stays deferred.","Landed owner value: tiling topology, geometry-family contract, transform-aware macro remapping, reverse/setup-move playback tags, and macro XML compatibility boundary already live in first-party HyperTwist code.","Preserve as the landed first-party MagicTile owner lane for bounded topology and transform-aware macro surfaces. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-D/T packets; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner for the landed MagicTile topology and macro slices. Keep the broader MagicTile host-shell remainder, Hyperspeedcube, and the specialized Magic120Cell and MagicCube5D families as deferred or adjacent context, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed MagicTile owner lane, not subsystem harvesting from an external candidate queue.","Validate current first-party owner boundaries; identify narrower owned widening targets only if needed; preserve existing topology, geometry-family, transform-aware macro, reverse/setup-move, and macro XML contracts; keep notices and attribution visible","live owner boundary review","Remaining value is in already-landed owner boundaries and future owned widening targets, not donor extraction.","Which remaining non-Euclidean topology, transform-aware macro, or host-shell remainder gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-D/T packets?","Inspect current first-party topology and geometry-family boundaries, transform-aware macro remapping and macro XML compatibility boundaries, the deferred broader MagicTile host-shell remainder, and unresolved owned widening targets only.","Audit roice3/MagicTile only as an already-landed permissive owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist for its bounded topology and macro slices. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","do not exclude","This row is already implemented for its current justified slices and should no longer be treated as a donor extraction candidate.","high","single-source signal; clear taxonomy; active integration value; bounded landed owner lane","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 already landed for its current justified tiling topology, geometry-family, transform-aware macro remapping, reverse/setup-move playback-tag, and macro XML compatibility slices. Its row-source posture should now be preserve-and-owned-widen rather than donor extraction.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0007","Implemented non-Euclidean topology and macro owner","Landed non-Euclidean topology owner lane for HyperTwist; validate boundaries and widen only through owned first-party work while the broader host-shell remainder stays deferred.","HyperTwist","Implemented non-Euclidean topology and macro owner","integrate","moderate modification","medium","roice3/magictile","1.0","Locked Strategic Donor","4.0","Already-landed MagicTile owner row for bounded tiling topology, geometry-family, transform-aware macro remapping, and macro compatibility families; no donor thesis remains for the current slice.","Implemented non-Euclidean topology and macro owner lane","Included","P1","Keep in canon as an already-landed first-party MagicTile owner lane and route all future work through owned widening while the broader host-shell remainder stays deferred.","2.0","2.0","2.0","11950.0","136.0","","roice3/magictile","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","36.0","3","4.0","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified topology and transform-aware macro slice is already implemented in first-party HyperTwist code. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party topology and macro owner surfaces plus landed packet authority, and keep the broader host-shell remainder deferred unless a later owned widening is justified.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-bounded-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
 "41.0","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","1.0","Donor Bench","4.0","Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.","Telemetry / replay / feature-governance donor","Included","P2","PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.","2.0","2.0","2.0","11966.0","139.0","Thin-fit assignment; verify project mapping during source audit","posthog/posthog","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT outside ee/; enterprise-restricted in ee/","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","41.0","3","4.0","72.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.","Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-D closed. Preserve as the landed first-party control-plane telemetry, replay-diagnostic, scheduled-change, early-access, and explicit root-MIT-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-D, then REPO_LICENSE_TRACKING.md; keep the explicit ee/ exclusion and mixed-license subtree boundary visible."
 "","met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","","","","","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","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Browser embodied coach surface","Included","P2","met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","","","","","","","met4citizen/talkinghead","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md."
 "","apache/echarts","https://github.com/apache/echarts","HyperTwist","","","","","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","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Browser analytics and reporting surface","Included","P2","apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","","","","","","","apache/echarts","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md."
diff --git a/docs/repo_portfolio_unified_source_audit_v6_3.csv b/docs/repo_portfolio_unified_source_audit_v6_3.csv
index 2ec5af1..c0ef104 100644
--- a/docs/repo_portfolio_unified_source_audit_v6_3.csv
+++ b/docs/repo_portfolio_unified_source_audit_v6_3.csv
@@ -73,7 +73,7 @@
 7) Reasons to promote / retain / demote
 8) Confidence change after source audit
 9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.","Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0003","HT_hyper_engine","cutelyaware/magiccube4d","","","","","","","Original global P0-P3 source audit retained","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.","Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.","Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.","medium","custom-license-attribution-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-B closed. Preserve as the landed attributed legacy 4D interaction, history, macro, topology-reference, and provenance-boundary lane beneath the Hyperspeedcube anchor; start future widening from the live-lane audit, then Phase 4R-B, then REPO_LICENSE_TRACKING.md."
-"roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","Locked Strategic Donor","Specialized 4D interaction and puzzle-UX donor","P1","7464","9219","49.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether roice3/Magic120Cell should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
+"roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","Locked Strategic Donor","Specialized 4D interaction and puzzle-UX donor","P1","7464","9219","49.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Validate the current first-party owner boundaries for roice3/Magic120Cell and record any narrower owned widening targets that remain after the landed Phase 6R-I slice beneath the retained Hyperspeedcube runtime anchor.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect current first-party 120-cell family runtime-profile and persistence boundary, the retained Hyperspeedcube anchor relation, retained broader MagicTile family context, and unresolved owned widening targets only.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture.","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages
 4) Integration path into target project
@@ -81,8 +81,8 @@
 6) Best merge partners and exact coupling seam
 7) Reasons to promote / retain / demote
 8) Confidence change after source audit
-9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0004","HT_hyper_engine","roice3/magic120cell","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
-"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","Specialized 5D cube interaction, progress, and macro donor","P1","7465","9220","50.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether roice3/MagicCube5D should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
+9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Audit roice3/Magic120Cell only as an already-landed permissive family owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","HT_hyper_engine_0004","HT_hyper_engine","roice3/magic120cell","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified 120-cell family runtime slice is already implemented in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party 120-cell family owner surfaces plus landed packet authority beneath the retained Hyperspeedcube anchor.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-specialized-family-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-I preserve sequence closed for the bounded family slice. Preserve as the landed first-party 120-cell family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-I packet."
+"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","Specialized 5D cube interaction, progress, and macro donor","P1","7465","9220","50.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Validate the current first-party owner boundaries for roice3/MagicCube5D and record any narrower owned widening targets that remain after the landed Phase 6R-J slice beneath the retained Hyperspeedcube runtime anchor.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect current first-party 5D family runtime-profile and persistence boundary, the retained Hyperspeedcube anchor relation, retained broader MagicTile family context, and unresolved owned widening targets only.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture.","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages
 4) Integration path into target project
@@ -90,7 +90,7 @@
 6) Best merge partners and exact coupling seam
 7) Reasons to promote / retain / demote
 8) Confidence change after source audit
-9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0005","HT_hyper_engine","roice3/magiccube5d","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
+9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Audit roice3/MagicCube5D only as an already-landed permissive family owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","HT_hyper_engine_0005","HT_hyper_engine","roice3/magiccube5d","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified 5D family runtime slice is already implemented in first-party HyperTwist code beneath the retained Hyperspeedcube runtime anchor. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party 5D family owner surfaces plus landed packet authority beneath the retained Hyperspeedcube runtime anchor.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-specialized-family-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-J preserve sequence closed for the bounded family slice. Preserve as the landed first-party 5D family runtime-profile and persistence lane beneath the retained hyper runtime anchor; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the landed Phase 6R-J packet."
 "aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","Reserve Bench","Reference-only XR benchmark","P3","7467","9222","51.0","119.0","134.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","future candidate","architecture only","Validate that CodeXR remains reference-only and record the specific immersive interaction ideas worth preserving without direct source reuse.","Collaboration-room flow, scene launch, virtual screens, and immersive interaction behavior as benchmark material only.","Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?","Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.","Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.","","","","","","","","","","Historical comparison only","Retain only as discarded historical comparison context; do not plan donor, merge, or clean-room reopening from this row.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in aMonteSl/CodeXR
 2) What must stay benchmark-only or clean-room-only
 3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.","GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.","HT_cube_vision_0005","HT_cube_vision","amontesl/codexr","","","","","","","Original global P0-P3 source audit retained","GPL-3.0-only","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","119.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-reference-only-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows."
@@ -166,7 +166,7 @@
 "Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","Donor Bench","Adjacency / future transfer","P2","7485","9240","2.0","88.0","97.0","medium","This row is already live for its current justified slices. Preserve the landed local timer lifecycle, inspection, split capture and editing, session stats, local persistence, and timer-scoped replay boundaries, and widen only through owned HyperTwist work.","repurpose","moderate modification","Validate the current first-party owner boundaries for Aarav2709/KubeTimr and record any narrower owned widening targets that remain after the landed timer-substrate slice.","Landed timer lifecycle, inspection, split capture, stats, local persistence, and timer-scoped replay boundaries as live first-party material.","Inspect current first-party timer owner boundaries, landed packet scope, retained timer oracle and reference rows, and unresolved owned widening targets only.","Which remaining timer-substrate gaps, if any, are not already covered by the landed HyperTwist code and the KubeTimr implementation packet?","Preserve as the landed first-party timer substrate owner lane. Start any future widening from owned HyperTwist surfaces, the timer implementation packet, FEATURE_REGISTRY, ROADMAP, and REPO_LICENSE_TRACKING; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner. Keep cstimer as the retained restrictive oracle, cubing/qqTimer as legacy reference, and CubeDesk as adjacent live trainer-session and smart-device workflow composition rather than donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed timer substrate owner lane, not external donor harvesting.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture.","1) Which landed timer owner boundaries are already closed
 2) Which narrower owned widening targets, if any, remain
 3) Which adjacent retained oracle or reference rows stay outside the landed slice","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon as an already-landed first-party timer owner lane and route all future work through owned widening.","Already-landed timer owner row for bounded lifecycle, inspection, split, persistence, stats, and timer-scoped replay families; no donor thesis remains for the current slice.","Audit Aarav2709/KubeTimr only as an already-landed permissive owner lane for HyperTwist. Validate current timer owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","HT_training_stack_0015","HT_training_stack","aarav2709/kubetimr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Already landed: start from first-party owner surfaces and landed packet authority, not donor-transfer framing.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","routine-review-only","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md."
-"roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","Locked Strategic Donor","Top-tier non-Euclidean geometry and topology donor","P1","7487","9242","2.0","88.0","97.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.","repurpose","moderate modification","Determine whether roice3/MagicTile should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
+"roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","Locked Strategic Donor","Top-tier non-Euclidean geometry and topology donor","P1","7487","9242","2.0","88.0","97.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.","repurpose","moderate modification","Validate the current first-party owner boundaries for roice3/MagicTile and record any narrower owned widening targets that remain after the landed Phase 6R-D/T slice while keeping the broader host-shell remainder deferred.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect current first-party topology and geometry-family boundaries, transform-aware macro remapping and macro XML compatibility boundaries, the deferred broader MagicTile host-shell remainder, and unresolved owned widening targets only.","Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture.","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages
 4) Integration path into target project
@@ -174,7 +174,7 @@
 6) Best merge partners and exact coupling seam
 7) Reasons to promote / retain / demote
 8) Confidence change after source audit
-9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0007","HT_hyper_engine","roice3/magictile","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
+9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Audit roice3/MagicTile only as an already-landed permissive owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","HT_hyper_engine_0007","HT_hyper_engine","roice3/magictile","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and its current justified topology and transform-aware macro slice is already implemented in first-party HyperTwist code. Further work should be ordinary owned widening from landed packet authority, not donor-transfer framing.","Already landed: start from first-party topology and macro owner surfaces plus landed packet authority, and keep the broader host-shell remainder deferred unless a later owned widening is justified.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","implemented-bounded-owner","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-D/T preserve sequence closed for the bounded retained slice. Preserve as the landed first-party tiling topology, geometry-family, and transform-aware macro remapping lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broader host-shell ownership stays deferred."
 "PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","Donor Bench","Adjacency / future transfer","P2","7492","9247","20.0","72.0","81.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Determine whether PostHog/posthog should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","telemetry and event schemas, replay product boundaries, feature-flag governance, diagnostics, service slices, hidden modules","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
 2) Hidden capabilities found only in source
 3) Best salvageable modules/files/packages