Align Phase 2R-C row source truth

This commit is contained in:
axiomlogicnexus 2026-05-27 23:50:31 +02:00
parent a1c3d64dc9
commit 15f676f0d1
4 changed files with 89 additions and 18 deletions

View file

@ -0,0 +1,71 @@
# HyperTwist Phase 2R-C Row Source Alignment - 2026-05-27
## Status
This document closes the stale row-source truth gap for the already-clarified
`Phase 2R-C` permissive retained rows in HyperTwist.
It answers one narrow question:
- after the `2026-05-27` recognition-comparison adjunct hierarchy note and the
symbolic-XR plus browser-comparison hierarchy note landed, do the `v6.3`
row-source layers still speak about these repos like open implementation
candidates instead of already-bounded adjunct or comparison rows
Result:
- yes, the operational, `Phase G`, and source-audit layers were still carrying
stale candidate or donor-era wording for the affected `2R-C` rows
- the state board and later hierarchy notes were already correct
- the needed fix is row-source alignment only
- no product code, live ownership, or roadmap routing changed from this pass
## Affected rows
- `cahidenes/rubiks-cube-solver`
- `tentone/rubix-solver`
- `NuiLab/code-vr`
- `pissang/claygl`
- `pissang/clay-viewer`
## Required row-source posture
For these rows the source pack must now say:
- `cahidenes/rubiks-cube-solver` is retained only as a narrow recognition
comparison adjunct beneath landed recognition and correction owners
- `tentone/rubix-solver` is retained only as a narrow recognition comparison
adjunct beneath landed recognition and correction owners
- `NuiLab/code-vr` is retained only as a symbolic-to-spatial pedagogy
experiment lane beneath first-party knowledge and landed browser/XR owners
- `pissang/claygl` is retained only as an optional browser `3D` comparison lane
subordinate to the landed browser stack
- `pissang/clay-viewer` is retained only as an optional browser viewer/editor
comparison lane subordinate to the landed browser stack
- no default widening packet is open for any of these rows
## Source basis
- `C:\HyperTwist\docs\HYPERTWIST_RECOGNITION_COMPARISON_ADJUNCT_HIERARCHY_RECONCILIATION_2026-05-27.md`
- `C:\HyperTwist\docs\HYPERTWIST_SYMBOLIC_XR_AND_ALTERNATIVE_BROWSER_COMPARISON_HIERARCHY_RECONCILIATION_2026-05-27.md`
- `C:\HyperTwist\docs\HYPERTWIST_REPO_STATE_BOARD_2026-05-11.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 row:
- replace open implementation-candidate wording with bounded adjunct or
comparison wording
- replace generic donor or merge framing with explicit closed retained-lane
framing
- keep current live-state and reset-lane values unchanged
## Final call
These rows remain intentionally non-live.
They are retained only as closed adjunct, pedagogy-experiment, or comparison
rows, and the full `v6.3` row-source pack must now describe them that way.

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View file

@ -28,7 +28,7 @@
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_semantics_0001","HT_cube_semantics","cubing/cubing.js","","","","","","","Original global P0-P3 source audit retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","2","1","152.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-A closed. Preserve as the landed first-party classic-cubing semantic/runtime adapter lane through explicit MPL-aware dependency or adapter use; keep notices and publication duties explicit before any future direct upstream file modification."
"cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","25","9208","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/alg.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.","Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.","Inspect cubing/alg.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0002","HT_cube_semantics","cubing/alg.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","implemented_live_clean_room_verified","landed_clean_room_preserve","Later clean-room sequence closed through Bound 4. Preserve as the landed first-party algorithm-language 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."
"cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","27","9210","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/twisty.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.","Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.","Inspect cubing/twisty.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0003","HT_cube_semantics","cubing/twisty.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","implemented_live_clean_room_verified","landed_clean_room_preserve","Later clean-room sequence closed through Bound 4. Preserve as the landed first-party replay-player, cursor/timeline transport, adapter/bootstrap, and local visualization 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."
"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","Retained face-placement and cube-string comparison adjunct","P1","55","9211","4.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the retained comparison-adjunct thesis for cahidenes/rubiks-cube-solver in HyperTwist: what exact narrow logic survives, how it compares against the landed first-party recognition stack, and whether any later owner-gap reopening is actually justified.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect face-orientation fill logic, cube-string assembly, per-sticker bookkeeping, HSV sampling, opposite-corner capture assumptions, and divergence-reporting possibilities against the landed first-party stack.","Inspect opposite-corner capture assumptions; face-placement fill; cube-string assembly; per-sticker bookkeeping; HSV sampling; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface face-placement, cube-string assembly, or divergence-reporting comparisons without widening camera shell, primary calibration, or solver ownership.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded cross-checking or disagreement reporting; do not form a separate recognition silo or reopen primary recognition ownership.","Repurpose here means: optional face-placement, cube-string, or disagreement comparator logic only, not a primary recognition service or AR shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","Retained face-placement and cube-string comparison adjunct","P1","55","9211","4.0","148.0","174.0","high","This row is already closed for its current justified retained slice. Preserve the retained face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners, and reopen only if a narrower gap is later proven.","integrate","direct","Confirm that cahidenes/rubiks-cube-solver remains a closed retained face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners, and record only narrower reopen criteria, if any.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect the retained face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct slice only in relation to the landed qbr, rubix-cube-solver, and first-party correction-stack owners, existing first-party surfaces, and any unresolved narrower reopen gaps.","whether any narrower face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct gap remains after the landed qbr, rubix-cube-solver, and first-party correction-stack owners and the existing first-party surfaces.","Retain only as the closed face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners. No default widening packet is open; any future work must start from the landed owners and narrower gap proof.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded cross-checking or disagreement reporting; do not form a separate recognition silo or reopen primary recognition ownership.","Integrate here means: only a narrower first-party widening if a concrete owner-side gap is later proven.","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.","No cross-project transfer by default","This row is already closed as a retained bounded row. Reuse should start only from narrower owner-side gap proof, not generic transfer framing.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Closed retained-boundary note + explicit no-default-widening posture + narrower reopen criteria.","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
4) Integration path into target project
@ -36,8 +36,8 @@
6) Best merge partners and exact coupling seam
7) Reasons to promote / retain / demote
8) Confidence change after source audit
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver only as a retained recognition-comparison adjunct for HyperTwist. Inspect opposite-corner capture assumptions, face-orientation fill logic, cube-string assembly from partial capture, and lightweight HSV or per-sticker bookkeeping. Do not reopen it as a primary recognition, calibration, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","HT_cube_vision_0003","HT_cube_vision","cahidenes/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","Retained native quad and color comparison adjunct","P1","56","9212","5.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the retained native comparison-adjunct thesis for tentone/rubix-solver in HyperTwist: what exact narrow logic survives, how it compares against the landed first-party recognition stack, and whether any later owner-gap reopening is actually justified.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect quad detection and sorting, square-mask color sampling, center-color face labeling, native face-array mutation behavior, and brute-force solve-shell exclusion.","Inspect quad clustering; sort stability; square-mask and threshold logic; center-color face labeling; native state-mutation semantics; disagreement-reporting value; reasons it should stay subordinate to qbr and rubix-cube-solver.","Do not integrate as a primary perception subsystem. Retain only as a narrow native comparison adjunct behind the landed qbr calibration/webcam owner and landed rubix-cube-solver reconstruction/browser owner. Any later use should surface quad, mask, or divergence comparisons without widening the local camera shell or brute-force solve shell.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded native comparison, side-by-side validation, or disagreement reporting; do not form a separate recognition silo or promote the local solve shell.","Repurpose here means: optional quad-sorting, square-mask, and native face-state comparator logic only, not a primary recognition service or solver shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a closed retained face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners; reopen only through narrower gap proof, not generic implementation routing.","Closed retained face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct row beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners; no default widening packet is open for the current slice.","Audit cahidenes/rubiks-cube-solver only as a closed retained face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct row for HyperTwist. Validate that it remains bounded beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners and identify narrower reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_cube_vision_0003","HT_cube_vision","cahidenes/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow face-placement, cube-string assembly, and optional two-opposite-corner comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","Retained native quad and color comparison adjunct","P1","56","9212","5.0","148.0","174.0","high","This row is already closed for its current justified retained slice. Preserve the retained native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners, and reopen only if a narrower gap is later proven.","integrate","direct","Confirm that tentone/rubix-solver remains a closed retained native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners, and record only narrower reopen criteria, if any.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect the retained native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct slice only in relation to the landed qbr, rubix-cube-solver, and first-party correction-stack owners, existing first-party surfaces, and any unresolved narrower reopen gaps.","whether any narrower native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct gap remains after the landed qbr, rubix-cube-solver, and first-party correction-stack owners and the existing first-party surfaces.","Retain only as the closed native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners. No default widening packet is open; any future work must start from the landed owners and narrower gap proof.","Keep subordinate to qbr and rubix-cube-solver inside the current recognition stack. Use only for bounded native comparison, side-by-side validation, or disagreement reporting; do not form a separate recognition silo or promote the local solve shell.","Integrate here means: only a narrower first-party widening if a concrete owner-side gap is later proven.","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.","No cross-project transfer by default","This row is already closed as a retained bounded row. Reuse should start only from narrower owner-side gap proof, not generic transfer framing.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Closed retained-boundary note + explicit no-default-widening posture + narrower reopen criteria.","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
4) Integration path into target project
@ -45,7 +45,7 @@
6) Best merge partners and exact coupling seam
7) Reasons to promote / retain / demote
8) Confidence change after source audit
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Audit tentone/rubix-solver only as a retained native recognition-comparison adjunct for HyperTwist. Inspect quad clustering, square-mask color sampling, center-color face identification, native face-array mutation behavior, and brute-force solve-shell exclusion. Do not reopen it as a primary recognition, correction, or solver owner. Compare only against the landed qbr, rubix-cube-solver, and correction-stack seams and report whether any narrower divergence-reporting gap remains.","HT_cube_vision_0004","HT_cube_vision","tentone/rubix-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","Practical working assumption remains MIT from README and repo presentation, but the checked mirror lacks a bundled top-level license file. Keep this row permissive-active only as a subordinate recognition comparison adjunct, and capture the final authoritative upstream license text before any direct vendoring.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","medium","readme-only-license-capture-before-direct-vendoring","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a closed retained native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners; reopen only through narrower gap proof, not generic implementation routing.","Closed retained native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct row beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners; no default widening packet is open for the current slice.","Audit tentone/rubix-solver only as a closed retained native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct row for HyperTwist. Validate that it remains bounded beneath the landed qbr, rubix-cube-solver, and first-party correction-stack owners and identify narrower reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_cube_vision_0004","HT_cube_vision","tentone/rubix-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","Practical working assumption remains MIT from README and repo presentation, but the checked mirror lacks a bundled top-level license file. Keep this row permissive-active only as a subordinate recognition comparison adjunct, and capture the final authoritative upstream license text before any direct vendoring.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","medium","readme-only-license-capture-before-direct-vendoring","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase2rc_recognition_adjunct_gap_eval_only","Phase 2R-C plus the 2026-05-27 recognition-comparison adjunct hierarchy clarification are closed. Retain only as a narrow native quad-sorting, square-mask color sampling, center-color face labeling, and face-state comparison adjunct beneath the landed qbr, rubix-cube-solver, and correction-stack owners; no default widening packet is open."
"Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","Locked Strategic Donor","Training / timing layer","P1","57","9213","14.0","145.0","171.0","high","This row is already live for its current justified slices. Preserve the landed persisted coaching, weighted sampling, method exploration, and BLD-domain training-session boundaries, and widen only through owned HyperTwist work.","integrate","direct","Validate the current first-party owner boundaries for Lykos/cube_trainer and record any narrower owned widening targets that remain after the landed persisted-coaching slice.","Landed persisted coaching, weighted sampling, method exploration, and BLD-domain training-session boundaries as live first-party material.","Inspect current first-party persisted-coaching owner boundaries, retained adjacent training-foundation and timer families, and unresolved owned widening targets only.","Which remaining persisted-coaching or weighted-sampling gaps, if any, are not already covered by the landed HyperTwist code and the current cube_trainer preserve slice?","Preserve as the landed first-party persisted-coaching owner lane. Start any future widening from owned HyperTwist surfaces, the live training stack, 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 Alg-Trainer as the broader training-foundation owner, KubeTimr as the timer substrate owner, and CubeDesk as adjacent 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 persisted-coaching 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.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture.","1) Which landed persisted-coaching owner boundaries are already closed
2) Which narrower owned widening targets, if any, remain
3) Which adjacent live or retained 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; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon as an already-landed first-party persisted-coaching owner lane and route all future work through owned widening.","Already-landed persisted-coaching owner row for weighted sampling, method exploration, and BLD-domain session families; no donor thesis remains for the current slice.","Audit Lykos/cube_trainer only as an already-landed permissive owner lane for HyperTwist. Validate current persisted-coaching owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","HT_training_stack_0002","HT_training_stack","lykos/cube_trainer","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","145.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Already landed: start from first-party owner surfaces and landed preserve 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","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work."
@ -100,7 +100,7 @@
"MathewKJ2048/Rubiks-cube-simulator","https://github.com/MathewKJ2048/Rubiks-cube-simulator","HyperTwist","Reserve Bench","Clean-room simulator benchmark","P3","7469","9224","51.0","118.0","133.0","medium","Retain no implementation path from this row. Preserve only historical comparison notes about lightweight simulator shell behavior because stronger pedagogy, planner, and history benchmarks already cover the surviving value.","future candidate","architecture only","Confirm that MathewKJ2048/Rubiks-cube-simulator has no surviving unique retained slice after comparison against the stronger guided pedagogy, planner, and history benchmark rows.","Discard confirmation against stronger pedagogy, planner, and history benchmark rows.","Inspect only enough to confirm duplicate-retirement posture against stronger pedagogy, planner, and history benchmark rows.","Is any lightweight simulator behavior still unique after comparison against the stronger guided pedagogy, planner, and history benchmark rows?","Discard from active retention. Keep only as historical comparison context for lightweight simulator behavior; do not plan clean-room reuse or source incorporation.","Prefer AviKaufman, alinen, and vwcwong for the surviving guided pedagogy, planner, and readable state-history benchmark value. This row no longer carries a unique retained slice.","Historical comparison only; no retained implementation or clean-room route remains.","","","","","","","","","","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.","Discard-confirmation note + stronger surviving benchmark rows + clear no-reopen boundary.","1) What product behaviors existed in the discarded simulator shell
2) Why stronger pedagogy, planner, and history rows supersede it
3) Why no clean-room or donor reopening should proceed from this row","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 discarded historical comparison context; no clean-room or donor route survives.","Inferior lightweight simulator duplicate with no surviving unique retained slice after comparison against stronger pedagogy, planner, and history benchmarks.","Audit MathewKJ2048/Rubiks-cube-simulator only as a discard-confirmation row for HyperTwist. Confirm that no unique retained pedagogy, planner, or history slice survives after comparison against stronger benchmark rows.","HT_training_clean_room_0004","HT_training_clean_room","mathewkj2048/rubiks-cube-simulator","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.","Reference only: discarded historical comparison context for lightweight simulator shell behavior; do not plan direct incorporation or clean-room reopening.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks."
"NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","Donor Bench","Retained symbolic-to-spatial XR pedagogy experiment","P2","7470","9225","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Confirm the retained symbolic-to-spatial pedagogy thesis for NuiLab/code-vr in HyperTwist: what exact narrow logic survives, how it compares against the landed knowledge and browser-spatial/XR stack, and whether any later owner-gap reopening is actually justified.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect symbolic-to-spatial conversion, parse/export/runtime separation, language-aware teaching-sidecar behavior, and bounded pedagogy-experiment seams against the landed knowledge and browser-spatial/XR stack.","Inspect AST or graph-to-scene conversion; parse/export/runtime separation; language-server sidecar boundaries; symbolic-to-spatial pedagogy value; reasons it should stay subordinate to the knowledge shell and browser-spatial/XR owners.","Do not integrate as a practical XR runtime or training subsystem. Retain only as a narrow symbolic-to-spatial pedagogy experiment behind the first-party knowledge shell and landed browser-spatial/XR owners. Any later use should surface abstract-structure spatial teaching or parse/export/runtime experiments without widening the VR runtime shell.","Keep subordinate to the first-party knowledge shell and landed browser-spatial/XR owners. Use only for bounded pedagogy experiments; do not form a separate XR or game-runtime silo.","Repurpose here means: optional code-structure-to-space pedagogy, parse/export/runtime experiment logic, or teaching-sidecar patterns only, not a practical XR runtime or trainer foundation.","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
"NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","Donor Bench","Retained symbolic-to-spatial XR pedagogy experiment","P2","7470","9225","51.0","118.0","133.0","medium","This row is already closed for its current justified retained slice. Preserve the retained symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and the landed browser-spatial/XR owners, and reopen only if a narrower gap is later proven.","repurpose","moderate modification","Confirm that NuiLab/code-vr remains a closed retained symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and the landed browser-spatial/XR owners, and record only narrower reopen criteria, if any.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect the retained symbolic-to-spatial pedagogy experiment lane slice only in relation to the first-party knowledge shell and the landed browser-spatial/XR owners, existing first-party surfaces, and any unresolved narrower reopen gaps.","whether any narrower symbolic-to-spatial pedagogy experiment lane gap remains after the first-party knowledge shell and the landed browser-spatial/XR owners and the existing first-party surfaces.","Retain only as the closed symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and the landed browser-spatial/XR owners. No default widening packet is open; any future work must start from the landed owners and narrower gap proof.","Keep subordinate to the first-party knowledge shell and landed browser-spatial/XR owners. Use only for bounded pedagogy experiments; do not form a separate XR or game-runtime silo.","Integrate here means: only a narrower first-party widening if a concrete owner-side gap is later proven.","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.","No cross-project transfer by default","This row is already closed as a retained bounded row. Reuse should start only from narrower owner-side gap proof, not generic transfer 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.","Closed retained-boundary note + explicit no-default-widening posture + narrower reopen criteria.","1) Confirmed visible capabilities
2) Hidden capabilities found only in source
3) Best salvageable modules/files/packages
4) Integration path into target project
@ -108,7 +108,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 below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.","MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.","Audit NuiLab/code-vr only as a retained symbolic-to-spatial pedagogy experiment for HyperTwist. Inspect AST or graph-to-scene conversion, parse/export/runtime separation, and language-aware teaching-sidecar behavior. Do not reopen it as a practical XR runtime, gameplay shell, or training foundation owner. Compare only against the first-party knowledge shell and landed browser-spatial/XR stack and report whether any narrower pedagogy gap remains.","HT_cube_vision_0007","HT_cube_vision","nuilab/code-vr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase2rc_symbolic_xr_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as a symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and landed browser-spatial/XR owners; no default widening packet is open."
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 in canon only as a closed retained symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and the landed browser-spatial/XR owners; reopen only through narrower gap proof, not generic implementation routing.","Closed retained symbolic-to-spatial pedagogy experiment lane row beneath the first-party knowledge shell and the landed browser-spatial/XR owners; no default widening packet is open for the current slice.","Audit NuiLab/code-vr only as a closed retained symbolic-to-spatial pedagogy experiment lane row for HyperTwist. Validate that it remains bounded beneath the first-party knowledge shell and the landed browser-spatial/XR owners and identify narrower reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_cube_vision_0007","HT_cube_vision","nuilab/code-vr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase2rc_symbolic_xr_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as a symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and landed browser-spatial/XR owners; no default widening packet is open."
"ShellPuppy/RCube","https://github.com/ShellPuppy/RCube","HyperTwist","Reserve Bench","Large-N solver benchmark","P3","7471","9226","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Document the large-N orientation and stage-framing ideas that justify retaining RCube only as a benchmark row.","Large-cube orientation logic, stage framing, and solver behavior as benchmark material.","Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.","Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.","Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.","","","","","","","","","","Reference only","Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in ShellPuppy/RCube
2) What must stay benchmark-only or clean-room-only
3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.","GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.","HT_solver_oracles_0001","HT_solver_oracles","shellpuppy/rcube","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.","high","gpl-large-n-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor."
@ -236,8 +236,8 @@
"screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","Donor Bench","Support-plane capture, history, and replay sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0001","HT_support_sidecars","screenpipe/screenpipe","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-E closed. Preserve as the landed first-party capture/history/replay, deterministic-permission, persistence, vault-lifecycle, timeline-review, and explicit permissive-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-E, then REPO_LICENSE_TRACKING.md."
"remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","Donor Bench","Commercially licensed media-export and explainer sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.","player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0002","HT_support_sidecars","remotion-dev/remotion","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-F closed. Preserve as the landed first-party media-export, embedded playback, parser, explainer-studio, and package-split commercial-compliance lane; start future widening from the live-lane audit, then Phase 4R-F, then REPO_LICENSE_TRACKING.md; keep the explicit company-license and package-split boundary visible."
"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","Browser 2D render substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that ecomfe/zrender remains a closed subordinate lower-level 2D painter and event substrate beneath the landed apache/echarts anchor, and record only narrower sidecar-gap reopen criteria, if any.","scene graph, canvas and SVG painters, event handling, animation primitives","Inspect the retained lower-level 2D painter and event substrate slice only in relation to the landed apache/echarts anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender only as a closed subordinate lower-level 2D painter and event substrate row for HyperTwist. Validate that it remains bounded beneath the landed apache/echarts anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0001","HT_browser_support","ecomfe/zrender","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_analytics_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate 2D render substrate beneath the landed apache/echarts lane; no default widening packet is open."
"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Retained alternative browser 3D comparison substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm the retained browser 3D comparison thesis for pissang/claygl in HyperTwist: what exact narrow infrastructure value survives, how it compares against the landed browser spatial stack, and whether any later sidecar-gap reopening is actually justified.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect renderer and scene infrastructure, camera and control patterns, picking and compositor behavior, and bounded browser-side comparison value against the landed browser spatial stack.","Inspect renderer, scene, camera, control, picking, compositor, and App3D patterns; sidecar-only value; reasons it should stay subordinate to the landed browser spatial stack.","Do not integrate as a primary browser spatial runtime. Retain only as an optional comparison substrate beneath the landed three.js, react-three-fiber, and xr stack. Any later use should surface bounded lower-level browser-side 3D control or explainer sidecars only if a real gap remains.","Keep subordinate to the landed browser spatial stack and do not form a separate WebGL runtime silo. Use only for optional comparison or bounded sidecar support.","Repurpose here means: optional lower-level browser 3D comparison or explainer substrate only, not a runtime foundation.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl only as a retained alternative browser 3D comparison substrate for HyperTwist. Inspect renderer, scene, camera, control, picking, compositor, and App3D patterns. Do not reopen it as a primary browser spatial runtime or puzzle-renderer owner. Compare only against the landed three.js, react-three-fiber, and xr stack and report whether any narrower sidecar gap remains.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser 3D comparison lane subordinate to the landed three.js, react-three-fiber, and xr stack; keep 3R-G deferred unless a real sidecar gap remains."
"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Retained alternative browser viewer/editor comparison sidecar","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm the retained browser viewer/editor comparison thesis for pissang/clay-viewer in HyperTwist: what exact narrow sidecar value survives, how it compares against the landed browser viewer and spatial stack, and whether any later sidecar-gap reopening is actually justified.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect viewer shell, hotspot and animation-preview behavior, environment or lighting presets, compact inspection surfaces, and bounded browser comparison value against google/model-viewer and the landed browser spatial stack.","Inspect hotspot, camera, animation-preview, environment or post-effect preset, and inspection-shell patterns; sidecar-only value; reasons it should stay subordinate to google/model-viewer and the landed browser spatial stack.","Do not integrate as a primary browser viewer or editor runtime. Retain only as an optional comparison sidecar behind the landed google/model-viewer and browser spatial owners. Any later use should surface bounded preview, inspection, or explainer behaviors only if a real gap remains.","Keep subordinate to google/model-viewer and the landed browser spatial stack. Use only for optional comparison or bounded preview or editor sidecars.","Repurpose here means: optional viewer/editor comparison, preview, or inspection sidecar only, not a runtime foundation.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer only as a retained alternative browser viewer/editor comparison sidecar for HyperTwist. Inspect hotspot, animation-preview, environment or post-effect preset, and compact inspection-shell behavior. Do not reopen it as a primary browser viewer, editor, gameplay, or runtime owner. Compare only against the landed google/model-viewer and browser spatial stack and report whether any narrower sidecar gap remains.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser viewer/editor comparison lane subordinate to the landed google/model-viewer and browser spatial stack; keep 3R-G deferred unless a real sidecar gap remains."
"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Retained alternative browser 3D comparison substrate","P3","","","","","","medium","This row is already closed for its current justified retained slice. Preserve the retained optional browser 3D comparison lane beneath the landed mrdoob/three.js and browser-spatial owner stack, and reopen only if a narrower gap is later proven.","integrate","moderate modification","Confirm that pissang/claygl remains a closed retained optional browser 3D comparison lane beneath the landed mrdoob/three.js and browser-spatial owner stack, and record only narrower reopen criteria, if any.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect the retained optional browser 3D comparison lane slice only in relation to the landed mrdoob/three.js and browser-spatial owner stack, existing first-party surfaces, and any unresolved narrower reopen gaps.","whether any narrower optional browser 3D comparison lane gap remains after the landed mrdoob/three.js and browser-spatial owner stack and the existing first-party surfaces.","Retain only as the closed optional browser 3D comparison lane beneath the landed mrdoob/three.js and browser-spatial owner stack. No default widening packet is open; any future work must start from the landed owners and narrower gap proof.","Keep subordinate to the landed browser spatial stack and do not form a separate WebGL runtime silo. Use only for optional comparison or bounded sidecar support.","Integrate here means: only a narrower first-party widening if a concrete owner-side gap is later proven.","","","","","","","","","","No cross-project transfer by default","This row is already closed as a retained bounded row. Reuse should start only from narrower owner-side gap proof, not generic transfer framing.","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed retained-boundary note + explicit no-default-widening posture + narrower reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","Keep in canon only as a closed retained optional browser 3D comparison lane beneath the landed mrdoob/three.js and browser-spatial owner stack; reopen only through narrower gap proof, not generic implementation routing.","Closed retained optional browser 3D comparison lane row beneath the landed mrdoob/three.js and browser-spatial owner stack; no default widening packet is open for the current slice.","Audit pissang/claygl only as a closed retained optional browser 3D comparison lane row for HyperTwist. Validate that it remains bounded beneath the landed mrdoob/three.js and browser-spatial owner stack and identify narrower reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser 3D comparison lane subordinate to the landed three.js, react-three-fiber, and xr stack; keep 3R-G deferred unless a real sidecar gap remains."
"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Retained alternative browser viewer/editor comparison sidecar","P3","","","","","","medium","This row is already closed for its current justified retained slice. Preserve the retained optional browser viewer/editor comparison lane beneath the landed google/model-viewer and browser-viewer owner stack, and reopen only if a narrower gap is later proven.","integrate","moderate modification","Confirm that pissang/clay-viewer remains a closed retained optional browser viewer/editor comparison lane beneath the landed google/model-viewer and browser-viewer owner stack, and record only narrower reopen criteria, if any.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect the retained optional browser viewer/editor comparison lane slice only in relation to the landed google/model-viewer and browser-viewer owner stack, existing first-party surfaces, and any unresolved narrower reopen gaps.","whether any narrower optional browser viewer/editor comparison lane gap remains after the landed google/model-viewer and browser-viewer owner stack and the existing first-party surfaces.","Retain only as the closed optional browser viewer/editor comparison lane beneath the landed google/model-viewer and browser-viewer owner stack. No default widening packet is open; any future work must start from the landed owners and narrower gap proof.","Keep subordinate to google/model-viewer and the landed browser spatial stack. Use only for optional comparison or bounded preview or editor sidecars.","Integrate here means: only a narrower first-party widening if a concrete owner-side gap is later proven.","","","","","","","","","","No cross-project transfer by default","This row is already closed as a retained bounded row. Reuse should start only from narrower owner-side gap proof, not generic transfer framing.","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed retained-boundary note + explicit no-default-widening posture + narrower reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","Keep in canon only as a closed retained optional browser viewer/editor comparison lane beneath the landed google/model-viewer and browser-viewer owner stack; reopen only through narrower gap proof, not generic implementation routing.","Closed retained optional browser viewer/editor comparison lane row beneath the landed google/model-viewer and browser-viewer owner stack; no default widening packet is open for the current slice.","Audit pissang/clay-viewer only as a closed retained optional browser viewer/editor comparison lane row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer and browser-viewer owner stack and identify narrower reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser viewer/editor comparison lane subordinate to the landed google/model-viewer and browser spatial stack; keep 3R-G deferred unless a real sidecar gap remains."
"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","Browser asset renderer substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that KhronosGroup/glTF-Sample-Renderer remains a closed subordinate renderer and reference substrate beneath the landed google/model-viewer asset-QA lane, and record only narrower sidecar-gap reopen criteria, if any.","GltfView, GltfState, resource loader, user camera, renderer core","Inspect the retained renderer and reference substrate slice only in relation to the landed google/model-viewer asset-QA lane, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer only as a closed subordinate renderer and reference substrate row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer asset-QA lane and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0004","HT_browser_support","khronosgroup/gltf-sample-renderer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; no default widening packet is open."
"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","Browser asset editor and inspection surface","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that google/model-viewer/packages/space-opera remains a closed subordinate browser editor and inspection sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect the retained browser editor and inspection sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera only as a closed subordinate browser editor and inspection sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0005","HT_browser_support","google/model-viewer/packages/space-opera","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","Browser fidelity QA harness","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that google/model-viewer/packages/render-fidelity-tools remains a closed subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect the retained fidelity-oracle and regression sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools only as a closed subordinate fidelity-oracle and regression sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0006","HT_browser_support","google/model-viewer/packages/render-fidelity-tools","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; no default widening packet is open."

1 repo primary_url project phase_g_bucket stack_layer audit_tier tier_queue_order global_order wave_number portfolio_priority_score execution_priority_score_v3 current_confidence modification_scope_detail_v3 recommended_action_v2 repurposing_potential_v2 audit_goal inspect_emphasis source_code_audit_targets source_inspection_questions integration_realization_detail consolidation_detail repurpose_detail merger_partner_1 merger_type_1 merger_rationale_1 merger_partner_2 merger_type_2 merger_rationale_2 merger_partner_3 merger_type_3 merger_rationale_3 cross_project_transfer_targets cross_project_transfer_rationale reclassify_up_if reclassify_down_if deliverable_expected session_note_template recommended_context_packet phase_g_master_list_rationale phase_g_bucket_reason coding_model_instruction_v3 source_audit_packet_id cluster_tag _repo_norm v5_runtime_project v5_scriptorium_override_status v5_scriptorium_bucket v5_scriptorium_stack_layer v5_scriptorium_current_reality_status v5_scriptorium_supersedes_prior_assessment v5_source_of_truth v6_license_annotation v6_license_annotation_status v6_license_annotation_source v6_supplemental_intake_present v6_supplemental_source_groups v6_supplemental_source_sections v6_supplemental_source_files v6_reference_material_position v6_kali_agent_access_relevance v6_branch_seed_prompt_included v6_branch_seed_scope v6_intake_wave v6_notes v6_source_of_truth project_rank_num tier_rank_num priority_num copyleft_relevance_v6_1 copyleft_strategy_v6_1 copyleft_rationale_v6_1 preferred_boundary_model_v6_1 open_compliance_if_used_as_is_v6_1 reverse_engineer_if_proprietary_core_needed_v6_1 copyleft_strategy_confidence_v6_1 copyleft_manual_review_trigger_v6_1 as_is_incorporation_sensible_v6_1 v6_2_sre_layer v6_2_sre_stratum v6_2_sre_role v6_2_sre_family v6_2_related_kali_package v6_2_related_upstream_repo v6_2_kali_package_suffices_for_tool_execution v6_2_upstream_repo_preferred_for_deep_eval v6_2_index_page_followup_useful v6_2_index_page_followup_reason v6_2_sre_notes v6_2_dnspy_ilspy_relevance v6_3_source_of_truth v6_3_merge_note v6_3_live_state_2026_05_11 v6_3_reset_lane_2026_05_11 v6_3_reset_next_step_2026_05_11
28 alinen/cube https://github.com/alinen/cube HyperTwist Reserve Bench Clean-room planner benchmark P3 7478 9233 52.0 117.0 132.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the planner and guided-lesson behaviors worth preserving from alinen/cube through a scrubbed clean-room spec. Planner flow, guided lessons, cube-state handling, and bounded-search behavior as clean-room benchmark material. Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only. Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only. Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process. Clean-room only Retain only as benchmark, oracle, acceptance-test, or scrubbed clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in alinen/cube 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a clean-room planner benchmark for first-party guided-lesson and planner work. No explicit license visible and limited scope; retain only for clean-room planner behavior extraction. Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0001 HT_training_clean_room alinen/cube Original global P0-P3 source audit retained no explicit license visible pending_repo_license_audit not_resolved_from_uploaded_materials no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 117.0 license_unknown_pending reverse_engineer_preferred No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications. Model A may inspect and summarize planner behavior; Model B should implement only from a scrubbed clean-room specification. Do not incorporate source directly without a confirmed license grant. Yes — this is the preferred path if planner or lesson behavior later proves strategically necessary. medium no-license-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room planner benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly.
29 ambisinister/blindsolve https://github.com/ambisinister/blindsolve HyperTwist Reserve Bench Clean-room BLD memo benchmark P3 7479 9234 52.0 117.0 132.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the memo-practice and feedback behaviors worth preserving from blindsolve through a scrubbed clean-room spec. Memo-practice flow, feedback behavior, and narrow training-state transitions as clean-room benchmark material. Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only. Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff? Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source. Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only. Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process. Clean-room only Retain only as benchmark, oracle, acceptance-test, or scrubbed clean-room planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in ambisinister/blindsolve 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon only as a clean-room BLD memo benchmark for later first-party micro-mode work. No explicit license visible and extremely narrow scope; retain only as clean-room benchmark material. Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation. HT_training_clean_room_0002 HT_training_clean_room ambisinister/blindsolve Original global P0-P3 source audit retained no explicit license visible pending_repo_license_audit not_resolved_from_uploaded_materials no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 117.0 license_unknown_pending reverse_engineer_preferred No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications. Model A may inspect and summarize memo-practice behavior; Model B should implement only from a scrubbed clean-room specification. Do not incorporate source directly without a confirmed license grant. Yes — this is the preferred path if a memo-practice micro-mode later proves strategically necessary. medium no-license-clean-room-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room BLD memo benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only.
30 efrantar/rob-twophase https://github.com/efrantar/rob-twophase HyperTwist Reserve Bench Solver oracle and robot-metric benchmark P2 7480 9235 52.0 117.0 132.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. future candidate architecture only Capture the correctness, metric, and oracle behaviors that justify keeping rob-twophase only as a benchmark row. Robot metrics, pruning tables, CLI oracle behavior, and multiple-solution search as benchmark material. Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only. Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation? Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code. Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests. Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark. Reference only Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Benchmark note + salvage list + clear do-not-incorporate boundary. 1) What specific benchmark value remains in efrantar/rob-twophase 2) What must stay benchmark-only or clean-room-only 3) Acceptance-test, oracle, or behavior targets worth preserving Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon as a restrictive solver oracle benchmark with robot-metric value. GPL solver/oracle repo whose retained value is correctness, performance, and metric benchmarking rather than donor use. Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code. HT_solver_oracles_0002 HT_solver_oracles efrantar/rob-twophase Original global P0-P3 source audit retained GPL-3.0 known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 117.0 mixed_or_boundary_sensitive_known pattern_only_preferred The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code. Reference only: use as a solver oracle and robot-metric benchmark without direct source incorporation. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Only if a narrow oracle behavior later needs first-party recreation; otherwise keep this as a benchmark. high gpl-solver-oracle-benchmark no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed solver oracle benchmark status. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code.
31 onionhoney/roux-trainers https://github.com/onionhoney/roux-trainers HyperTwist Donor Bench Focused restrictive clean-room donor target P2 7481 9236 52.0 117.0 132.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI. repurpose architecture only Capture the stage-specific training, analyzer, recognition, and drill-loop behaviors that justify keeping roux-trainers as a clean-room donor target. Stage-specific training flows, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries. Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries. Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff? Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code. Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary. Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process. tao-yu/Alg-Trainer base + donor swarm Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. poliva/cubedex specialized training UX donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. Lykos/cube_trainer sampling/analytics donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. HyperTwist only Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Model A salvage map + clean-room boundary note + first-party subsystem extraction plan. 1) Which stage-specific subsystems are worth preserving 2) What must stay behind Model A / Model B separation 3) What first-party implementations should replace the GPL source Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon as a focused restrictive clean-room donor for method-specific training and analyzer behavior. GPLv3 method-specific trainer with real subsystem value that should be preserved through clean-room extraction rather than donor use. Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only. HT_training_clean_room_0006 HT_training_clean_room onionhoney/roux-trainers Original global P0-P3 source audit retained GPL-3.0 known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 117.0 mixed_or_boundary_sensitive_known reverse_engineer_preferred The repo is GPLv3 and should not be used as direct donor code in the HyperTwist core. Its value is in selective behavior and subsystem extraction through a clean-room Model A / Model B process. Model A inspects the restrictive source; Model B implements only from a scrubbed first-party specification and must not access the repo directly. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Yes — preferred path for selectively reproducing stage-specific training and analyzer behavior in first-party code. high gpl-clean-room-donor no v6.3_final_source_of_truth Corrected on 2026-04-25 from stale donor posture to dossier-backed focused restrictive clean-room donor status. implemented_live_clean_room_verified landed_clean_room_preserve Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs.
32 yakupbilen/drl-rubiks-cube https://github.com/yakupbilen/drl-rubiks-cube HyperTwist Reserve Bench Adjacency / future transfer P2 7482 9237 53.0 117.0 132.0 medium Retain the valuable internal 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. future candidate architecture only Capture the learned-heuristic search, anti-cancellation move-sequence, ADI state-generation, and offline experiment behaviors that justify keeping yakupbilen only as a research benchmark row. 54-sticker encoding, ADI state generation, anti-cancellation sequence logic, batched neural A* experimentation, and offline training-loop behavior as research benchmark material. 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. 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. 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. Reference only Retain only as benchmark, oracle, acceptance-test, comparison, research, or clean-room-later planning input. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Research benchmark note + bounded reusable primitives + explicit no-live-owner boundary. 1) What specific learned-search and ADI research value remains in yakupbilen/drl-rubiks-cube 2) What must stay research-only rather than product-donor 3) Experiment, oracle, or planning 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. yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths. Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core. Audit yakupbilen/drl-rubiks-cube as a 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. HT_cube_vision_0008 HT_cube_vision yakupbilen/drl-rubiks-cube Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 117.0 permissive_or_noncopyleft_known pattern_only_preferred The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor. Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation. Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed. Usually unnecessary unless you later decide the existing implementation is too constraining architecturally. high strategic-or-implemented-component yes v6.3_final_source_of_truth Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25. not_live_reference_or_discard_candidate phase0r_reference_benchmark_or_discard_eval Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation.
33 Hypercubers/hypercubing.xyz https://github.com/Hypercubers/hypercubing.xyz HyperTwist Locked Strategic Donor Knowledge and curriculum donor P1 7483 9238 1.0 92.0 101.0 medium Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it. repurpose moderate modification Determine whether Hypercubers/hypercubing.xyz should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks. Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer. Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer. Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell. HactarCE/Hyperspeedcube foundation + donor Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization. cubing/cubing.js 3D engine + notation/state donor Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top. tao-yu/Alg-Trainer training UX donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. VectorShell | ScriptoriumAI VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment. MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value. Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell. HT_hyper_engine_0006 HT_hyper_engine hypercubers/hypercubing.xyz Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 92.0 permissive_or_noncopyleft_known direct_incorporation_ok The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist. Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo. Preserve MIT notices and attribution where required. Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code. high permissive-knowledge-donor yes v6.3_final_source_of_truth Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status. implemented_live_permissive landed_permissive_preserve Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md.
34 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.
36 PostHog/posthog https://github.com/PostHog/posthog HyperTwist Donor Bench Adjacency / future transfer P2 7492 9247 20.0 72.0 81.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces. repurpose moderate modification Determine whether PostHog/posthog should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path. telemetry and event schemas, replay product boundaries, feature-flag governance, diagnostics, service slices, hidden modules Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits. Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits. Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr. Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr. Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer. kkoomen/qbr foundation + perception donor Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization. vivaansinghvi07/rubix-cube-solver perception + replay donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. cubing/cubing.js state/render backend Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top. VectorShell | ScriptoriumAI VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role. Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell. Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell. HT_control_plane_0001 HT_control_plane posthog/posthog Original global P0-P3 source audit retained MIT outside ee/; enterprise-restricted in ee/ known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 3 72.0 mixed_or_boundary_sensitive_known bounded_sidecar_or_selective_reimplementation The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths. Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams. Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping. Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths. high mixed-license-path-review-required no v6.3_final_source_of_truth Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25. 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.
37 HactarCE/2x2x2x2-Scrambler https://github.com/HactarCE/2x2x2x2-Scrambler HyperTwist Donor Bench Focused restrictive clean-room donor target P2 7496 9251 2.0 63.0 63.0 low-to-medium Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize. repurpose architecture only Determine the real reusable value of HactarCE/2x2x2x2-Scrambler for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces. Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training. Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators. Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters. HactarCE/Hyperspeedcube foundation repo + feature donor Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation. cubing/cubing.js engine repo + interface donor Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation. kkoomen/qbr feature extraction only Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation. multi-project Audit for hidden abstractions that travel across projects. Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks. Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem. Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision. Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket. Use v6 unified board + P2 tier packet + project design language + relevant family references. Keep as a narrow but real clean-room donor for Melinda 2x2x2x2 state encoding, handedness/parity repair, random-state generation, move-family representation, and flat debug/teaching views. GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use. Inspect HactarCE/2x2x2x2-Scrambler directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion. HT_cube_semantics_0004 HT_cube_semantics hactarce/2x2x2x2-scrambler supplemental_v6_not_runtime_anchored no v6_unified_source_of_truth_pack GPL-3.0 known_from_reference_material uploaded_reference_docs 2 3 63.0 mixed_or_boundary_sensitive_known reverse_engineer_preferred The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification. Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification. Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path. Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code. high gpl-clean-room-donor no v6.3_final_source_of_truth Assigned to HT_cube_semantics during cluster normalization on 2026-04-25. implemented_live_clean_room_verified landed_clean_room_preserve Later clean-room sequence closed through Bound 4. Preserve as the landed first-party Melinda state legality, random-state generation, move-family application, scramble-packet, and flat debug/teaching 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.
38 SYSTRAN/faster-whisper https://github.com/SYSTRAN/faster-whisper multi-project Donor Bench Cross-project / future-adjacent P2 8351 10345 49.0 71.0 80.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers. repurpose moderate modification Determine whether SYSTRAN/faster-whisper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path. STT API surface, VAD chunking, batch inference, timestamps, service boundaries, model/runtime constraints, hidden modules Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries. Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage. Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS. Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline. Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor. project-local anchor base + donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. shared portfolio utility augmenter Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. cross-project transfer candidate future merger Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. project-local first Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. SYSTRAN/faster-whisper is placed in Donor Bench for multi-project because it provides the clearest Python STT service-layer path in the voice stack. Recommended action remains repurpose, but the real retained value is batch transcription, VAD-aware chunking, timestamps, and Python-side service integration rather than any code-intelligence or graph role. Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current Python STT donor and service-layer candidate in the voice stack. Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell. MU_misc_0001 MU_misc systran/faster-whisper Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Potentially relevant yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 4 3 71.0 permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default. Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam. Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license. Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies. high model-artifact-review-required yes v6.3_final_source_of_truth Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff. implemented_live_permissive landed_permissive_preserve Phase 6R-F is closed. Preserve as the landed complementary Python transcription-orchestration lane above the existing speech session boundary; do not widen it into top-level provider/session ownership.
39 coqui-ai/TTS https://github.com/coqui-ai/TTS multi-project Donor Bench Cross-project / future-adjacent P2 8352 10346 49.0 71.0 80.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration. repurpose moderate modification Determine whether coqui-ai/TTS should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path. API surface, synthesis orchestration, multilingual and speaker handling, voice conversion, model registry, deployment boundary, hidden modules Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata. Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper. Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline. Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor. project-local anchor base + donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. shared portfolio utility augmenter Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. cross-project transfer candidate future merger Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. VectorShell | HyperTwist | ScriptoriumAI This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. coqui-ai/TTS is placed in Donor Bench for multi-project because it provides the richest current voice-output and coaching architecture in the stack. Recommended action remains repurpose, but the real retained value is synthesis orchestration, multilingual and speaker handling, XTTS/voice-conversion paths, and model-registry discipline rather than broad assistant scope. Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current voice and coaching donor, but boundary-sensitive because code and model payload licensing must be separated. Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell. MU_misc_0002 MU_misc coqui-ai/tts Original global P0-P3 source audit retained MPL-2.0 code; mixed model payload licenses known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Potentially relevant yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 4 3 71.0 mixed_or_boundary_sensitive_known bounded_sidecar_or_selective_reimplementation Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency. Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption. Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping. Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path. medium model-license-selection-required yes v6.3_final_source_of_truth Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff. implemented_live_boundary_sensitive landed_boundary_sensitive_preserve Phase 6R-H is closed. Preserve as the landed bounded advanced narration orchestration lane under the current MPL boundary doctrine; keep model, voice, and payload review separate from the code-license judgment.
40 ggml-org/whisper.cpp https://github.com/ggml-org/whisper.cpp multi-project Donor Bench Cross-project / future-adjacent P2 8353 10347 49.0 71.0 80.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration. repurpose moderate modification Determine whether ggml-org/whisper.cpp should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path. native STT runtime seam, VAD, grammar-constrained decoding, server boundary, portability, hidden modules Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts. Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks. Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS. Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline. Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor. project-local anchor base + donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. shared portfolio utility augmenter Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. cross-project transfer candidate future merger Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. VectorShell | HyperTwist | ScriptoriumAI This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. ggml-org/whisper.cpp is placed in Donor Bench for multi-project because it is the clearest native/offline STT anchor in the voice stack. Recommended action remains repurpose, but the real retained value is a bounded speech-input runtime, VAD, grammar-constrained decoding, and portable deployment rather than a full product shell. Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current native/offline STT sidecar candidate in the voice stack. Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell. MU_misc_0003 MU_misc ggml-org/whisper.cpp Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Potentially relevant yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 4 3 71.0 permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default. Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam. Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license. Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime. high model-artifact-review-recommended yes v6.3_final_source_of_truth Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff. implemented_live_permissive landed_permissive_preserve Phase 6R-E, Phase 6R-U, Phase 6R-V, and Phase 6R-W are closed. Preserve as the landed bounded native speech-session, microphone-shell, permission-readiness, and payload-custody lane; keep broader payload shipping and model-license review separate.
41 rhasspy/piper https://github.com/rhasspy/piper multi-project Donor Bench Cross-project / future-adjacent P2 8354 10348 49.0 71.0 80.0 medium Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration. repurpose moderate modification Determine whether rhasspy/piper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path. local TTS runtime seam, ONNX and eSpeak integration, streaming output, HTTP service boundary, voice catalog, hidden modules Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints. Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints. Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper. Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline. Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor. project-local anchor base + donor Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. shared portfolio utility augmenter Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. cross-project transfer candidate future merger Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. VectorShell | HyperTwist | ScriptoriumAI This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters. Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack. Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role. Capability inventory + salvage targets + promotion/demotion verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope. Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate. Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell. MU_misc_0004 MU_misc rhasspy/piper Original global P0-P3 source audit retained MIT code; voice artifacts reviewed separately known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Potentially relevant yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 4 3 71.0 permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption. Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review. Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license. Usually unnecessary unless you later replace the runtime for packaging or architecture reasons. high voice-artifact-review-required yes v6.3_final_source_of_truth Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff. implemented_live_permissive landed_permissive_preserve Phase 6R-G is closed. Preserve as the landed bounded local narration sidecar lane; keep broad voice-model and payload review separate.
42 met4citizen/TalkingHead https://github.com/met4citizen/TalkingHead HyperTwist Donor Bench Browser embodied coach surface P2 medium Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces. repurpose moderate modification Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded. avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions. Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior. Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture. Repurpose here means: turn it into a browser-side embodied coach or companion layer. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack. Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell. HT_browser_surface_0001 HT_browser_surface met4citizen/talkinghead MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell. Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell. Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. implemented_live_permissive landed_permissive_preserve Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md.
43 apache/echarts https://github.com/apache/echarts HyperTwist Donor Bench Browser analytics and reporting surface P2 medium Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system. repurpose moderate modification Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces. option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior. Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface. Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture. Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack. Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references. HT_browser_surface_0002 HT_browser_surface apache/echarts Apache-2.0 known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor. Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell. Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high notice-file-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. implemented_live_permissive landed_permissive_preserve Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md.
45 KhronosGroup/glTF-Sample-Viewer https://github.com/KhronosGroup/glTF-Sample-Viewer HyperTwist Donor Bench Browser asset validation and viewer surface P3 medium Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer. repurpose moderate modification Confirm that KhronosGroup/glTF-Sample-Viewer remains a closed subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any. validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell Inspect the retained standards-aware asset QA and validation sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps. Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer. Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces. Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria. 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling. Audit KhronosGroup/glTF-Sample-Viewer only as a closed subordinate standards-aware asset QA and validation sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane. HT_browser_surface_0004 HT_browser_surface khronosgroup/gltf-sample-viewer Apache-2.0 known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor. Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell. Preserve LICENSE and NOTICE materials where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high notice-file-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase2rb_browser_viewer_subordinate_gap_eval_only Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; no default widening packet is open.
46 google/model-viewer https://github.com/google/model-viewer HyperTwist Donor Bench Browser 3D presentation and inspection surface P2 medium Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project. repurpose moderate modification Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces. custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces. Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support. Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows. Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack. Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction. HT_browser_surface_0005 HT_browser_surface google/model-viewer Apache-2.0 known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor. Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell. Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high notice-file-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. implemented_live_permissive landed_permissive_preserve Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md.
47 mrdoob/three.js https://github.com/mrdoob/three.js HyperTwist Donor Bench Browser 3D substrate P2 medium Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction. repurpose moderate modification Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces. renderer, scene, camera, math core, loaders, WebXR manager, addons, editor Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell. Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell. Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine. Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack. Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual. HT_browser_surface_0006 HT_browser_surface mrdoob/three.js MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation. Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. implemented_live_permissive landed_permissive_preserve Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md.
48 pmndrs/postprocessing https://github.com/pmndrs/postprocessing HyperTwist Merge Bench Browser post-processing substrate P3 medium Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package. integrate moderate modification Confirm that pmndrs/postprocessing remains a closed subordinate browser post-effect substrate beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any. EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions Inspect the retained browser post-effect substrate slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps. Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions. Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces. Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria. 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane. Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers. Audit pmndrs/postprocessing only as a closed subordinate browser post-effect substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane. HT_browser_surface_0007 HT_browser_surface pmndrs/postprocessing Zlib known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency. Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase2rb_browser_support_subordinate_gap_eval_only Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser post-effect substrate beneath the landed browser-spatial owner trio; no default widening packet is open.
49 pmndrs/react-three-fiber https://github.com/pmndrs/react-three-fiber HyperTwist Donor Bench Browser React 3D substrate P2 medium Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer. repurpose moderate modification Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes. Canvas, createRoot, reconciler runtime, event system, hooks, native path Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points. Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path. Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer. Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack. Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference. HT_browser_surface_0008 HT_browser_surface pmndrs/react-three-fiber MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate. Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. implemented_live_permissive landed_permissive_preserve Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md.
50 pmndrs/drei https://github.com/pmndrs/drei HyperTwist Merge Bench Browser 3D helper and abstraction layer P3 medium Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl. integrate moderate modification Confirm that pmndrs/drei remains a closed subordinate browser helper and abstraction shelf beneath the landed browser-spatial owner trio and pmndrs/react-three-fiber, and record only narrower sidecar-gap reopen criteria, if any. Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior Inspect the retained browser helper and abstraction shelf slice only in relation to the landed browser-spatial owner trio and pmndrs/react-three-fiber, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps. Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities. Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl. Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria. 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation. Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions. Audit pmndrs/drei only as a closed subordinate browser helper and abstraction shelf row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and pmndrs/react-three-fiber and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane. HT_browser_surface_0009 HT_browser_surface pmndrs/drei MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber. Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase2rb_browser_support_subordinate_gap_eval_only Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed Phase 3R-F stack; no default widening packet is open.
51 pmndrs/xr https://github.com/pmndrs/xr HyperTwist Donor Bench Browser XR and immersive UI substrate P2 medium Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack. repurpose moderate modification Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces. XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages. Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior. Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions. Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack. Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual. HT_browser_surface_0010 HT_browser_surface pmndrs/xr MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor. Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. implemented_live_permissive landed_permissive_preserve Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md.
100
101
102
103
104
105
106
108
109
110
111
112
113
114
236
237
238
239
240
241
242
243