diff --git a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json index 4c3f471..54c2e39 100644 --- a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json +++ b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json @@ -1,13 +1,13 @@ { - "generated_at": "2026-05-13T16:20:00Z", - "slice": "catalog-materialization", - "slice_status": "closed", - "counts": { - "content_packs": 14, - "track_manifests": 14, - "deck_import_specs": 498, - "runtime_content_bundles": 498, - "reference_targets": 29, - "overlap_pruned_exclusions": 29 - } -} + "generated_at": "2026-05-13T19:00:00Z", + "slice": "catalog-materialization", + "slice_status": "closed", + "counts": { + "content_packs": 14, + "track_manifests": 14, + "deck_import_specs": 498, + "runtime_content_bundles": 498, + "reference_targets": 36, + "overlap_pruned_exclusions": 36 + } +} \ No newline at end of file diff --git a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json index d18ad85..09a4c31 100644 --- a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json +++ b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json @@ -1,1187 +1,1481 @@ { - "generated_at": "2026-05-13T16:20:00Z", - "reference_targets": [ - { - "ReferenceTargetId": "reference/speedcubedb-course-reference-page-speedcubedb-root", - "SurfaceType": "course-reference", - "TrackTitle": "Advanced 3x3 Systems", - "ItemTitle": "Speedcubedb Root", - "IncorporationChannel": "course-reference-supplement", - "TargetAssetFamily": "reference-page", - "PuzzleFamily": "ClassicCube", - "NotationProfile": "classic-wca", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "SpeedCubeDB", - "SourceLicense": "retained-web-content", - "SourceTrackId": "advanced-3x3-systems", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten curriculum brief for Speedcubedb Root, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "speedcubedb", - "source_scope": "httrack-retained", - "structure_template": "course-reference-page", - "family": "speedcubedb-root", - "subset": null - }, - "MaterializationNotes": [ - "Rewritten curriculum brief for Speedcubedb Root, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/speedcubedb-tool-reference-page-speedcubedb-root", - "SurfaceType": "tool-reference", - "TrackTitle": "Advanced 3x3 Systems", - "ItemTitle": "Speedcubedb Root", - "IncorporationChannel": "feature-reference", - "TargetAssetFamily": "tool-note", - "PuzzleFamily": "ClassicCube", - "NotationProfile": "classic-wca", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "SpeedCubeDB", - "SourceLicense": "retained-web-content", - "SourceTrackId": "advanced-3x3-systems", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Feature-semantics reference for Speedcubedb Root, rewritten as first-party product guidance instead of donor utility-page copy." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "speedcubedb", - "source_scope": "httrack-retained", - "structure_template": "tool-reference-page", - "family": "speedcubedb-root", - "subset": null - }, - "MaterializationNotes": [ - "Feature-semantics reference for Speedcubedb Root, rewritten as first-party product guidance instead of donor utility-page copy.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-com-course-reference-page-magic-cube-4d-solution", - "SurfaceType": "course-reference", - "TrackTitle": "Hypercubing Software Manuals", - "ItemTitle": "Magic Cube 4D Solution Notes", - "IncorporationChannel": "course-reference-supplement", - "TargetAssetFamily": "reference-page", - "PuzzleFamily": "Hypercube", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "superliminal.com", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-software-manuals", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten curriculum brief for Magic Cube 4D Solution Notes, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal.com", - "source_scope": "httrack-retained", - "structure_template": "course-reference-page", - "family": "Magic Cube 4D", - "subset": "solution" - }, - "MaterializationNotes": [ - "Rewritten curriculum brief for Magic Cube 4D Solution Notes, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-cube-4d", - "SurfaceType": "software-manual", - "TrackTitle": "Hypercubing Software Manuals", - "ItemTitle": "Magic Cube 4D Manual", - "IncorporationChannel": "software-manual-surface", - "TargetAssetFamily": "manual-page", - "PuzzleFamily": "Hypercube", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "superliminal.com", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-software-manuals", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten operational guide target for Magic Cube 4D Manual, preserving behavior and workflow semantics without reusing donor manual prose." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal.com", - "source_scope": "httrack-retained", - "structure_template": "software-manual-reference-page", - "family": "Magic Cube 4D", - "subset": null - }, - "MaterializationNotes": [ - "Rewritten operational guide target for Magic Cube 4D Manual, preserving behavior and workflow semantics without reusing donor manual prose.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-cube-7d", - "SurfaceType": "software-manual", - "TrackTitle": "Hypercubing Software Manuals", - "ItemTitle": "Magic Cube 7D Manual", - "IncorporationChannel": "software-manual-surface", - "TargetAssetFamily": "manual-page", - "PuzzleFamily": "Hypercube", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "superliminal.com", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-software-manuals", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten operational guide target for Magic Cube 7D Manual, preserving behavior and workflow semantics without reusing donor manual prose." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal.com", - "source_scope": "httrack-retained", - "structure_template": "software-manual-reference-page", - "family": "Magic Cube 7D", - "subset": null - }, - "MaterializationNotes": [ - "Rewritten operational guide target for Magic Cube 7D Manual, preserving behavior and workflow semantics without reusing donor manual prose.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-hyperbolic-tile", - "SurfaceType": "software-manual", - "TrackTitle": "Hypercubing Software Manuals", - "ItemTitle": "Magic Hyperbolic Tile Manual", - "IncorporationChannel": "software-manual-surface", - "TargetAssetFamily": "manual-page", - "PuzzleFamily": "Tiling", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "superliminal.com", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-software-manuals", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten operational guide target for Magic Hyperbolic Tile Manual, preserving behavior and workflow semantics without reusing donor manual prose." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal.com", - "source_scope": "httrack-retained", - "structure_template": "software-manual-reference-page", - "family": "Magic Hyperbolic Tile", - "subset": null - }, - "MaterializationNotes": [ - "Rewritten operational guide target for Magic Hyperbolic Tile Manual, preserving behavior and workflow semantics without reusing donor manual prose.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-puzzle-ultimate", - "SurfaceType": "software-manual", - "TrackTitle": "Hypercubing Software Manuals", - "ItemTitle": "Magic Puzzle Ultimate Manual", - "IncorporationChannel": "software-manual-surface", - "TargetAssetFamily": "manual-page", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "superliminal.com", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-software-manuals", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten operational guide target for Magic Puzzle Ultimate Manual, preserving behavior and workflow semantics without reusing donor manual prose." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal.com", - "source_scope": "httrack-retained", - "structure_template": "software-manual-reference-page", - "family": "Magic Puzzle Ultimate", - "subset": null - }, - "MaterializationNotes": [ - "Rewritten operational guide target for Magic Puzzle Ultimate Manual, preserving behavior and workflow semantics without reusing donor manual prose.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-simplex-5d", - "SurfaceType": "software-manual", - "TrackTitle": "Hypercubing Software Manuals", - "ItemTitle": "Magic Simplex 5D Manual", - "IncorporationChannel": "software-manual-surface", - "TargetAssetFamily": "manual-page", - "PuzzleFamily": "Hypercube", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "superliminal.com", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-software-manuals", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Rewritten operational guide target for Magic Simplex 5D Manual, preserving behavior and workflow semantics without reusing donor manual prose." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal.com", - "source_scope": "httrack-retained", - "structure_template": "software-manual-reference-page", - "family": "Magic Simplex 5D", - "subset": null - }, - "MaterializationNotes": [ - "Rewritten operational guide target for Magic Simplex 5D Manual, preserving behavior and workflow semantics without reusing donor manual prose.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/superliminal-wiki-historical-reference-page-hypercubing-reference", - "SurfaceType": "historical-reference", - "TrackTitle": "Hypercubing Reference", - "ItemTitle": "Hypercubing Historical Reference", - "IncorporationChannel": "historical-reference-supplement", - "TargetAssetFamily": "history-note", - "PuzzleFamily": "Hypercube", - "NotationProfile": "hypercubing-standard", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "Superliminal Wiki", - "SourceLicense": "retained-web-content", - "SourceTrackId": "hypercubing-reference", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "Historical and conceptual reference lane for hypercubing context, rewritten into concise HyperTwist-native background guidance." - }, - "PreserveFactualElements": [ - "topic scope", - "page role", - "factual software or method semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional/reference prose" - ], - "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", - "MatchFilter": { - "source": "superliminal-wiki", - "source_scope": "httrack-retained", - "structure_template": "historical-reference-page", - "family": "hypercubing-reference", - "subset": null - }, - "MaterializationNotes": [ - "Historical and conceptual reference lane for hypercubing context, rewritten into concise HyperTwist-native background guidance.", - "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." - ] - }, - { - "ReferenceTargetId": "reference/hypercubing-xyz-course-reference-page-progression", - "SurfaceType": "course-reference", - "TrackTitle": "Hypercubing Progression", - "ItemTitle": "Hypercubing Progression Ladder", - "IncorporationChannel": "course-reference-supplement", - "TargetAssetFamily": "reference-page", - "PuzzleFamily": "Hypercube", - "NotationProfile": "hypercubing-standard", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "Hypercubers/hypercubing.xyz", - "SourceLicense": "MIT", - "SourceTrackId": "progression", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist progression contract target preserving stage order, prerequisites, and widening boundaries from the donor progression guide." - }, - "PreserveFactualElements": [ - "stage ordering", - "prerequisite relationships", - "family branching semantics" - ], - "RewriteRequiredElements": [ - "page title", - "all instructional prose", - "all donor-specific presentation language" - ], - "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", - "MatchFilter": { - "source": "hypercubing.xyz", - "source_scope": "repo-backed", - "structure_template": "progression-reference-page", - "family": "hypercubing-progression", - "subset": null - }, - "MaterializationNotes": [ - "Preserve the donor\u0027s progression ordering and branch logic while rewriting the actual instructional surface in first-party HyperTwist language.", - "This target feeds the Phase 3R-B knowledge and curriculum lane rather than the runtime simulation lane." - ] - }, - { - "ReferenceTargetId": "reference/hypercubing-xyz-notation-reference-page-cell-turning-hypercubes", - "SurfaceType": "notation-reference", - "TrackTitle": "Hypercubing Notation", - "ItemTitle": "Cell-Turning Hypercube Notation", - "IncorporationChannel": "notation-reference-supplement", - "TargetAssetFamily": "glossary-page", - "PuzzleFamily": "Hypercube", - "NotationProfile": "hypercubing-standard", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "Hypercubers/hypercubing.xyz", - "SourceLicense": "MIT", - "SourceTrackId": "notation", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist notation reference target preserving factual cell, twist, plane-rotation, and metric semantics from the donor notation guide." - }, - "PreserveFactualElements": [ - "cell naming semantics", - "twist and rotation rules", - "metric distinctions" - ], - "RewriteRequiredElements": [ - "page title", - "all explanatory prose", - "all donor-specific examples beyond factual notation payloads" - ], - "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", - "MatchFilter": { - "source": "hypercubing.xyz", - "source_scope": "repo-backed", - "structure_template": "notation-reference-page", - "family": "cell-turning-hypercubes", - "subset": null - }, - "MaterializationNotes": [ - "Preserve factual notation grammar and cross-links while rewriting reference prose into HyperTwist-native documentation.", - "This target is paired with the compiled Phase 3R-B notation glossary contract." - ] - }, - { - "ReferenceTargetId": "reference/hypercubing-xyz-tool-reference-page-software-matrix", - "SurfaceType": "tool-reference", - "TrackTitle": "Hypercubing Software", - "ItemTitle": "Hypercubing Software Matrix", - "IncorporationChannel": "feature-reference", - "TargetAssetFamily": "tool-note", - "PuzzleFamily": "Hypercube", - "NotationProfile": "hypercubing-standard", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "Hypercubers/hypercubing.xyz", - "SourceLicense": "MIT", - "SourceTrackId": "software", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist software-comparison target preserving factual platform and capability semantics from the donor feature matrix." - }, - "PreserveFactualElements": [ - "platform coverage", - "capability taxonomy", - "program-role distinctions" - ], - "RewriteRequiredElements": [ - "page title", - "all donor prose", - "all donor presentation formatting" - ], - "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", - "MatchFilter": { - "source": "hypercubing.xyz", - "source_scope": "repo-backed", - "structure_template": "tool-reference-page", - "family": "software-matrix", - "subset": null - }, - "MaterializationNotes": [ - "Preserve factual feature, platform, and recommendation semantics while rewriting the reference surface in first-party HyperTwist terms.", - "This target supports bounded software-comparison and community-guidance surfaces, not runtime ownership." - ] - }, - { - "ReferenceTargetId": "reference/hypercubing-xyz-community-reference-page-leaderboards", - "SurfaceType": "community-reference", - "TrackTitle": "Hypercubing Leaderboards", - "ItemTitle": "Hypercubing Leaderboard Conventions", - "IncorporationChannel": "community-reference-supplement", - "TargetAssetFamily": "leaderboard-note", - "PuzzleFamily": "Hypercube", - "NotationProfile": "hypercubing-standard", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "Hypercubers/hypercubing.xyz", - "SourceLicense": "MIT", - "SourceTrackId": "leaderboards", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist leaderboard/report contract target preserving event identity, time formatting, relative-date, and solver-profile semantics from the donor community site." - }, - "PreserveFactualElements": [ - "event naming and ids", - "format semantics", - "display-rule conventions" - ], - "RewriteRequiredElements": [ - "page title", - "all donor prose", - "all donor HTML or presentation output" - ], - "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", - "MatchFilter": { - "source": "hypercubing.xyz", - "source_scope": "repo-backed", - "structure_template": "community-reference-page", - "family": "leaderboards", - "subset": null - }, - "MaterializationNotes": [ - "Preserve factual leaderboard contracts while rewriting community-reference copy into HyperTwist-native language.", - "This target pairs with the compiled Phase 3R-B leaderboard policy and event schema." - ] - }, - { - "ReferenceTargetId": "reference/apache-echarts-analytics-reference-page-session-outcome-and-progress", - "SurfaceType": "analytics-reference", - "TrackTitle": "Training Analytics", - "ItemTitle": "Session Outcome and Progress Reporting", - "IncorporationChannel": "analytics-report-contract", - "TargetAssetFamily": "dashboard-report", - "PuzzleFamily": "ClassicCube", - "NotationProfile": "classic-wca", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "apache/echarts", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "analytics/session-outcome-balance", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist analytics contract target preserving bounded option, data-store, and outcome-reporting semantics from the retained echarts lane." - }, - "PreserveFactualElements": [ - "option and state layering", - "dataset separation", - "series-oriented outcome reporting" - ], - "RewriteRequiredElements": [ - "all donor source text", - "all donor component names", - "all donor shell assumptions" - ], - "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", - "MatchFilter": { - "source": "apache/echarts", - "source_scope": "repo-backed", - "structure_template": "analytics-report-reference-page", - "family": "session-outcome-and-progress", - "subset": null - }, - "MaterializationNotes": [ - "Preserve the donor\u0027s option and dataset separation while rewriting the report contract in first-party HyperTwist analytics language.", - "This target pairs with the compiled Phase 3R-C analytics report bundle and runtime data-view helpers." - ] - }, - { - "ReferenceTargetId": "reference/apache-echarts-report-export-reference-page-data-view-and-export", - "SurfaceType": "report-export-reference", - "TrackTitle": "Training Analytics", - "ItemTitle": "Analytics Data View and Export", - "IncorporationChannel": "report-export-contract", - "TargetAssetFamily": "export-note", - "PuzzleFamily": "ClassicCube", - "NotationProfile": "classic-wca", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "apache/echarts", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "analytics/export", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist analytics export target preserving bounded tabular data-view, image export, and SSR-ready reporting expectations from the retained echarts lane." - }, - "PreserveFactualElements": [ - "tabular data-view contract", - "image export behavior", - "SSR-ready report shell expectations" - ], - "RewriteRequiredElements": [ - "all donor UI wording", - "all donor shell framing", - "all donor implementation-specific presentation" - ], - "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", - "MatchFilter": { - "source": "apache/echarts", - "source_scope": "repo-backed", - "structure_template": "report-export-reference-page", - "family": "report-data-view-and-export", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded export and data-view semantics while rewriting the surfaced report shell and copy in first-party HyperTwist terms.", - "This target feeds the Phase 3R-C TSV data-view and accessible export layer, not a generic BI shell." - ] - }, - { - "ReferenceTargetId": "reference/apache-echarts-analytics-interaction-reference-page-timing-trend-history", - "SurfaceType": "analytics-interaction-reference", - "TrackTitle": "Training Analytics", - "ItemTitle": "Timing Trend History and Overview", - "IncorporationChannel": "analytics-interaction-contract", - "TargetAssetFamily": "interaction-note", - "PuzzleFamily": "ClassicCube", - "NotationProfile": "classic-wca", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "apache/echarts", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "analytics/timing-trend-rolling-windows", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist timing-trend interaction target preserving bounded zoom-history, thumbnail overview, and rolling-window inspection semantics from the retained echarts lane." - }, - "PreserveFactualElements": [ - "history-aware zoom interactions", - "thumbnail overview behavior", - "windowed timing-trend inspection" - ], - "RewriteRequiredElements": [ - "all donor component wording", - "all donor UI text", - "all donor chart-shell presentation" - ], - "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", - "MatchFilter": { - "source": "apache/echarts", - "source_scope": "repo-backed", - "structure_template": "analytics-interaction-reference-page", - "family": "timing-trend-history", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded history and overview semantics while rewriting the actual interaction copy and report framing in first-party HyperTwist language.", - "This target pairs with the Phase 3R-C rolling-window timing report bundle." - ] - }, - { - "ReferenceTargetId": "reference/apache-echarts-analytics-explainer-reference-page-optional-3d-sidecar", - "SurfaceType": "analytics-explainer-reference", - "TrackTitle": "Training Analytics", - "ItemTitle": "Optional 3D Analytics Sidecar", - "IncorporationChannel": "analytics-sidecar-boundary", - "TargetAssetFamily": "explainer-note", - "PuzzleFamily": "ClassicCube", - "NotationProfile": "classic-wca", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "apache/echarts", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "analytics/live-split-ladder", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist sidecar-boundary target preserving how optional richer explainers stay subordinate to the apache/echarts lane while bounded concepts from echarts-gl and zrender remain support-only." - }, - "PreserveFactualElements": [ - "optional 3D analytics sidecar boundary", - "camera and zoom helper behavior", - "subordinate 2D and GL renderer layering" - ], - "RewriteRequiredElements": [ - "all donor implementation text", - "all donor framework naming", - "all donor chart-shell presentation" - ], - "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", - "MatchFilter": { - "source": "apache/echarts", - "source_scope": "repo-backed", - "structure_template": "analytics-explainer-reference-page", - "family": "optional-3d-analytics-explainer", - "subset": null - }, - "MaterializationNotes": [ - "Preserve the subordinate-sidecar boundary while rewriting the actual explainer framing in first-party HyperTwist language.", - "This target keeps `ecomfe/echarts-gl` and `ecomfe/zrender` explicit as support-only beneath the landed `apache/echarts` lane." - ] - }, - { - "ReferenceTargetId": "reference/google-model-viewer-browser-viewer-reference-page-embed-contract", - "SurfaceType": "browser-viewer-reference", - "TrackTitle": "Browser Viewer and Asset QA", - "ItemTitle": "Browser Viewer Embed Contract", - "IncorporationChannel": "viewer-embed-contract", - "TargetAssetFamily": "support-widget", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "google/model-viewer", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "viewer/browser-viewer-embed", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist browser viewer target preserving bounded embed, camera, annotation, and readiness semantics from the retained model-viewer lane." - }, - "PreserveFactualElements": [ - "embeddable viewer lifecycle", - "camera and framing state", - "annotation and load-progress semantics" - ], - "RewriteRequiredElements": [ - "all donor docs and demo copy", - "all donor shell assumptions", - "all donor site framing" - ], - "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", - "MatchFilter": { - "source": "google/model-viewer", - "source_scope": "repo-backed", - "structure_template": "browser-viewer-reference-page", - "family": "browser-viewer-embed", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded viewer, camera, and annotation semantics while rewriting the actual support-plane viewer shell in first-party HyperTwist terms.", - "This target pairs with the compiled Phase 3R-D browser viewer embed contract and runtime access layer." - ] - }, - { - "ReferenceTargetId": "reference/google-model-viewer-browser-editor-reference-page-compact-editor", - "SurfaceType": "browser-editor-reference", - "TrackTitle": "Browser Viewer and Asset QA", - "ItemTitle": "Compact Browser Editor and Inspection", - "IncorporationChannel": "viewer-editor-contract", - "TargetAssetFamily": "editor-panel", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "google/model-viewer/packages/space-opera", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "viewer/compact-editor", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist compact editor target preserving bounded inspection, camera, hotspot, and preview-state semantics from the retained space-opera lane." - }, - "PreserveFactualElements": [ - "compact inspection state", - "camera settings behavior", - "hotspot authoring boundaries" - ], - "RewriteRequiredElements": [ - "all donor UI wording", - "all donor shell framing", - "all donor site-navigation assumptions" - ], - "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", - "MatchFilter": { - "source": "google/model-viewer", - "source_scope": "repo-backed", - "structure_template": "browser-editor-reference-page", - "family": "compact-editor-and-inspection", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded compact editor and inspection semantics while rewriting the actual shell and copy in first-party HyperTwist language.", - "This target pairs with the compiled Phase 3R-D editor contract beneath the landed browser viewer lane." - ] - }, - { - "ReferenceTargetId": "reference/google-model-viewer-browser-export-reference-page-snippet-and-export", - "SurfaceType": "browser-export-reference", - "TrackTitle": "Browser Viewer and Asset QA", - "ItemTitle": "Snippet and Export Surface", - "IncorporationChannel": "viewer-export-contract", - "TargetAssetFamily": "export-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "google/model-viewer/packages/modelviewer.dev", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "viewer/snippet-and-export", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist export target preserving bounded snippet, preview, and portable embed semantics from the retained modelviewer.dev and space-opera sidecars." - }, - "PreserveFactualElements": [ - "portable snippet generation", - "preview and export posture", - "single-source embed expectations" - ], - "RewriteRequiredElements": [ - "all donor docs copy", - "all donor example-shell framing", - "all donor tutorial wording" - ], - "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", - "MatchFilter": { - "source": "google/model-viewer", - "source_scope": "repo-backed", - "structure_template": "browser-export-reference-page", - "family": "snippet-and-export", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded snippet and export semantics while rewriting the actual support-plane export shell in first-party HyperTwist language.", - "This target keeps docs/demo infrastructure subordinate while still surfacing snippet and portable-embed value." - ] - }, - { - "ReferenceTargetId": "reference/khronos-gltf-browser-qa-reference-page-validation-and-statistics", - "SurfaceType": "asset-qa-reference", - "TrackTitle": "Browser Viewer and Asset QA", - "ItemTitle": "Asset Validation and Statistics", - "IncorporationChannel": "asset-qa-contract", - "TargetAssetFamily": "qa-checklist", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "KhronosGroup/glTF-Sample-Viewer", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "qa/asset-validation-and-statistics", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist QA target preserving bounded validator, statistics, camera export, and failure-reporting semantics from the retained Khronos viewer lane." - }, - "PreserveFactualElements": [ - "validator and statistics boundary", - "standards-aware preview state", - "camera export and capture posture" - ], - "RewriteRequiredElements": [ - "all donor shell framing", - "all donor UI wording", - "all donor product assumptions" - ], - "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", - "MatchFilter": { - "source": "KhronosGroup/glTF-Sample-Viewer", - "source_scope": "repo-backed", - "structure_template": "asset-qa-reference-page", - "family": "asset-validation-and-statistics", - "subset": null - }, - "MaterializationNotes": [ - "Preserve standards-aware validation and statistics semantics while rewriting the surfaced QA shell in first-party HyperTwist terms.", - "This target pairs with the compiled Phase 3R-D QA checks and keeps the Khronos lane subordinate to the landed viewer owner." - ] - }, - { - "ReferenceTargetId": "reference/google-model-viewer-renderer-comparison-reference-page-fidelity", - "SurfaceType": "renderer-comparison-reference", - "TrackTitle": "Browser Viewer and Asset QA", - "ItemTitle": "Renderer Comparison and Fidelity", - "IncorporationChannel": "renderer-comparison-contract", - "TargetAssetFamily": "regression-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "google/model-viewer/packages/render-fidelity-tools", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "qa/renderer-comparison-and-fidelity", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist renderer-comparison target preserving bounded golden-result, delta, and threshold semantics from the retained render-fidelity-tools lane." - }, - "PreserveFactualElements": [ - "golden-result comparison", - "delta and threshold reporting", - "renderer parity discipline" - ], - "RewriteRequiredElements": [ - "all donor workflow text", - "all donor shell framing", - "all donor docs/demo wording" - ], - "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", - "MatchFilter": { - "source": "google/model-viewer", - "source_scope": "repo-backed", - "structure_template": "renderer-comparison-reference-page", - "family": "renderer-comparison-and-fidelity", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded renderer-regression semantics while rewriting the surfaced comparison shell in first-party HyperTwist language.", - "This target keeps render-fidelity-tools subordinate to the landed viewer lane and the Khronos reference renderer." - ] - }, - { - "ReferenceTargetId": "reference/google-model-viewer-docs-boundary-reference-page-demo-separation", - "SurfaceType": "docs-boundary-reference", - "TrackTitle": "Browser Viewer and Asset QA", - "ItemTitle": "Docs and Demo Separation Boundary", - "IncorporationChannel": "docs-demo-boundary", - "TargetAssetFamily": "docs-boundary-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "google/model-viewer/packages/modelviewer.dev", - "SourceLicense": "Apache-2.0", - "SourceTrackId": "viewer/docs-demo-separation", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist boundary target preserving snippet-to-demo infrastructure insights while keeping docs and demo shells explicitly outside the shippable viewer lane." - }, - "PreserveFactualElements": [ - "snippet-to-demo stamping", - "interactive docs support patterns", - "demo-only shell boundaries" - ], - "RewriteRequiredElements": [ - "all donor docs copy", - "all donor navigation framing", - "all donor example-site assumptions" - ], - "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", - "MatchFilter": { - "source": "google/model-viewer", - "source_scope": "repo-backed", - "structure_template": "docs-boundary-reference-page", - "family": "docs-demo-separation", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded docs/demo separation semantics while rewriting the actual support copy and shell in first-party HyperTwist language.", - "This target keeps modelviewer.dev explicitly subordinate to the landed browser viewer lane." - ] - }, - { - "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-reference-page-narration", - "SurfaceType": "companion-reference", - "TrackTitle": "Embodied Companion and Narrated Coaching", - "ItemTitle": "Embodied Companion Narration", - "IncorporationChannel": "narration-contract", - "TargetAssetFamily": "companion-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "met4citizen/TalkingHead", - "SourceLicense": "MIT", - "SourceTrackId": "companion/narration-contract", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist narration target preserving queued coach speech, subtitle timing, viseme alignment, and gesture-aware companion presentation from the retained TalkingHead lane." - }, - "PreserveFactualElements": [ - "queued speech lifecycle", - "subtitle timing", - "viseme alignment", - "gesture and mood cues" - ], - "RewriteRequiredElements": [ - "all donor example-shell framing", - "all donor vendor-specific copy", - "all donor avatar-demo wording" - ], - "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", - "MatchFilter": { - "source": "met4citizen/TalkingHead", - "source_scope": "repo-backed", - "structure_template": "embodied-companion-reference-page", - "family": "embodied-companion-narration", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded coach narration semantics while rewriting the actual companion shell in first-party HyperTwist terms.", - "This target pairs with the compiled Phase 3R-E narration contract and runtime access layer." - ] - }, - { - "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-subtitle-reference-page-sync", - "SurfaceType": "companion-subtitle-reference", - "TrackTitle": "Embodied Companion and Narrated Coaching", - "ItemTitle": "Subtitle and Viseme Synchronization", - "IncorporationChannel": "subtitle-sync-contract", - "TargetAssetFamily": "subtitle-checklist", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "met4citizen/TalkingHead", - "SourceLicense": "MIT", - "SourceTrackId": "companion/subtitle-and-viseme-sync", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist subtitle target preserving bounded caption timing, marker sync, and viseme-envelope behavior from the retained TalkingHead lane." - }, - "PreserveFactualElements": [ - "word-level subtitle cues", - "marker sync", - "blendshape viseme envelopes" - ], - "RewriteRequiredElements": [ - "all donor UI wording", - "all donor demo captions", - "all donor tutorial framing" - ], - "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", - "MatchFilter": { - "source": "met4citizen/TalkingHead", - "source_scope": "repo-backed", - "structure_template": "companion-subtitle-reference-page", - "family": "subtitle-and-viseme-sync", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded subtitle and viseme timing semantics while rewriting the surfaced cue shell in first-party HyperTwist language.", - "This target pairs with the compiled Phase 3R-E subtitle and viseme reference bundle." - ] - }, - { - "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-avatar-reference-page-embed", - "SurfaceType": "companion-avatar-reference", - "TrackTitle": "Embodied Companion and Narrated Coaching", - "ItemTitle": "Avatar-Only Embed Contract", - "IncorporationChannel": "avatar-embed-contract", - "TargetAssetFamily": "embed-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "met4citizen/TalkingHead", - "SourceLicense": "MIT", - "SourceTrackId": "companion/avatar-only-embed", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist embed target preserving bounded external-scene avatar composition, retargeting, and camera-safe companion presence from the retained TalkingHead lane." - }, - "PreserveFactualElements": [ - "external scene embedding", - "camera-safe avatar composition", - "retargeted motion and pose" - ], - "RewriteRequiredElements": [ - "all donor asset assumptions", - "all donor demo shell framing", - "all donor avatar picker UX" - ], - "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", - "MatchFilter": { - "source": "met4citizen/TalkingHead", - "source_scope": "repo-backed", - "structure_template": "companion-avatar-reference-page", - "family": "avatar-only-embedding", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded avatar-only embedding semantics while rewriting the actual companion scene shell in first-party HyperTwist terms.", - "This target pairs with the compiled Phase 3R-E avatar embed contract." - ] - }, - { - "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-gesture-reference-page-presets", - "SurfaceType": "companion-gesture-reference", - "TrackTitle": "Embodied Companion and Narrated Coaching", - "ItemTitle": "Gesture, Mood, and Pose Surface", - "IncorporationChannel": "gesture-mood-contract", - "TargetAssetFamily": "gesture-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "met4citizen/TalkingHead", - "SourceLicense": "MIT", - "SourceTrackId": "companion/gesture-mood-and-pose", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist gesture target preserving bounded coach acknowledgement, focus-callout, celebration, and mood-switching semantics from the retained TalkingHead lane." - }, - "PreserveFactualElements": [ - "gesture presets", - "mood switching", - "coach-facing pose cues" - ], - "RewriteRequiredElements": [ - "all donor animation-demo framing", - "all donor shell wording", - "all donor example choreography copy" - ], - "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", - "MatchFilter": { - "source": "met4citizen/TalkingHead", - "source_scope": "repo-backed", - "structure_template": "companion-gesture-reference-page", - "family": "gesture-mood-and-pose", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded gesture, mood, and pose semantics while rewriting the actual coach-presence shell in first-party HyperTwist language.", - "This target keeps expressive presentation inside the embodied companion lane rather than spreading it into unrelated owners." - ] - }, - { - "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-listening-reference-page-lifecycle", - "SurfaceType": "companion-listening-reference", - "TrackTitle": "Embodied Companion and Narrated Coaching", - "ItemTitle": "Streaming and Listening Lifecycle", - "IncorporationChannel": "listening-lifecycle-contract", - "TargetAssetFamily": "listening-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "met4citizen/TalkingHead", - "SourceLicense": "MIT", - "SourceTrackId": "companion/streaming-and-listening-lifecycle", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist listening target preserving bounded streaming playback, queue underrun handling, and microphone threshold-gating semantics from the retained TalkingHead lane." - }, - "PreserveFactualElements": [ - "audio stream buffering", - "queue underrun handling", - "listening thresholds", - "microphone handoff" - ], - "RewriteRequiredElements": [ - "all donor vendor tutorial text", - "all donor example shell framing", - "all donor microphone-demo wording" - ], - "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", - "MatchFilter": { - "source": "met4citizen/TalkingHead", - "source_scope": "repo-backed", - "structure_template": "companion-listening-reference-page", - "family": "streaming-and-listening-lifecycle", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded streaming and listening semantics while rewriting the surfaced audio and microphone shell in first-party HyperTwist terms.", - "This target pairs with the compiled Phase 3R-E queue lifecycle and listening contract surfaces." - ] - }, - { - "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-boundary-reference-page-adapter", - "SurfaceType": "companion-boundary-reference", - "TrackTitle": "Embodied Companion and Narrated Coaching", - "ItemTitle": "TTS and Asset Adapter Boundary", - "IncorporationChannel": "vendor-adapter-boundary", - "TargetAssetFamily": "boundary-note", - "PuzzleFamily": "Other", - "NotationProfile": "family-specific", - "SourceAttribution": { - "SourceMode": "DirectDonor", - "SourceRepo": "met4citizen/TalkingHead", - "SourceLicense": "MIT", - "SourceTrackId": "companion/tts-and-asset-adapter-boundary", - "SourceDeckId": "", - "SourceCaseId": "", - "SourceNotes": "First-party HyperTwist boundary target preserving configurable TTS, JWT, avatar, and streaming seams while keeping donor examples and sample assets explicitly outside the shipped companion lane." - }, - "PreserveFactualElements": [ - "replaceable voice-service fields", - "asset-seam boundaries", - "demo-only shell separation" - ], - "RewriteRequiredElements": [ - "all donor vendor branding", - "all donor example copy", - "all donor sample-asset assumptions" - ], - "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", - "MatchFilter": { - "source": "met4citizen/TalkingHead", - "source_scope": "repo-backed", - "structure_template": "companion-boundary-reference-page", - "family": "tts-and-asset-adapter-boundary", - "subset": null - }, - "MaterializationNotes": [ - "Preserve bounded TTS and asset-adapter semantics while rewriting the surfaced configuration shell in first-party HyperTwist language.", - "This target keeps sample avatars, vendor wiring, and donor examples subordinate to the landed companion owner." - ] - } - ] -} + "generated_at": "2026-05-13T19:00:00Z", + "reference_targets": [ + { + "ReferenceTargetId": "reference/speedcubedb-course-reference-page-speedcubedb-root", + "SurfaceType": "course-reference", + "TrackTitle": "Advanced 3x3 Systems", + "ItemTitle": "Speedcubedb Root", + "IncorporationChannel": "course-reference-supplement", + "TargetAssetFamily": "reference-page", + "PuzzleFamily": "ClassicCube", + "NotationProfile": "classic-wca", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "SpeedCubeDB", + "SourceLicense": "retained-web-content", + "SourceTrackId": "advanced-3x3-systems", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten curriculum brief for Speedcubedb Root, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "speedcubedb", + "source_scope": "httrack-retained", + "structure_template": "course-reference-page", + "family": "speedcubedb-root", + "subset": null + }, + "MaterializationNotes": [ + "Rewritten curriculum brief for Speedcubedb Root, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/speedcubedb-tool-reference-page-speedcubedb-root", + "SurfaceType": "tool-reference", + "TrackTitle": "Advanced 3x3 Systems", + "ItemTitle": "Speedcubedb Root", + "IncorporationChannel": "feature-reference", + "TargetAssetFamily": "tool-note", + "PuzzleFamily": "ClassicCube", + "NotationProfile": "classic-wca", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "SpeedCubeDB", + "SourceLicense": "retained-web-content", + "SourceTrackId": "advanced-3x3-systems", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Feature-semantics reference for Speedcubedb Root, rewritten as first-party product guidance instead of donor utility-page copy." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "speedcubedb", + "source_scope": "httrack-retained", + "structure_template": "tool-reference-page", + "family": "speedcubedb-root", + "subset": null + }, + "MaterializationNotes": [ + "Feature-semantics reference for Speedcubedb Root, rewritten as first-party product guidance instead of donor utility-page copy.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-com-course-reference-page-magic-cube-4d-solution", + "SurfaceType": "course-reference", + "TrackTitle": "Hypercubing Software Manuals", + "ItemTitle": "Magic Cube 4D Solution Notes", + "IncorporationChannel": "course-reference-supplement", + "TargetAssetFamily": "reference-page", + "PuzzleFamily": "Hypercube", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "superliminal.com", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-software-manuals", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten curriculum brief for Magic Cube 4D Solution Notes, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal.com", + "source_scope": "httrack-retained", + "structure_template": "course-reference-page", + "family": "Magic Cube 4D", + "subset": "solution" + }, + "MaterializationNotes": [ + "Rewritten curriculum brief for Magic Cube 4D Solution Notes, preserving factual method structure while replacing donor page wording with first-party HyperTwist copy.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-cube-4d", + "SurfaceType": "software-manual", + "TrackTitle": "Hypercubing Software Manuals", + "ItemTitle": "Magic Cube 4D Manual", + "IncorporationChannel": "software-manual-surface", + "TargetAssetFamily": "manual-page", + "PuzzleFamily": "Hypercube", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "superliminal.com", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-software-manuals", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten operational guide target for Magic Cube 4D Manual, preserving behavior and workflow semantics without reusing donor manual prose." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal.com", + "source_scope": "httrack-retained", + "structure_template": "software-manual-reference-page", + "family": "Magic Cube 4D", + "subset": null + }, + "MaterializationNotes": [ + "Rewritten operational guide target for Magic Cube 4D Manual, preserving behavior and workflow semantics without reusing donor manual prose.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-cube-7d", + "SurfaceType": "software-manual", + "TrackTitle": "Hypercubing Software Manuals", + "ItemTitle": "Magic Cube 7D Manual", + "IncorporationChannel": "software-manual-surface", + "TargetAssetFamily": "manual-page", + "PuzzleFamily": "Hypercube", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "superliminal.com", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-software-manuals", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten operational guide target for Magic Cube 7D Manual, preserving behavior and workflow semantics without reusing donor manual prose." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal.com", + "source_scope": "httrack-retained", + "structure_template": "software-manual-reference-page", + "family": "Magic Cube 7D", + "subset": null + }, + "MaterializationNotes": [ + "Rewritten operational guide target for Magic Cube 7D Manual, preserving behavior and workflow semantics without reusing donor manual prose.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-hyperbolic-tile", + "SurfaceType": "software-manual", + "TrackTitle": "Hypercubing Software Manuals", + "ItemTitle": "Magic Hyperbolic Tile Manual", + "IncorporationChannel": "software-manual-surface", + "TargetAssetFamily": "manual-page", + "PuzzleFamily": "Tiling", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "superliminal.com", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-software-manuals", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten operational guide target for Magic Hyperbolic Tile Manual, preserving behavior and workflow semantics without reusing donor manual prose." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal.com", + "source_scope": "httrack-retained", + "structure_template": "software-manual-reference-page", + "family": "Magic Hyperbolic Tile", + "subset": null + }, + "MaterializationNotes": [ + "Rewritten operational guide target for Magic Hyperbolic Tile Manual, preserving behavior and workflow semantics without reusing donor manual prose.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-puzzle-ultimate", + "SurfaceType": "software-manual", + "TrackTitle": "Hypercubing Software Manuals", + "ItemTitle": "Magic Puzzle Ultimate Manual", + "IncorporationChannel": "software-manual-surface", + "TargetAssetFamily": "manual-page", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "superliminal.com", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-software-manuals", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten operational guide target for Magic Puzzle Ultimate Manual, preserving behavior and workflow semantics without reusing donor manual prose." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal.com", + "source_scope": "httrack-retained", + "structure_template": "software-manual-reference-page", + "family": "Magic Puzzle Ultimate", + "subset": null + }, + "MaterializationNotes": [ + "Rewritten operational guide target for Magic Puzzle Ultimate Manual, preserving behavior and workflow semantics without reusing donor manual prose.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-com-software-manual-reference-page-magic-simplex-5d", + "SurfaceType": "software-manual", + "TrackTitle": "Hypercubing Software Manuals", + "ItemTitle": "Magic Simplex 5D Manual", + "IncorporationChannel": "software-manual-surface", + "TargetAssetFamily": "manual-page", + "PuzzleFamily": "Hypercube", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "superliminal.com", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-software-manuals", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Rewritten operational guide target for Magic Simplex 5D Manual, preserving behavior and workflow semantics without reusing donor manual prose." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal.com", + "source_scope": "httrack-retained", + "structure_template": "software-manual-reference-page", + "family": "Magic Simplex 5D", + "subset": null + }, + "MaterializationNotes": [ + "Rewritten operational guide target for Magic Simplex 5D Manual, preserving behavior and workflow semantics without reusing donor manual prose.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/superliminal-wiki-historical-reference-page-hypercubing-reference", + "SurfaceType": "historical-reference", + "TrackTitle": "Hypercubing Reference", + "ItemTitle": "Hypercubing Historical Reference", + "IncorporationChannel": "historical-reference-supplement", + "TargetAssetFamily": "history-note", + "PuzzleFamily": "Hypercube", + "NotationProfile": "hypercubing-standard", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "Superliminal Wiki", + "SourceLicense": "retained-web-content", + "SourceTrackId": "hypercubing-reference", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "Historical and conceptual reference lane for hypercubing context, rewritten into concise HyperTwist-native background guidance." + }, + "PreserveFactualElements": [ + "topic scope", + "page role", + "factual software or method semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional/reference prose" + ], + "ContentSourceFile": "./raw-extracts/httrack-retained-reference-pages.jsonl", + "MatchFilter": { + "source": "superliminal-wiki", + "source_scope": "httrack-retained", + "structure_template": "historical-reference-page", + "family": "hypercubing-reference", + "subset": null + }, + "MaterializationNotes": [ + "Historical and conceptual reference lane for hypercubing context, rewritten into concise HyperTwist-native background guidance.", + "Reference/manual surfaces remain rewritten first-party content targets, not copied donor pages." + ] + }, + { + "ReferenceTargetId": "reference/hypercubing-xyz-course-reference-page-progression", + "SurfaceType": "course-reference", + "TrackTitle": "Hypercubing Progression", + "ItemTitle": "Hypercubing Progression Ladder", + "IncorporationChannel": "course-reference-supplement", + "TargetAssetFamily": "reference-page", + "PuzzleFamily": "Hypercube", + "NotationProfile": "hypercubing-standard", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "Hypercubers/hypercubing.xyz", + "SourceLicense": "MIT", + "SourceTrackId": "progression", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist progression contract target preserving stage order, prerequisites, and widening boundaries from the donor progression guide." + }, + "PreserveFactualElements": [ + "stage ordering", + "prerequisite relationships", + "family branching semantics" + ], + "RewriteRequiredElements": [ + "page title", + "all instructional prose", + "all donor-specific presentation language" + ], + "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", + "MatchFilter": { + "source": "hypercubing.xyz", + "source_scope": "repo-backed", + "structure_template": "progression-reference-page", + "family": "hypercubing-progression", + "subset": null + }, + "MaterializationNotes": [ + "Preserve the donor's progression ordering and branch logic while rewriting the actual instructional surface in first-party HyperTwist language.", + "This target feeds the Phase 3R-B knowledge and curriculum lane rather than the runtime simulation lane." + ] + }, + { + "ReferenceTargetId": "reference/hypercubing-xyz-notation-reference-page-cell-turning-hypercubes", + "SurfaceType": "notation-reference", + "TrackTitle": "Hypercubing Notation", + "ItemTitle": "Cell-Turning Hypercube Notation", + "IncorporationChannel": "notation-reference-supplement", + "TargetAssetFamily": "glossary-page", + "PuzzleFamily": "Hypercube", + "NotationProfile": "hypercubing-standard", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "Hypercubers/hypercubing.xyz", + "SourceLicense": "MIT", + "SourceTrackId": "notation", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist notation reference target preserving factual cell, twist, plane-rotation, and metric semantics from the donor notation guide." + }, + "PreserveFactualElements": [ + "cell naming semantics", + "twist and rotation rules", + "metric distinctions" + ], + "RewriteRequiredElements": [ + "page title", + "all explanatory prose", + "all donor-specific examples beyond factual notation payloads" + ], + "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", + "MatchFilter": { + "source": "hypercubing.xyz", + "source_scope": "repo-backed", + "structure_template": "notation-reference-page", + "family": "cell-turning-hypercubes", + "subset": null + }, + "MaterializationNotes": [ + "Preserve factual notation grammar and cross-links while rewriting reference prose into HyperTwist-native documentation.", + "This target is paired with the compiled Phase 3R-B notation glossary contract." + ] + }, + { + "ReferenceTargetId": "reference/hypercubing-xyz-tool-reference-page-software-matrix", + "SurfaceType": "tool-reference", + "TrackTitle": "Hypercubing Software", + "ItemTitle": "Hypercubing Software Matrix", + "IncorporationChannel": "feature-reference", + "TargetAssetFamily": "tool-note", + "PuzzleFamily": "Hypercube", + "NotationProfile": "hypercubing-standard", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "Hypercubers/hypercubing.xyz", + "SourceLicense": "MIT", + "SourceTrackId": "software", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist software-comparison target preserving factual platform and capability semantics from the donor feature matrix." + }, + "PreserveFactualElements": [ + "platform coverage", + "capability taxonomy", + "program-role distinctions" + ], + "RewriteRequiredElements": [ + "page title", + "all donor prose", + "all donor presentation formatting" + ], + "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", + "MatchFilter": { + "source": "hypercubing.xyz", + "source_scope": "repo-backed", + "structure_template": "tool-reference-page", + "family": "software-matrix", + "subset": null + }, + "MaterializationNotes": [ + "Preserve factual feature, platform, and recommendation semantics while rewriting the reference surface in first-party HyperTwist terms.", + "This target supports bounded software-comparison and community-guidance surfaces, not runtime ownership." + ] + }, + { + "ReferenceTargetId": "reference/hypercubing-xyz-community-reference-page-leaderboards", + "SurfaceType": "community-reference", + "TrackTitle": "Hypercubing Leaderboards", + "ItemTitle": "Hypercubing Leaderboard Conventions", + "IncorporationChannel": "community-reference-supplement", + "TargetAssetFamily": "leaderboard-note", + "PuzzleFamily": "Hypercube", + "NotationProfile": "hypercubing-standard", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "Hypercubers/hypercubing.xyz", + "SourceLicense": "MIT", + "SourceTrackId": "leaderboards", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist leaderboard/report contract target preserving event identity, time formatting, relative-date, and solver-profile semantics from the donor community site." + }, + "PreserveFactualElements": [ + "event naming and ids", + "format semantics", + "display-rule conventions" + ], + "RewriteRequiredElements": [ + "page title", + "all donor prose", + "all donor HTML or presentation output" + ], + "ContentSourceFile": "./raw-extracts/hypercubing-xyz-reference-pages.jsonl", + "MatchFilter": { + "source": "hypercubing.xyz", + "source_scope": "repo-backed", + "structure_template": "community-reference-page", + "family": "leaderboards", + "subset": null + }, + "MaterializationNotes": [ + "Preserve factual leaderboard contracts while rewriting community-reference copy into HyperTwist-native language.", + "This target pairs with the compiled Phase 3R-B leaderboard policy and event schema." + ] + }, + { + "ReferenceTargetId": "reference/apache-echarts-analytics-reference-page-session-outcome-and-progress", + "SurfaceType": "analytics-reference", + "TrackTitle": "Training Analytics", + "ItemTitle": "Session Outcome and Progress Reporting", + "IncorporationChannel": "analytics-report-contract", + "TargetAssetFamily": "dashboard-report", + "PuzzleFamily": "ClassicCube", + "NotationProfile": "classic-wca", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "apache/echarts", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "analytics/session-outcome-balance", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist analytics contract target preserving bounded option, data-store, and outcome-reporting semantics from the retained echarts lane." + }, + "PreserveFactualElements": [ + "option and state layering", + "dataset separation", + "series-oriented outcome reporting" + ], + "RewriteRequiredElements": [ + "all donor source text", + "all donor component names", + "all donor shell assumptions" + ], + "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", + "MatchFilter": { + "source": "apache/echarts", + "source_scope": "repo-backed", + "structure_template": "analytics-report-reference-page", + "family": "session-outcome-and-progress", + "subset": null + }, + "MaterializationNotes": [ + "Preserve the donor's option and dataset separation while rewriting the report contract in first-party HyperTwist analytics language.", + "This target pairs with the compiled Phase 3R-C analytics report bundle and runtime data-view helpers." + ] + }, + { + "ReferenceTargetId": "reference/apache-echarts-report-export-reference-page-data-view-and-export", + "SurfaceType": "report-export-reference", + "TrackTitle": "Training Analytics", + "ItemTitle": "Analytics Data View and Export", + "IncorporationChannel": "report-export-contract", + "TargetAssetFamily": "export-note", + "PuzzleFamily": "ClassicCube", + "NotationProfile": "classic-wca", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "apache/echarts", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "analytics/export", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist analytics export target preserving bounded tabular data-view, image export, and SSR-ready reporting expectations from the retained echarts lane." + }, + "PreserveFactualElements": [ + "tabular data-view contract", + "image export behavior", + "SSR-ready report shell expectations" + ], + "RewriteRequiredElements": [ + "all donor UI wording", + "all donor shell framing", + "all donor implementation-specific presentation" + ], + "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", + "MatchFilter": { + "source": "apache/echarts", + "source_scope": "repo-backed", + "structure_template": "report-export-reference-page", + "family": "report-data-view-and-export", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded export and data-view semantics while rewriting the surfaced report shell and copy in first-party HyperTwist terms.", + "This target feeds the Phase 3R-C TSV data-view and accessible export layer, not a generic BI shell." + ] + }, + { + "ReferenceTargetId": "reference/apache-echarts-analytics-interaction-reference-page-timing-trend-history", + "SurfaceType": "analytics-interaction-reference", + "TrackTitle": "Training Analytics", + "ItemTitle": "Timing Trend History and Overview", + "IncorporationChannel": "analytics-interaction-contract", + "TargetAssetFamily": "interaction-note", + "PuzzleFamily": "ClassicCube", + "NotationProfile": "classic-wca", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "apache/echarts", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "analytics/timing-trend-rolling-windows", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist timing-trend interaction target preserving bounded zoom-history, thumbnail overview, and rolling-window inspection semantics from the retained echarts lane." + }, + "PreserveFactualElements": [ + "history-aware zoom interactions", + "thumbnail overview behavior", + "windowed timing-trend inspection" + ], + "RewriteRequiredElements": [ + "all donor component wording", + "all donor UI text", + "all donor chart-shell presentation" + ], + "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", + "MatchFilter": { + "source": "apache/echarts", + "source_scope": "repo-backed", + "structure_template": "analytics-interaction-reference-page", + "family": "timing-trend-history", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded history and overview semantics while rewriting the actual interaction copy and report framing in first-party HyperTwist language.", + "This target pairs with the Phase 3R-C rolling-window timing report bundle." + ] + }, + { + "ReferenceTargetId": "reference/apache-echarts-analytics-explainer-reference-page-optional-3d-sidecar", + "SurfaceType": "analytics-explainer-reference", + "TrackTitle": "Training Analytics", + "ItemTitle": "Optional 3D Analytics Sidecar", + "IncorporationChannel": "analytics-sidecar-boundary", + "TargetAssetFamily": "explainer-note", + "PuzzleFamily": "ClassicCube", + "NotationProfile": "classic-wca", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "apache/echarts", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "analytics/live-split-ladder", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist sidecar-boundary target preserving how optional richer explainers stay subordinate to the apache/echarts lane while bounded concepts from echarts-gl and zrender remain support-only." + }, + "PreserveFactualElements": [ + "optional 3D analytics sidecar boundary", + "camera and zoom helper behavior", + "subordinate 2D and GL renderer layering" + ], + "RewriteRequiredElements": [ + "all donor implementation text", + "all donor framework naming", + "all donor chart-shell presentation" + ], + "ContentSourceFile": "./raw-extracts/apache-echarts-reference-pages.jsonl", + "MatchFilter": { + "source": "apache/echarts", + "source_scope": "repo-backed", + "structure_template": "analytics-explainer-reference-page", + "family": "optional-3d-analytics-explainer", + "subset": null + }, + "MaterializationNotes": [ + "Preserve the subordinate-sidecar boundary while rewriting the actual explainer framing in first-party HyperTwist language.", + "This target keeps `ecomfe/echarts-gl` and `ecomfe/zrender` explicit as support-only beneath the landed `apache/echarts` lane." + ] + }, + { + "ReferenceTargetId": "reference/google-model-viewer-browser-viewer-reference-page-embed-contract", + "SurfaceType": "browser-viewer-reference", + "TrackTitle": "Browser Viewer and Asset QA", + "ItemTitle": "Browser Viewer Embed Contract", + "IncorporationChannel": "viewer-embed-contract", + "TargetAssetFamily": "support-widget", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "google/model-viewer", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "viewer/browser-viewer-embed", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser viewer target preserving bounded embed, camera, annotation, and readiness semantics from the retained model-viewer lane." + }, + "PreserveFactualElements": [ + "embeddable viewer lifecycle", + "camera and framing state", + "annotation and load-progress semantics" + ], + "RewriteRequiredElements": [ + "all donor docs and demo copy", + "all donor shell assumptions", + "all donor site framing" + ], + "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", + "MatchFilter": { + "source": "google/model-viewer", + "source_scope": "repo-backed", + "structure_template": "browser-viewer-reference-page", + "family": "browser-viewer-embed", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded viewer, camera, and annotation semantics while rewriting the actual support-plane viewer shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-D browser viewer embed contract and runtime access layer." + ] + }, + { + "ReferenceTargetId": "reference/google-model-viewer-browser-editor-reference-page-compact-editor", + "SurfaceType": "browser-editor-reference", + "TrackTitle": "Browser Viewer and Asset QA", + "ItemTitle": "Compact Browser Editor and Inspection", + "IncorporationChannel": "viewer-editor-contract", + "TargetAssetFamily": "editor-panel", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "google/model-viewer/packages/space-opera", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "viewer/compact-editor", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist compact editor target preserving bounded inspection, camera, hotspot, and preview-state semantics from the retained space-opera lane." + }, + "PreserveFactualElements": [ + "compact inspection state", + "camera settings behavior", + "hotspot authoring boundaries" + ], + "RewriteRequiredElements": [ + "all donor UI wording", + "all donor shell framing", + "all donor site-navigation assumptions" + ], + "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", + "MatchFilter": { + "source": "google/model-viewer", + "source_scope": "repo-backed", + "structure_template": "browser-editor-reference-page", + "family": "compact-editor-and-inspection", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded compact editor and inspection semantics while rewriting the actual shell and copy in first-party HyperTwist language.", + "This target pairs with the compiled Phase 3R-D editor contract beneath the landed browser viewer lane." + ] + }, + { + "ReferenceTargetId": "reference/google-model-viewer-browser-export-reference-page-snippet-and-export", + "SurfaceType": "browser-export-reference", + "TrackTitle": "Browser Viewer and Asset QA", + "ItemTitle": "Snippet and Export Surface", + "IncorporationChannel": "viewer-export-contract", + "TargetAssetFamily": "export-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "google/model-viewer/packages/modelviewer.dev", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "viewer/snippet-and-export", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist export target preserving bounded snippet, preview, and portable embed semantics from the retained modelviewer.dev and space-opera sidecars." + }, + "PreserveFactualElements": [ + "portable snippet generation", + "preview and export posture", + "single-source embed expectations" + ], + "RewriteRequiredElements": [ + "all donor docs copy", + "all donor example-shell framing", + "all donor tutorial wording" + ], + "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", + "MatchFilter": { + "source": "google/model-viewer", + "source_scope": "repo-backed", + "structure_template": "browser-export-reference-page", + "family": "snippet-and-export", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded snippet and export semantics while rewriting the actual support-plane export shell in first-party HyperTwist language.", + "This target keeps docs/demo infrastructure subordinate while still surfacing snippet and portable-embed value." + ] + }, + { + "ReferenceTargetId": "reference/khronos-gltf-browser-qa-reference-page-validation-and-statistics", + "SurfaceType": "asset-qa-reference", + "TrackTitle": "Browser Viewer and Asset QA", + "ItemTitle": "Asset Validation and Statistics", + "IncorporationChannel": "asset-qa-contract", + "TargetAssetFamily": "qa-checklist", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "KhronosGroup/glTF-Sample-Viewer", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "qa/asset-validation-and-statistics", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist QA target preserving bounded validator, statistics, camera export, and failure-reporting semantics from the retained Khronos viewer lane." + }, + "PreserveFactualElements": [ + "validator and statistics boundary", + "standards-aware preview state", + "camera export and capture posture" + ], + "RewriteRequiredElements": [ + "all donor shell framing", + "all donor UI wording", + "all donor product assumptions" + ], + "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", + "MatchFilter": { + "source": "KhronosGroup/glTF-Sample-Viewer", + "source_scope": "repo-backed", + "structure_template": "asset-qa-reference-page", + "family": "asset-validation-and-statistics", + "subset": null + }, + "MaterializationNotes": [ + "Preserve standards-aware validation and statistics semantics while rewriting the surfaced QA shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-D QA checks and keeps the Khronos lane subordinate to the landed viewer owner." + ] + }, + { + "ReferenceTargetId": "reference/google-model-viewer-renderer-comparison-reference-page-fidelity", + "SurfaceType": "renderer-comparison-reference", + "TrackTitle": "Browser Viewer and Asset QA", + "ItemTitle": "Renderer Comparison and Fidelity", + "IncorporationChannel": "renderer-comparison-contract", + "TargetAssetFamily": "regression-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "google/model-viewer/packages/render-fidelity-tools", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "qa/renderer-comparison-and-fidelity", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist renderer-comparison target preserving bounded golden-result, delta, and threshold semantics from the retained render-fidelity-tools lane." + }, + "PreserveFactualElements": [ + "golden-result comparison", + "delta and threshold reporting", + "renderer parity discipline" + ], + "RewriteRequiredElements": [ + "all donor workflow text", + "all donor shell framing", + "all donor docs/demo wording" + ], + "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", + "MatchFilter": { + "source": "google/model-viewer", + "source_scope": "repo-backed", + "structure_template": "renderer-comparison-reference-page", + "family": "renderer-comparison-and-fidelity", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded renderer-regression semantics while rewriting the surfaced comparison shell in first-party HyperTwist language.", + "This target keeps render-fidelity-tools subordinate to the landed viewer lane and the Khronos reference renderer." + ] + }, + { + "ReferenceTargetId": "reference/google-model-viewer-docs-boundary-reference-page-demo-separation", + "SurfaceType": "docs-boundary-reference", + "TrackTitle": "Browser Viewer and Asset QA", + "ItemTitle": "Docs and Demo Separation Boundary", + "IncorporationChannel": "docs-demo-boundary", + "TargetAssetFamily": "docs-boundary-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "google/model-viewer/packages/modelviewer.dev", + "SourceLicense": "Apache-2.0", + "SourceTrackId": "viewer/docs-demo-separation", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist boundary target preserving snippet-to-demo infrastructure insights while keeping docs and demo shells explicitly outside the shippable viewer lane." + }, + "PreserveFactualElements": [ + "snippet-to-demo stamping", + "interactive docs support patterns", + "demo-only shell boundaries" + ], + "RewriteRequiredElements": [ + "all donor docs copy", + "all donor navigation framing", + "all donor example-site assumptions" + ], + "ContentSourceFile": "./raw-extracts/google-model-viewer-reference-pages.jsonl", + "MatchFilter": { + "source": "google/model-viewer", + "source_scope": "repo-backed", + "structure_template": "docs-boundary-reference-page", + "family": "docs-demo-separation", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded docs/demo separation semantics while rewriting the actual support copy and shell in first-party HyperTwist language.", + "This target keeps modelviewer.dev explicitly subordinate to the landed browser viewer lane." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-reference-page-narration", + "SurfaceType": "companion-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Embodied Companion Narration", + "IncorporationChannel": "narration-contract", + "TargetAssetFamily": "companion-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/narration-contract", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist narration target preserving queued coach speech, subtitle timing, viseme alignment, and gesture-aware companion presentation from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "queued speech lifecycle", + "subtitle timing", + "viseme alignment", + "gesture and mood cues" + ], + "RewriteRequiredElements": [ + "all donor example-shell framing", + "all donor vendor-specific copy", + "all donor avatar-demo wording" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "embodied-companion-reference-page", + "family": "embodied-companion-narration", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded coach narration semantics while rewriting the actual companion shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-E narration contract and runtime access layer." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-subtitle-reference-page-sync", + "SurfaceType": "companion-subtitle-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Subtitle and Viseme Synchronization", + "IncorporationChannel": "subtitle-sync-contract", + "TargetAssetFamily": "subtitle-checklist", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/subtitle-and-viseme-sync", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist subtitle target preserving bounded caption timing, marker sync, and viseme-envelope behavior from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "word-level subtitle cues", + "marker sync", + "blendshape viseme envelopes" + ], + "RewriteRequiredElements": [ + "all donor UI wording", + "all donor demo captions", + "all donor tutorial framing" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-subtitle-reference-page", + "family": "subtitle-and-viseme-sync", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded subtitle and viseme timing semantics while rewriting the surfaced cue shell in first-party HyperTwist language.", + "This target pairs with the compiled Phase 3R-E subtitle and viseme reference bundle." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-avatar-reference-page-embed", + "SurfaceType": "companion-avatar-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Avatar-Only Embed Contract", + "IncorporationChannel": "avatar-embed-contract", + "TargetAssetFamily": "embed-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/avatar-only-embed", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist embed target preserving bounded external-scene avatar composition, retargeting, and camera-safe companion presence from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "external scene embedding", + "camera-safe avatar composition", + "retargeted motion and pose" + ], + "RewriteRequiredElements": [ + "all donor asset assumptions", + "all donor demo shell framing", + "all donor avatar picker UX" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-avatar-reference-page", + "family": "avatar-only-embedding", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded avatar-only embedding semantics while rewriting the actual companion scene shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-E avatar embed contract." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-gesture-reference-page-presets", + "SurfaceType": "companion-gesture-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Gesture, Mood, and Pose Surface", + "IncorporationChannel": "gesture-mood-contract", + "TargetAssetFamily": "gesture-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/gesture-mood-and-pose", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist gesture target preserving bounded coach acknowledgement, focus-callout, celebration, and mood-switching semantics from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "gesture presets", + "mood switching", + "coach-facing pose cues" + ], + "RewriteRequiredElements": [ + "all donor animation-demo framing", + "all donor shell wording", + "all donor example choreography copy" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-gesture-reference-page", + "family": "gesture-mood-and-pose", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded gesture, mood, and pose semantics while rewriting the actual coach-presence shell in first-party HyperTwist language.", + "This target keeps expressive presentation inside the embodied companion lane rather than spreading it into unrelated owners." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-listening-reference-page-lifecycle", + "SurfaceType": "companion-listening-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Streaming and Listening Lifecycle", + "IncorporationChannel": "listening-lifecycle-contract", + "TargetAssetFamily": "listening-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/streaming-and-listening-lifecycle", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist listening target preserving bounded streaming playback, queue underrun handling, and microphone threshold-gating semantics from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "audio stream buffering", + "queue underrun handling", + "listening thresholds", + "microphone handoff" + ], + "RewriteRequiredElements": [ + "all donor vendor tutorial text", + "all donor example shell framing", + "all donor microphone-demo wording" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-listening-reference-page", + "family": "streaming-and-listening-lifecycle", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded streaming and listening semantics while rewriting the surfaced audio and microphone shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-E queue lifecycle and listening contract surfaces." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-boundary-reference-page-adapter", + "SurfaceType": "companion-boundary-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "TTS and Asset Adapter Boundary", + "IncorporationChannel": "vendor-adapter-boundary", + "TargetAssetFamily": "boundary-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/tts-and-asset-adapter-boundary", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist boundary target preserving configurable TTS, JWT, avatar, and streaming seams while keeping donor examples and sample assets explicitly outside the shipped companion lane." + }, + "PreserveFactualElements": [ + "replaceable voice-service fields", + "asset-seam boundaries", + "demo-only shell separation" + ], + "RewriteRequiredElements": [ + "all donor vendor branding", + "all donor example copy", + "all donor sample-asset assumptions" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-boundary-reference-page", + "family": "tts-and-asset-adapter-boundary", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded TTS and asset-adapter semantics while rewriting the surfaced configuration shell in first-party HyperTwist language.", + "This target keeps sample avatars, vendor wiring, and donor examples subordinate to the landed companion owner." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-scene-reference-page-stack", + "SurfaceType": "browser-spatial-scene-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "Browser Spatial Scene and Renderer Contract", + "IncorporationChannel": "browser-spatial-scene-contract", + "TargetAssetFamily": "scene-contract-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "mrdoob/three.js", + "SourceLicense": "MIT", + "SourceTrackId": "spatial/scene-substrate", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser spatial scene target preserving bounded three.js and react-three-fiber renderer, camera, frameloop, and WebXR-manager semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "scene and renderer lifecycle", + "camera and raycaster binding", + "frameloop invalidation", + "WebXR manager integration" + ], + "RewriteRequiredElements": [ + "all donor editor shell framing", + "all donor docs or demo wording", + "all donor example chrome" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "mrdoob/three.js", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-scene-reference-page", + "family": "browser-spatial-scene-substrate", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded browser scene and renderer semantics while rewriting the surfaced integration contract in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-F browser spatial scene contract and runtime access layer." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-react-reference-page-renderer", + "SurfaceType": "browser-spatial-react-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "React Scene Renderer and Event Bridge", + "IncorporationChannel": "browser-spatial-react-contract", + "TargetAssetFamily": "renderer-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "pmndrs/react-three-fiber", + "SourceLicense": "MIT", + "SourceTrackId": "spatial/react-renderer", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser spatial renderer target preserving bounded React canvas-root, event-manager, and camera-store bridge semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "canvas root configuration", + "event-manager bridge", + "pointer and raycaster routing", + "camera or store lifecycle" + ], + "RewriteRequiredElements": [ + "all donor docs or demo wording", + "all donor example framing", + "all donor package-marketing copy" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "pmndrs/react-three-fiber", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-react-reference-page", + "family": "browser-spatial-react-renderer", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded React renderer semantics while rewriting the surfaced browser spatial shell in first-party HyperTwist language.", + "This target pairs with the compiled Phase 3R-F browser spatial scene contract." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-xr-reference-page-session", + "SurfaceType": "browser-spatial-xr-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "Browser XR Session and Immersive Interaction Contract", + "IncorporationChannel": "browser-spatial-xr-contract", + "TargetAssetFamily": "xr-contract-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "pmndrs/xr", + "SourceLicense": "MIT", + "SourceTrackId": "spatial/xr-session-store", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser XR target preserving bounded session-store, controller or hand input, pointer-routing, and immersive interaction semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "XR store lifecycle", + "controller, hand, and gaze inputs", + "session visibility and origin management", + "pointer routing and immersive interaction" + ], + "RewriteRequiredElements": [ + "all donor showroom framing", + "all donor docs wording", + "all donor sample-app chrome" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "pmndrs/xr", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-xr-reference-page", + "family": "browser-spatial-xr-session", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded browser XR semantics while rewriting the immersive-support shell in first-party HyperTwist language.", + "This target pairs with the compiled Phase 3R-F XR session contract and runtime access layer." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-ui-reference-page-panels", + "SurfaceType": "browser-spatial-ui-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "Browser Spatial UI and World-Anchored Controls", + "IncorporationChannel": "browser-spatial-ui-contract", + "TargetAssetFamily": "spatial-ui-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "pmndrs/uikit", + "SourceLicense": "MIT", + "SourceTrackId": "spatial/world-anchored-ui", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser spatial UI target preserving bounded instanced-panel, text-input, and world-anchored control semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "instanced panels", + "world-anchored control families", + "text and input surfaces", + "themeable spatial UI kits" + ], + "RewriteRequiredElements": [ + "all donor dashboard framing", + "all donor example wording", + "all donor theme-kit copy" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "pmndrs/uikit", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-ui-reference-page", + "family": "browser-spatial-ui", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded spatial UI semantics while rewriting the surfaced world-anchored control shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-F spatial UI contract." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-effect-reference-page-boundary", + "SurfaceType": "browser-spatial-effect-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "Browser Post-Processing and Effect Boundary", + "IncorporationChannel": "browser-spatial-effect-boundary", + "TargetAssetFamily": "effect-boundary-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "pmndrs/postprocessing", + "SourceLicense": "Zlib", + "SourceTrackId": "spatial/effect-composer", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser effect target preserving bounded effect-composer, pass-orchestration, and render-priority semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "effect composer lifecycle", + "pass ordering and grouping", + "depth and normal pass orchestration", + "render-priority driven effect routing" + ], + "RewriteRequiredElements": [ + "all donor effect-gallery wording", + "all donor docs framing", + "all donor demo-shell assumptions" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "pmndrs/postprocessing", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-effect-reference-page", + "family": "browser-spatial-effects", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded post-processing semantics while rewriting the surfaced effect policy in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-F effect boundary." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-helper-reference-page-stack", + "SurfaceType": "browser-spatial-helper-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "Browser Spatial Helper and Utility Stack", + "IncorporationChannel": "browser-spatial-helper-stack", + "TargetAssetFamily": "helper-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "pmndrs/drei", + "SourceLicense": "MIT", + "SourceTrackId": "spatial/helper-primitives", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist helper target preserving bounded view, HTML overlay, controller-helper, and motion-friendly math semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "scissored view embedding", + "HTML overlay bridging", + "XR controller model helpers", + "damping and easing helpers" + ], + "RewriteRequiredElements": [ + "all donor helper-demo wording", + "all donor example framing", + "all donor sample-shell assumptions" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "pmndrs/drei", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-helper-reference-page", + "family": "browser-spatial-helpers", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded helper and utility semantics while rewriting the surfaced integration shell in first-party HyperTwist terms.", + "This target keeps helper abstractions subordinate to the landed 3R-F spatial support lane." + ] + }, + { + "ReferenceTargetId": "reference/browser-spatial-state-reference-page-stack", + "SurfaceType": "browser-spatial-state-reference", + "TrackTitle": "Browser 3D and XR Support", + "ItemTitle": "Browser Spatial State, Gesture, and Motion Contract", + "IncorporationChannel": "browser-spatial-state-motion-contract", + "TargetAssetFamily": "state-motion-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "pmndrs/zustand", + "SourceLicense": "MIT", + "SourceTrackId": "spatial/state-gesture-motion", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist browser state target preserving bounded store, gesture-routing, spring-motion, and parameter-control semantics from the retained 3R-F lane." + }, + "PreserveFactualElements": [ + "lightweight store lifecycle", + "gesture composition and routing", + "spring-based motion and interpolation", + "schema-driven parameter controls" + ], + "RewriteRequiredElements": [ + "all donor playground wording", + "all donor demo framing", + "all donor package-marketing copy" + ], + "ContentSourceFile": "./raw-extracts/browser-spatial-support-reference-pages.jsonl", + "MatchFilter": { + "source": "pmndrs/zustand", + "source_scope": "repo-backed", + "structure_template": "browser-spatial-state-reference-page", + "family": "browser-spatial-state-motion", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded state, gesture, and motion semantics while rewriting the surfaced control shell in first-party HyperTwist language.", + "This target pairs with the compiled Phase 3R-F state and motion contract." + ] + } + ] +} \ No newline at end of file diff --git a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl new file mode 100644 index 0000000..b00f06c --- /dev/null +++ b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl @@ -0,0 +1,7 @@ +{"source":"mrdoob/three.js","source_scope":"repo-backed","family":"browser-spatial-scene-substrate","subset":"scene","page_id":"browser-spatial-scene-stack","page_title":"Browser Spatial Scene and Renderer Contract","surface_type":"browser-spatial-scene-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\mrdoob\\three.js\\src\\renderers\\webxr\\WebXRManager.js","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\react-three-fiber\\packages\\fiber\\src\\core\\renderer.tsx"],"preserve_factual_elements":["scene and renderer lifecycle","camera and raycaster binding","frameloop invalidation","WebXR manager integration"],"notes":"Source-backed scene contract target for first-party HyperTwist browser spatial roots, renderer lifecycle, camera binding, and frameloop control without promoting donor editor shells."} +{"source":"pmndrs/react-three-fiber","source_scope":"repo-backed","family":"browser-spatial-react-renderer","subset":"react-renderer","page_id":"browser-spatial-react-renderer","page_title":"React Scene Renderer and Event Bridge","surface_type":"browser-spatial-react-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\react-three-fiber\\packages\\fiber\\src\\core\\renderer.tsx","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\react-three-fiber\\packages\\fiber\\src\\core\\events.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\react-three-fiber\\packages\\fiber\\src\\web\\Canvas.tsx"],"preserve_factual_elements":["canvas root configuration","event-manager bridge","pointer and raycaster routing","camera/store lifecycle"],"notes":"Source-backed renderer target for first-party HyperTwist React-side browser spatial surfaces, preserving root configuration, event routing, and camera-store bridging semantics."} +{"source":"pmndrs/xr","source_scope":"repo-backed","family":"browser-spatial-xr-session","subset":"xr","page_id":"browser-spatial-xr-session-stack","page_title":"Browser XR Session and Immersive Interaction Contract","surface_type":"browser-spatial-xr-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\xr\\packages\\react\\xr\\src\\xr.tsx","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\xr\\packages\\xr\\src\\store.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\xr\\packages\\pointer-events\\src\\pointer\\index.ts"],"preserve_factual_elements":["XR store lifecycle","controller, hand, and gaze inputs","session visibility and origin management","pointer routing and immersive interaction"],"notes":"Source-backed XR contract target for first-party HyperTwist browser immersive sessions, controller or hand state, pointer routing, and session lifecycle without promoting donor showroom behavior."} +{"source":"pmndrs/uikit","source_scope":"repo-backed","family":"browser-spatial-ui","subset":"spatial-ui","page_id":"browser-spatial-ui-stack","page_title":"Browser Spatial UI and World-Anchored Controls","surface_type":"browser-spatial-ui-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\uikit\\packages\\uikit\\src\\panel\\index.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\uikit\\packages\\uikit\\src\\components\\input.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\uikit\\packages\\kits\\default\\core\\src\\index.ts"],"preserve_factual_elements":["instanced panels","world-anchored control families","text and input surfaces","themeable spatial UI kits"],"notes":"Source-backed spatial UI target for first-party HyperTwist world-anchored panels, controls, and text-input surfaces beneath the browser spatial support lane."} +{"source":"pmndrs/postprocessing","source_scope":"repo-backed","family":"browser-spatial-effects","subset":"effects","page_id":"browser-spatial-effect-boundary","page_title":"Browser Post-Processing and Effect Boundary","surface_type":"browser-spatial-effect-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\postprocessing\\src\\core\\EffectComposer.js","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\react-postprocessing\\src\\EffectComposer.tsx"],"preserve_factual_elements":["effect composer lifecycle","pass ordering and grouping","depth and normal pass orchestration","render-priority driven effect routing"],"notes":"Source-backed effect-boundary target for first-party HyperTwist browser spatial effects, preserving composer, pass, and render-priority seams while keeping effect policy first-party."} +{"source":"pmndrs/drei","source_scope":"repo-backed","family":"browser-spatial-helpers","subset":"helpers","page_id":"browser-spatial-helper-stack","page_title":"Browser Spatial Helper and Utility Stack","surface_type":"browser-spatial-helper-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\drei\\src\\web\\View.tsx","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\drei\\src\\web\\Html.tsx","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\three-stdlib\\src\\webxr\\XRControllerModelFactory.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\maath\\packages\\maath\\src\\easing.ts"],"preserve_factual_elements":["scissored view embedding","HTML overlay bridging","XR controller model helpers","damping and easing helpers"],"notes":"Source-backed helper target for first-party HyperTwist browser spatial utilities, preserving overlay, controller-helper, and motion-friendly math seams without promoting generic donor shells."} +{"source":"pmndrs/zustand","source_scope":"repo-backed","family":"browser-spatial-state-motion","subset":"state-motion","page_id":"browser-spatial-state-motion-stack","page_title":"Browser Spatial State, Gesture, and Motion Contract","surface_type":"browser-spatial-state-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\zustand\\src\\vanilla.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\use-gesture\\packages\\react\\src\\useGesture.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\react-spring\\packages\\core\\src\\hooks\\useSpring.ts","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\pmndrs\\leva\\packages\\leva\\src\\useControls.ts"],"preserve_factual_elements":["lightweight store lifecycle","gesture composition and routing","spring-based motion and interpolation","schema-driven parameter controls"],"notes":"Source-backed state and motion target for first-party HyperTwist browser spatial tools, preserving store, gesture, spring, and parameter-panel seams while keeping product-wide state ownership first-party."} diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp index 2dfe72a..738d0de 100644 --- a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp @@ -475,6 +475,12 @@ UHyperTwistTrainingRuntimeLibrary::GetBundledEmbodiedCompanionReferenceBundle() return UHyperTwistTrainingCompanionLibrary::BuildBundledEmbodiedCompanionReferenceBundle(); } +FHyperTwistTrainingSpatialReferenceBundle +UHyperTwistTrainingRuntimeLibrary::GetBundledBrowserSpatialReferenceBundle() +{ + return UHyperTwistTrainingSpatialLibrary::BuildBundledBrowserSpatialReferenceBundle(); +} + bool UHyperTwistTrainingRuntimeLibrary::TryGetLatestGeneratedModeLaunchRequestForDeck( UObject* WorldContextObject, const FString& UserId, @@ -716,6 +722,73 @@ FString UHyperTwistTrainingRuntimeLibrary::BuildBundledEmbodiedCompanionSubtitle ); } +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledBrowserSpatialSceneContract( + const FString& ContractId, + FHyperTwistTrainingSpatialSceneContract& OutContract +) +{ + return UHyperTwistTrainingSpatialLibrary::TryGetSceneContractById( + GetBundledBrowserSpatialReferenceBundle(), + ContractId, + OutContract + ); +} + +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledBrowserSpatialXrSessionContract( + const FString& ContractId, + FHyperTwistTrainingSpatialXrSessionContract& OutContract +) +{ + return UHyperTwistTrainingSpatialLibrary::TryGetXrSessionContractById( + GetBundledBrowserSpatialReferenceBundle(), + ContractId, + OutContract + ); +} + +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledBrowserSpatialUiContract( + const FString& ContractId, + FHyperTwistTrainingSpatialUiContract& OutContract +) +{ + return UHyperTwistTrainingSpatialLibrary::TryGetSpatialUiContractById( + GetBundledBrowserSpatialReferenceBundle(), + ContractId, + OutContract + ); +} + +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledBrowserSpatialEffectBoundary( + const FString& BoundaryId, + FHyperTwistTrainingSpatialEffectBoundary& OutBoundary +) +{ + return UHyperTwistTrainingSpatialLibrary::TryGetEffectBoundaryById( + GetBundledBrowserSpatialReferenceBundle(), + BoundaryId, + OutBoundary + ); +} + +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledBrowserSpatialStateMotionContract( + const FString& ContractId, + FHyperTwistTrainingSpatialStateMotionContract& OutContract +) +{ + return UHyperTwistTrainingSpatialLibrary::TryGetStateMotionContractById( + GetBundledBrowserSpatialReferenceBundle(), + ContractId, + OutContract + ); +} + +FString UHyperTwistTrainingRuntimeLibrary::BuildBundledBrowserSpatialPackageChecklistTsv() +{ + return UHyperTwistTrainingSpatialLibrary::BuildPackageChecklistTsv( + GetBundledBrowserSpatialReferenceBundle() + ); +} + FHyperTwistTrainingLearnerDeckStateSummary UHyperTwistTrainingRuntimeLibrary::GetActiveTrainingLearnerDeckStateSummary(UObject* WorldContextObject) { if (UHyperTwistTrainingSubsystem* TrainingSubsystem = GetTrainingSubsystem(WorldContextObject)) diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp new file mode 100644 index 0000000..c63d19a --- /dev/null +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp @@ -0,0 +1,841 @@ +#include "HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h" + +namespace HyperTwistTrainingSpatialLibraryInternal +{ + FHyperTwistTrainingSourceAttribution MakeAttribution( + const FString& SourceRepo, + const FString& TrackId, + const FString& Notes, + const FString& SourceLicense = TEXT("MIT") + ) + { + FHyperTwistTrainingSourceAttribution Attribution; + Attribution.SourceMode = EHyperTwistTrainingSourceMode::DirectDonor; + Attribution.SourceRepo = SourceRepo; + Attribution.SourceLicense = SourceLicense; + Attribution.SourceTrackId = TrackId; + Attribution.SourceNotes = Notes; + return Attribution; + } + + FHyperTwistTrainingSpatialPackageReference MakePackageReference( + const FString& PackageId, + const FString& Label, + const FString& OwnershipRole, + const FString& Summary, + const TArray& RetainedSurfaceTags, + const TArray& ExplicitExclusions, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingSpatialPackageReference Reference; + Reference.PackageId = PackageId; + Reference.Label = Label; + Reference.OwnershipRole = OwnershipRole; + Reference.Summary = Summary; + Reference.RetainedSurfaceTags = RetainedSurfaceTags; + Reference.ExplicitExclusions = ExplicitExclusions; + Reference.SourceAttribution = SourceAttribution; + return Reference; + } + + void AppendJoined(FString& OutText, const TArray& Values) + { + for (int32 Index = 0; Index < Values.Num(); ++Index) + { + if (Index > 0) + { + OutText.Append(TEXT(", ")); + } + + OutText.Append(Values[Index]); + } + } +} + +FHyperTwistTrainingSpatialReferenceBundle +UHyperTwistTrainingSpatialLibrary::BuildBundledBrowserSpatialReferenceBundle() +{ + using namespace HyperTwistTrainingSpatialLibraryInternal; + + FHyperTwistTrainingSpatialReferenceBundle Bundle; + Bundle.ReferenceUtc = TEXT("2026-05-13T00:00:00Z"); + Bundle.PrimarySceneContractId = TEXT("browser-spatial-scene-stack"); + Bundle.PrimaryXrSessionContractId = TEXT("browser-spatial-xr-session-stack"); + Bundle.PrimarySpatialUiContractId = TEXT("browser-spatial-ui-stack"); + Bundle.PrimaryEffectBoundaryId = TEXT("browser-spatial-effect-boundary"); + Bundle.PrimaryStateMotionContractId = TEXT("browser-spatial-state-motion-stack"); + + Bundle.PackageReferences = + { + MakePackageReference( + TEXT("package/three-js"), + TEXT("three.js"), + TEXT("scene-substrate-anchor"), + TEXT("Commodity browser scene, renderer, camera, and WebXR substrate for the retained browser spatial lane."), + { + TEXT("scene graph"), + TEXT("camera and renderer lifecycle"), + TEXT("WebXR manager"), + TEXT("controller spaces") + }, + { + TEXT("editor shell ownership"), + TEXT("product runtime ownership"), + TEXT("browser-first app shell") + }, + MakeAttribution( + TEXT("mrdoob/three.js"), + TEXT("browser-spatial/three-js"), + TEXT("Preserves browser scene, renderer, and WebXR device-management seams from Three.Core.js and WebXRManager.js.") + ) + ), + MakePackageReference( + TEXT("package/react-three-fiber"), + TEXT("react-three-fiber"), + TEXT("react-renderer-anchor"), + TEXT("React-side renderer substrate over three.js for canvas roots, frameloop control, and event-manager bridging."), + { + TEXT("createRoot"), + TEXT("frameloop invalidation"), + TEXT("raycaster/event bridge"), + TEXT("camera/store lifecycle") + }, + { + TEXT("product shell ownership"), + TEXT("generic app-state ownership"), + TEXT("browser-only architecture control") + }, + MakeAttribution( + TEXT("pmndrs/react-three-fiber"), + TEXT("browser-spatial/react-three-fiber"), + TEXT("Preserves canvas-root configuration, renderer/store lifecycle, and pointer-event bridging from the retained fiber renderer.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-xr"), + TEXT("pmndrs/xr"), + TEXT("xr-session-anchor"), + TEXT("Browser XR session, controller, hand, gaze, pointer, and session-store anchor for immersive support-plane work."), + { + TEXT("XR store"), + TEXT("controller and hand state"), + TEXT("gaze and screen input"), + TEXT("pointer routing"), + TEXT("session visibility") + }, + { + TEXT("gameplay ownership"), + TEXT("simulation ownership"), + TEXT("generic VR showroom shell") + }, + MakeAttribution( + TEXT("pmndrs/xr"), + TEXT("browser-spatial/pmndrs-xr"), + TEXT("Preserves XR store, session lifecycle, pointer-routing, and immersive interaction seams from the retained XR lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-uikit"), + TEXT("pmndrs/uikit"), + TEXT("spatial-ui-support"), + TEXT("World-anchored panel, text, and control-kit substrate for browser-side spatial UI surfaces."), + { + TEXT("instanced panels"), + TEXT("text/input components"), + TEXT("theme kits"), + TEXT("world-anchored controls") + }, + { + TEXT("visual-brand ownership"), + TEXT("demo dashboard shell"), + TEXT("global design-system ownership") + }, + MakeAttribution( + TEXT("pmndrs/uikit"), + TEXT("browser-spatial/pmndrs-uikit"), + TEXT("Preserves instanced-panel, text-input, and world-anchored spatial UI seams from the retained uikit lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-postprocessing"), + TEXT("pmndrs/postprocessing"), + TEXT("effect-substrate-support"), + TEXT("Effect-composer substrate for render passes, depth copies, multisampling, and bounded post effects."), + { + TEXT("effect composer"), + TEXT("double-buffer render targets"), + TEXT("depth/normal pass orchestration"), + TEXT("pass ordering") + }, + { + TEXT("scene ownership"), + TEXT("browser viewer ownership"), + TEXT("demo effect gallery ownership") + }, + MakeAttribution( + TEXT("pmndrs/postprocessing"), + TEXT("browser-spatial/postprocessing"), + TEXT("Preserves effect-composer lifecycle, pass ordering, and buffer-management seams from the retained postprocessing lane."), + TEXT("Zlib") + ) + ), + MakePackageReference( + TEXT("package/react-postprocessing"), + TEXT("react-postprocessing"), + TEXT("react-effect-wrapper-support"), + TEXT("React wrapper layer above postprocessing for declarative pass grouping and render-priority control."), + { + TEXT("composer context"), + TEXT("render priority"), + TEXT("declarative pass grouping"), + TEXT("normal-pass gating") + }, + { + TEXT("scene ownership"), + TEXT("browser shell ownership"), + TEXT("effect showcase ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-postprocessing"), + TEXT("browser-spatial/react-postprocessing"), + TEXT("Preserves React-side effect-composer orchestration, pass grouping, and render-priority seams above postprocessing.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-drei"), + TEXT("pmndrs/drei"), + TEXT("helper-abstraction-support"), + TEXT("High-leverage helper and abstraction layer above react-three-fiber for overlays, views, and spatial helper primitives."), + { + TEXT("View scissoring"), + TEXT("Html overlay bridge"), + TEXT("text and helper primitives"), + TEXT("pivot/view helpers") + }, + { + TEXT("scene-substrate ownership"), + TEXT("runtime ownership"), + TEXT("product shell ownership") + }, + MakeAttribution( + TEXT("pmndrs/drei"), + TEXT("browser-spatial/drei"), + TEXT("Preserves view scissoring, HTML overlay, and helper abstraction seams from the retained drei lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-three-stdlib"), + TEXT("pmndrs/three-stdlib"), + TEXT("shared-utility-support"), + TEXT("Shared browser-side utility substrate for WebXR helpers, controller models, exporters, loaders, and geometry utilities."), + { + TEXT("XR controller models"), + TEXT("hand models"), + TEXT("geometry utilities"), + TEXT("loader/exporter helpers") + }, + { + TEXT("scene ownership"), + TEXT("gameplay ownership"), + TEXT("app-shell ownership") + }, + MakeAttribution( + TEXT("pmndrs/three-stdlib"), + TEXT("browser-spatial/three-stdlib"), + TEXT("Preserves WebXR helper, controller-model, and geometry-utility seams from the retained three-stdlib lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-maath"), + TEXT("pmndrs/maath"), + TEXT("math-helper-support"), + TEXT("Math and easing helper substrate for damping, interpolation, geometry utilities, and motion-friendly spatial helpers."), + { + TEXT("damping"), + TEXT("easing"), + TEXT("geometry helpers"), + TEXT("motion-friendly math") + }, + { + TEXT("animation-system ownership"), + TEXT("scene ownership"), + TEXT("app-shell ownership") + }, + MakeAttribution( + TEXT("pmndrs/maath"), + TEXT("browser-spatial/maath"), + TEXT("Preserves damping, easing, and geometry-helper seams from the retained maath lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-zustand"), + TEXT("pmndrs/zustand"), + TEXT("state-substrate-support"), + TEXT("Lightweight store, subscription, selector, and middleware substrate beneath browser-side spatial tools."), + { + TEXT("vanilla store"), + TEXT("subscriptions"), + TEXT("selector equality"), + TEXT("persist/devtools middleware") + }, + { + TEXT("global product-state ownership"), + TEXT("server-state ownership"), + TEXT("runtime-foundation ownership") + }, + MakeAttribution( + TEXT("pmndrs/zustand"), + TEXT("browser-spatial/zustand"), + TEXT("Preserves lightweight store creation, selector subscription, and middleware seams from the retained zustand lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-leva"), + TEXT("pmndrs/leva"), + TEXT("parameter-ui-support"), + TEXT("Schema-driven control-panel and parameter-UI sidecar for browser-side spatial tools and debug surfaces."), + { + TEXT("schema-driven controls"), + TEXT("headless store bridge"), + TEXT("plugin inputs"), + TEXT("parameter panels") + }, + { + TEXT("primary product UI ownership"), + TEXT("theme ownership"), + TEXT("persistent dashboard shell") + }, + MakeAttribution( + TEXT("pmndrs/leva"), + TEXT("browser-spatial/leva"), + TEXT("Preserves schema-driven controls, store-backed parameter panels, and plugin-extensible input seams from the retained leva lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-use-gesture"), + TEXT("pmndrs/use-gesture"), + TEXT("gesture-router-support"), + TEXT("Browser-side gesture-routing substrate for drag, pinch, hover, move, scroll, and wheel interaction."), + { + TEXT("drag"), + TEXT("pinch"), + TEXT("hover"), + TEXT("move"), + TEXT("scroll/wheel") + }, + { + TEXT("product input-policy ownership"), + TEXT("XR session ownership"), + TEXT("scene ownership") + }, + MakeAttribution( + TEXT("pmndrs/use-gesture"), + TEXT("browser-spatial/use-gesture"), + TEXT("Preserves drag, pinch, hover, move, scroll, and multi-gesture routing seams from the retained use-gesture lane.") + ) + ), + MakePackageReference( + TEXT("package/pmndrs-react-spring"), + TEXT("pmndrs/react-spring"), + TEXT("motion-substrate-support"), + TEXT("Motion and interpolation substrate for browser-side spatial transitions, springs, and frame-synchronized movement."), + { + TEXT("useSpring hooks"), + TEXT("controllers and spring values"), + TEXT("interpolation"), + TEXT("frame-scheduled motion") + }, + { + TEXT("scene ownership"), + TEXT("app-shell ownership"), + TEXT("global animation branding") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring"), + TEXT("Preserves spring-hook, interpolation, and frame-scheduled motion seams from the retained react-spring lane.") + ) + ), + MakePackageReference( + TEXT("package/react-spring-core"), + TEXT("@react-spring/core"), + TEXT("folded-motion-package"), + TEXT("Core controller, animation-config, interpolation, and scheduling logic folded beneath the retained react-spring lane."), + { + TEXT("Controller"), + TEXT("AnimationConfig"), + TEXT("Interpolation"), + TEXT("hook implementations") + }, + { + TEXT("standalone product ownership"), + TEXT("scene ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring-core"), + TEXT("Preserves controller, spring-value, interpolation, and hook-core seams from @react-spring/core.") + ) + ), + MakePackageReference( + TEXT("package/react-spring-animated"), + TEXT("@react-spring/animated"), + TEXT("folded-motion-package"), + TEXT("Animated host, animated value, and withAnimated helper package folded beneath the retained react-spring lane."), + { + TEXT("animated values"), + TEXT("animated strings"), + TEXT("animated host"), + TEXT("withAnimated") + }, + { + TEXT("standalone product ownership"), + TEXT("scene ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring-animated"), + TEXT("Preserves animated host and animated-value seams from @react-spring/animated.") + ) + ), + MakePackageReference( + TEXT("package/react-spring-shared"), + TEXT("@react-spring/shared"), + TEXT("folded-motion-package"), + TEXT("Shared interpolation, easing, reduced-motion, and global utility package folded beneath the retained react-spring lane."), + { + TEXT("interpolators"), + TEXT("easings"), + TEXT("reduced motion"), + TEXT("globals and helpers") + }, + { + TEXT("standalone product ownership"), + TEXT("scene ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring-shared"), + TEXT("Preserves interpolator, easing, and reduced-motion seams from @react-spring/shared.") + ) + ), + MakePackageReference( + TEXT("package/react-spring-types"), + TEXT("@react-spring/types"), + TEXT("folded-motion-package"), + TEXT("Type and interpolation contract package folded beneath the retained react-spring lane."), + { + TEXT("animated typing"), + TEXT("interpolation typing"), + TEXT("utility typing") + }, + { + TEXT("standalone product ownership"), + TEXT("runtime ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring-types"), + TEXT("Preserves animated and interpolation type-contract seams from @react-spring/types.") + ) + ), + MakePackageReference( + TEXT("package/react-spring-rafz"), + TEXT("@react-spring/rafz"), + TEXT("folded-motion-package"), + TEXT("Frame-loop scheduler package folded beneath the retained react-spring lane."), + { + TEXT("frame scheduling"), + TEXT("batched updates"), + TEXT("raf lifecycle") + }, + { + TEXT("standalone product ownership"), + TEXT("scene ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring-rafz"), + TEXT("Preserves frame-scheduler seams from @react-spring/rafz.") + ) + ), + MakePackageReference( + TEXT("package/react-spring-parallax"), + TEXT("@react-spring/parallax"), + TEXT("folded-motion-package"), + TEXT("Layered motion and panel-transition package folded beneath the retained react-spring lane."), + { + TEXT("parallax layers"), + TEXT("scroll-linked transitions"), + TEXT("panel motion") + }, + { + TEXT("standalone product ownership"), + TEXT("scene ownership") + }, + MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/react-spring-parallax"), + TEXT("Preserves layered motion and panel-transition seams from @react-spring/parallax.") + ) + ) + }; + + FHyperTwistTrainingSpatialSceneContract SceneContract; + SceneContract.ContractId = TEXT("browser-spatial-scene-stack"); + SceneContract.Title = TEXT("Browser spatial scene and renderer contract"); + SceneContract.Summary = TEXT("First-party browser spatial contract for scene roots, renderer lifecycle, frameloop invalidation, camera binding, event routing, and helper-portal seams without promoting donor editors or demo shells."); + SceneContract.RequiredPackageIds = + { + TEXT("package/three-js"), + TEXT("package/react-three-fiber"), + TEXT("package/pmndrs-drei"), + TEXT("package/pmndrs-three-stdlib"), + TEXT("package/pmndrs-maath") + }; + SceneContract.LifecycleStages = + { + TEXT("create canvas root"), + TEXT("configure WebGL renderer"), + TEXT("bind camera and raycaster"), + TEXT("drive frameloop invalidation"), + TEXT("host scissored views and overlays"), + TEXT("dispose helper primitives") + }; + SceneContract.EventSurfaceTags = + { + TEXT("canvas-root"), + TEXT("pointer-event bridge"), + TEXT("raycaster camera binding"), + TEXT("scissored view embedding"), + TEXT("HTML overlay bridge") + }; + SceneContract.ExplicitExclusions = + { + TEXT("donor editor shell"), + TEXT("demo documentation shell"), + TEXT("browser-first runtime ownership") + }; + SceneContract.SourceAttribution = MakeAttribution( + TEXT("mrdoob/three.js"), + TEXT("browser-spatial/scene-contract"), + TEXT("Preserves three.js renderer and WebXR camera-management seams, paired with react-three-fiber root, frameloop, and event-bridge surfaces.") + ); + Bundle.SceneContracts = {SceneContract}; + + FHyperTwistTrainingSpatialXrSessionContract XrContract; + XrContract.ContractId = TEXT("browser-spatial-xr-session-stack"); + XrContract.Title = TEXT("Browser XR session and immersive interaction contract"); + XrContract.Summary = TEXT("First-party browser XR contract for session modes, controller and hand state, gaze and screen input, pointer routing, dom overlays, and immersive interaction guards without promoting a donor showroom or gameplay shell."); + XrContract.RequiredPackageIds = + { + TEXT("package/three-js"), + TEXT("package/react-three-fiber"), + TEXT("package/pmndrs-xr"), + TEXT("package/pmndrs-three-stdlib") + }; + XrContract.SessionModes = + { + TEXT("inline"), + TEXT("immersive-vr"), + TEXT("immersive-ar") + }; + XrContract.InputSurfaceTags = + { + TEXT("controller target ray"), + TEXT("controller grip"), + TEXT("hand tracking"), + TEXT("gaze input"), + TEXT("screen input"), + TEXT("pointer routing") + }; + XrContract.InteractionSurfaceTags = + { + TEXT("session visibility"), + TEXT("origin and space management"), + TEXT("pointer combine"), + TEXT("dom overlay"), + TEXT("hit test and anchors"), + TEXT("teleport and locomotion") + }; + XrContract.ExplicitExclusions = + { + TEXT("gameplay ownership"), + TEXT("simulation ownership"), + TEXT("generic XR showroom shell") + }; + XrContract.SourceAttribution = MakeAttribution( + TEXT("pmndrs/xr"), + TEXT("browser-spatial/xr-contract"), + TEXT("Preserves XR store, session-mode, controller-input, and pointer-routing seams from the retained pmndrs/xr lane.") + ); + Bundle.XrSessionContracts = {XrContract}; + + FHyperTwistTrainingSpatialUiContract UiContract; + UiContract.ContractId = TEXT("browser-spatial-ui-stack"); + UiContract.Title = TEXT("Browser spatial UI and world-anchored controls contract"); + UiContract.Summary = TEXT("First-party spatial UI contract for world-anchored panels, parameter controls, text/input components, view overlays, and state-backed spatial control surfaces without inheriting donor dashboards or generic design-system ownership."); + UiContract.RequiredPackageIds = + { + TEXT("package/pmndrs-uikit"), + TEXT("package/pmndrs-drei"), + TEXT("package/pmndrs-zustand"), + TEXT("package/pmndrs-leva"), + TEXT("package/pmndrs-use-gesture") + }; + UiContract.ComponentFamilies = + { + TEXT("instanced panels"), + TEXT("buttons and toggles"), + TEXT("sliders and tabs"), + TEXT("text and input fields"), + TEXT("tooltips and dialogs"), + TEXT("parameter monitors") + }; + UiContract.StateSurfaceTags = + { + TEXT("world-anchored control panel"), + TEXT("schema-driven parameter state"), + TEXT("gesture-routed interactions"), + TEXT("HTML/spatial overlay bridge"), + TEXT("headless control-store bridge") + }; + UiContract.ExplicitExclusions = + { + TEXT("donor dashboard shells"), + TEXT("generic design-system ownership"), + TEXT("global product UI ownership") + }; + UiContract.SourceAttribution = MakeAttribution( + TEXT("pmndrs/uikit"), + TEXT("browser-spatial/ui-contract"), + TEXT("Preserves instanced panels, world-anchored controls, and state-backed parameter UI seams from uikit, leva, zustand, and use-gesture.") + ); + Bundle.SpatialUiContracts = {UiContract}; + + FHyperTwistTrainingSpatialEffectBoundary EffectBoundary; + EffectBoundary.BoundaryId = TEXT("browser-spatial-effect-boundary"); + EffectBoundary.Title = TEXT("Browser post-processing and effect boundary"); + EffectBoundary.Summary = TEXT("First-party effect boundary for effect-composer setup, pass grouping, depth or normal helpers, render-priority control, and HyperTwist-owned effect policy without promoting donor preset galleries."); + EffectBoundary.RequiredPackageIds = + { + TEXT("package/three-js"), + TEXT("package/react-three-fiber"), + TEXT("package/pmndrs-postprocessing"), + TEXT("package/react-postprocessing") + }; + EffectBoundary.EffectFamilies = + { + TEXT("render pass"), + TEXT("effect pass"), + TEXT("normal pass"), + TEXT("depth downsampling"), + TEXT("composer multisampling"), + TEXT("tone mapping and highlight effects") + }; + EffectBoundary.FirstPartyOwnedFields = + { + TEXT("effect enablement policy"), + TEXT("training-specific highlight semantics"), + TEXT("performance budgets"), + TEXT("export and replay parity rules") + }; + EffectBoundary.ExplicitExclusions = + { + TEXT("donor effect gallery ownership"), + TEXT("browser shell ownership"), + TEXT("scene ownership") + }; + EffectBoundary.SourceAttribution = MakeAttribution( + TEXT("pmndrs/postprocessing"), + TEXT("browser-spatial/effect-boundary"), + TEXT("Preserves effect-composer and pass-orchestration seams from postprocessing and react-postprocessing while keeping HyperTwist-specific effect policy first-party."), + TEXT("Zlib") + ); + Bundle.EffectBoundaries = {EffectBoundary}; + + FHyperTwistTrainingSpatialStateMotionContract StateMotionContract; + StateMotionContract.ContractId = TEXT("browser-spatial-state-motion-stack"); + StateMotionContract.Title = TEXT("Browser spatial state, gesture, and motion contract"); + StateMotionContract.Summary = TEXT("First-party state and motion contract for lightweight stores, selector subscriptions, gesture routing, spring-based motion, parameter panels, and helper interpolation beneath browser-side spatial tooling."); + StateMotionContract.RequiredPackageIds = + { + TEXT("package/pmndrs-zustand"), + TEXT("package/pmndrs-use-gesture"), + TEXT("package/pmndrs-react-spring"), + TEXT("package/react-spring-core"), + TEXT("package/react-spring-animated"), + TEXT("package/react-spring-shared"), + TEXT("package/react-spring-types"), + TEXT("package/react-spring-rafz"), + TEXT("package/react-spring-parallax"), + TEXT("package/pmndrs-leva") + }; + StateMotionContract.StateKinds = + { + TEXT("lightweight browser store"), + TEXT("selector subscriptions"), + TEXT("persist/devtools middleware"), + TEXT("schema-driven parameter state") + }; + StateMotionContract.GestureKinds = + { + TEXT("drag"), + TEXT("pinch"), + TEXT("hover"), + TEXT("wheel"), + TEXT("move"), + TEXT("multi-gesture composition") + }; + StateMotionContract.MotionKinds = + { + TEXT("spring hooks"), + TEXT("controller and spring values"), + TEXT("interpolation"), + TEXT("frame scheduling"), + TEXT("reduced-motion support"), + TEXT("layered transitions") + }; + StateMotionContract.ExplicitExclusions = + { + TEXT("global product-state ownership"), + TEXT("server-state ownership"), + TEXT("donor playground UI ownership") + }; + StateMotionContract.SourceAttribution = MakeAttribution( + TEXT("pmndrs/react-spring"), + TEXT("browser-spatial/state-motion-contract"), + TEXT("Preserves state-store, gesture-routing, spring-motion, frame-scheduling, and parameter-panel seams from zustand, use-gesture, react-spring, and leva.") + ); + Bundle.StateMotionContracts = {StateMotionContract}; + + return Bundle; +} + +bool UHyperTwistTrainingSpatialLibrary::TryGetSceneContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialSceneContract& OutContract +) +{ + for (const FHyperTwistTrainingSpatialSceneContract& Contract : Bundle.SceneContracts) + { + if (Contract.ContractId == ContractId) + { + OutContract = Contract; + return true; + } + } + + OutContract = FHyperTwistTrainingSpatialSceneContract(); + return false; +} + +bool UHyperTwistTrainingSpatialLibrary::TryGetXrSessionContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialXrSessionContract& OutContract +) +{ + for (const FHyperTwistTrainingSpatialXrSessionContract& Contract : Bundle.XrSessionContracts) + { + if (Contract.ContractId == ContractId) + { + OutContract = Contract; + return true; + } + } + + OutContract = FHyperTwistTrainingSpatialXrSessionContract(); + return false; +} + +bool UHyperTwistTrainingSpatialLibrary::TryGetSpatialUiContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialUiContract& OutContract +) +{ + for (const FHyperTwistTrainingSpatialUiContract& Contract : Bundle.SpatialUiContracts) + { + if (Contract.ContractId == ContractId) + { + OutContract = Contract; + return true; + } + } + + OutContract = FHyperTwistTrainingSpatialUiContract(); + return false; +} + +bool UHyperTwistTrainingSpatialLibrary::TryGetEffectBoundaryById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& BoundaryId, + FHyperTwistTrainingSpatialEffectBoundary& OutBoundary +) +{ + for (const FHyperTwistTrainingSpatialEffectBoundary& Boundary : Bundle.EffectBoundaries) + { + if (Boundary.BoundaryId == BoundaryId) + { + OutBoundary = Boundary; + return true; + } + } + + OutBoundary = FHyperTwistTrainingSpatialEffectBoundary(); + return false; +} + +bool UHyperTwistTrainingSpatialLibrary::TryGetStateMotionContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialStateMotionContract& OutContract +) +{ + for (const FHyperTwistTrainingSpatialStateMotionContract& Contract : Bundle.StateMotionContracts) + { + if (Contract.ContractId == ContractId) + { + OutContract = Contract; + return true; + } + } + + OutContract = FHyperTwistTrainingSpatialStateMotionContract(); + return false; +} + +FString UHyperTwistTrainingSpatialLibrary::BuildPackageChecklistTsv( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle +) +{ + using namespace HyperTwistTrainingSpatialLibraryInternal; + + FString Output = TEXT("package_id\tlabel\townership_role\tretained_surfaces\tsummary\n"); + for (const FHyperTwistTrainingSpatialPackageReference& Reference : Bundle.PackageReferences) + { + if (!Reference.IsStructurallyValid()) + { + continue; + } + + Output.Append(Reference.PackageId); + Output.Append(TEXT("\t")); + Output.Append(Reference.Label); + Output.Append(TEXT("\t")); + Output.Append(Reference.OwnershipRole); + Output.Append(TEXT("\t")); + + FString SurfaceTags; + AppendJoined(SurfaceTags, Reference.RetainedSurfaceTags); + Output.Append(SurfaceTags); + Output.Append(TEXT("\t")); + Output.Append(Reference.Summary.Replace(TEXT("\t"), TEXT(" "))); + Output.Append(TEXT("\n")); + } + + return Output; +} diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h index 8586bab..21e84b3 100644 --- a/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h @@ -8,6 +8,7 @@ #include "HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingCoachLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingKnowledgeLibrary.h" +#include "HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingViewerLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingTypes.h" #include "HyperTwistTrainingRuntimeLibrary.generated.h" @@ -156,6 +157,9 @@ public: UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Companion") static FHyperTwistTrainingCompanionReferenceBundle GetBundledEmbodiedCompanionReferenceBundle(); + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Spatial") + static FHyperTwistTrainingSpatialReferenceBundle GetBundledBrowserSpatialReferenceBundle(); + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training", meta = (WorldContext = "WorldContextObject")) static bool TryGetLatestGeneratedModeLaunchRequestForDeck( UObject* WorldContextObject, @@ -252,6 +256,39 @@ public: UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Companion") static FString BuildBundledEmbodiedCompanionSubtitleCueChecklistTsv(); + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetBundledBrowserSpatialSceneContract( + const FString& ContractId, + FHyperTwistTrainingSpatialSceneContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetBundledBrowserSpatialXrSessionContract( + const FString& ContractId, + FHyperTwistTrainingSpatialXrSessionContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetBundledBrowserSpatialUiContract( + const FString& ContractId, + FHyperTwistTrainingSpatialUiContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetBundledBrowserSpatialEffectBoundary( + const FString& BoundaryId, + FHyperTwistTrainingSpatialEffectBoundary& OutBoundary + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetBundledBrowserSpatialStateMotionContract( + const FString& ContractId, + FHyperTwistTrainingSpatialStateMotionContract& OutContract + ); + + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Spatial") + static FString BuildBundledBrowserSpatialPackageChecklistTsv(); + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training", meta = (WorldContext = "WorldContextObject")) static FHyperTwistTrainingLearnerDeckStateSummary GetActiveTrainingLearnerDeckStateSummary(UObject* WorldContextObject); diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h new file mode 100644 index 0000000..56687a3 --- /dev/null +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h @@ -0,0 +1,317 @@ +#pragma once + +#include "CoreMinimal.h" +#include "Kismet/BlueprintFunctionLibrary.h" +#include "HyperTwistTraining/HyperTwistTrainingTypes.h" +#include "HyperTwistTrainingSpatialLibrary.generated.h" + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialPackageReference +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PackageId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString OwnershipRole; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RetainedSurfaceTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !PackageId.IsEmpty() && !Label.IsEmpty() && !OwnershipRole.IsEmpty() + && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialSceneContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredPackageIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray LifecycleStages; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray EventSurfaceTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialXrSessionContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredPackageIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SessionModes; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray InputSurfaceTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray InteractionSurfaceTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialUiContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredPackageIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ComponentFamilies; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray StateSurfaceTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialEffectBoundary +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString BoundaryId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredPackageIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray EffectFamilies; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray FirstPartyOwnedFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !BoundaryId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialStateMotionContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredPackageIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray StateKinds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray GestureKinds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray MotionKinds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingSpatialReferenceBundle +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ReferenceUtc; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimarySceneContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryXrSessionContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimarySpatialUiContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryEffectBoundaryId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryStateMotionContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray PackageReferences; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SceneContracts; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray XrSessionContracts; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SpatialUiContracts; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray EffectBoundaries; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray StateMotionContracts; + + bool IsStructurallyValid() const + { + return !PrimarySceneContractId.IsEmpty() && !PrimaryXrSessionContractId.IsEmpty() + && !PrimarySpatialUiContractId.IsEmpty() && !PrimaryEffectBoundaryId.IsEmpty() + && !PrimaryStateMotionContractId.IsEmpty() && PackageReferences.Num() > 0; + } +}; + +UCLASS() +class UNREALHYPERTWIST_API UHyperTwistTrainingSpatialLibrary : public UBlueprintFunctionLibrary +{ + GENERATED_BODY() + +public: + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Spatial") + static FHyperTwistTrainingSpatialReferenceBundle BuildBundledBrowserSpatialReferenceBundle(); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetSceneContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialSceneContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetXrSessionContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialXrSessionContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetSpatialUiContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialUiContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetEffectBoundaryById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& BoundaryId, + FHyperTwistTrainingSpatialEffectBoundary& OutBoundary + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Spatial") + static bool TryGetStateMotionContractById( + const FHyperTwistTrainingSpatialReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingSpatialStateMotionContract& OutContract + ); + + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Spatial") + static FString BuildPackageChecklistTsv(const FHyperTwistTrainingSpatialReferenceBundle& Bundle); +}; diff --git a/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md b/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md index b49fe28..b469709 100644 --- a/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md +++ b/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md @@ -241,19 +241,19 @@ Practical rule: For HyperTwist specifically, the mirror/handoff model must now carry one additional explicit truth: - current curated shallow-eval set: `71` repos -- currently verified live in checked `UnrealHyperTwist` surfaces: `11` -- permissive live lanes: `10` +- currently verified live in checked `UnrealHyperTwist` surfaces: `14` +- permissive live lanes: `13` - restrictive live lane: `1` - the restrictive live lane is `onionhoney/roux-trainers` - that lane is to be treated as properly clean-roomed and then implemented -- `Phase 0R` is now closed for the remaining `61` non-live rows +- `Phase 0R` is now closed for the remaining `57` non-live rows - `Phase 1R` is now closed as the retained-set contract and handoff layer -- the eleven already-live rows now also have a dedicated source-backed preservation authority doc +- the fourteen already-live rows now also have a dedicated source-backed preservation authority doc - `Phase 2R-A` is now closed as the core ownership and acceptance authority for the five retained permissive anchor rows - `Phase 2R-B` is now closed as the support-plane ownership and acceptance authority for the retained permissive support rows in scope - `Phase 2R-C` is now closed as the residual adjunct and alternative-support ownership and acceptance authority for the final retained permissive `0R-B` rows - the current manifest and doc control plane should now distinguish: - - `48` non-live active implementation-board rows + - `45` non-live active implementation-board rows - `9` retained benchmark/oracle/clean-room-later rows outside the active implementation board - `3` discarded active-set rows @@ -269,13 +269,14 @@ Reset rule: - do not reopen `Phase 0R` - before new donor-shaped widening for HyperTwist, read: - - `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` for the eleven already-live lanes + - `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` for the fourteen already-live lanes - `docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md` for routing - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` for the five retained core permissive rows - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` for the retained permissive support-plane rows in scope - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` for the final retained permissive `0R-B` adjunct and alternative-support rows - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md` before widening the landed analytics/reporting lane again - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md` before widening the landed browser presentation and asset-QA lane again + - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md` before widening the landed browser spatial owner trio again - the relevant `0R-*` packet for any non-live retained row ## Manifest schema diff --git a/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md b/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md index db55470..4981c2a 100644 --- a/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md +++ b/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md @@ -33,6 +33,11 @@ Important correction added on `2026-05-13`: - `met4citizen/TalkingHead` is now a currently verified live permissive lane through `Phase 3R-E`. - it is live through first-party Unreal embodied-companion contract code plus bundled reference-target materialization rather than through the direct training-deck bundle path used by the earlier five permissive donor lanes in this audit. +Important correction added on `2026-05-13`: + +- `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` are now currently verified live permissive lanes through `Phase 3R-F`. +- they are live through first-party Unreal browser spatial contract code plus bundled reference-target materialization rather than through the direct training-deck bundle path used by the earlier five permissive donor lanes in this audit. + ## Scope - Current repo set audited: the 71 `HyperTwist` rows in `docs/repo_portfolio_unified_source_audit_v6_3.csv`. @@ -80,7 +85,6 @@ Important correction added on `2026-05-13`: - `MagicCube4D` - `MagicTile` - `MagicCube5D` - - `TalkingHead` ## Permissive bucket @@ -108,6 +112,10 @@ These rows are now materially present in checked first-party Unreal source, even | `Hypercubers/hypercubing.xyz` | MIT | landed via `Phase 3R-B` | `HyperTwistTrainingKnowledgeLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json` | First-party taxonomy, notation glossary, progression contracts, software matrix, and leaderboard/report contracts now landed in first-party source and bundled reference targets | | `apache/echarts` | Apache-2.0 | landed via `Phase 3R-C` | `HyperTwistTrainingAnalyticsLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json`; `apache-echarts-reference-pages.jsonl` | First-party analytics report bundle, TSV data-view export, live-timer reporting accessors, and bundled analytics reference-target surfaces now landed in first-party source and materialized reference outputs | | `google/model-viewer` | Apache-2.0 | landed via `Phase 3R-D` | `HyperTwistTrainingViewerLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json`; `google-model-viewer-reference-pages.jsonl` | First-party browser viewer, compact editor, asset-validation, renderer-comparison, and docs-boundary reference surfaces now landed in first-party source and materialized reference outputs | +| `met4citizen/TalkingHead` | MIT | landed via `Phase 3R-E` | `HyperTwistTrainingCompanionLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json`; `met4citizen-talkinghead-reference-pages.jsonl` | First-party embodied companion narration, subtitle timing, viseme/lip-sync, avatar-only embed, gesture/mood, and vendor-boundary reference surfaces now landed in first-party source and materialized reference outputs | +| `mrdoob/three.js` | MIT | landed via `Phase 3R-F` | `HyperTwistTrainingSpatialLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json`; `browser-spatial-support-reference-pages.jsonl` | First-party browser scene, renderer, camera, render-loop, and WebXR support contracts now landed in first-party source and materialized reference outputs | +| `pmndrs/react-three-fiber` | MIT | landed via `Phase 3R-F` | `HyperTwistTrainingSpatialLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json`; `browser-spatial-support-reference-pages.jsonl` | First-party React-side browser renderer, createRoot/frameloop, store, and event-bridge contracts now landed in first-party source and materialized reference outputs | +| `pmndrs/xr` | MIT | landed via `Phase 3R-F` | `HyperTwistTrainingSpatialLibrary.h/.cpp`; `HyperTwistTrainingRuntimeLibrary.h/.cpp`; `hypertwist-reference-incorporation-targets.json`; `hypertwist-catalog-materialization-summary.json`; `browser-spatial-support-reference-pages.jsonl` | First-party browser XR session, controller/hand/gaze input, pointer-routing, and immersive interaction contracts now landed in first-party source and materialized reference outputs | ### Partly implemented @@ -134,19 +142,15 @@ These rows are donor-approved or integration-shaped in the current docs, but thi - `cahidenes/rubiks-cube-solver` - `HactarCE/Hyperspeedcube` - `kkoomen/qbr` -- `met4citizen/TalkingHead` -- `mrdoob/three.js` - `NuiLab/code-vr` - `pmndrs/drei` - `pmndrs/leva` - `pmndrs/maath` - `pmndrs/react-postprocessing` - `pmndrs/react-spring` -- `pmndrs/react-three-fiber` - `pmndrs/three-stdlib` - `pmndrs/uikit` - `pmndrs/use-gesture` -- `pmndrs/xr` - `pmndrs/zustand` - `PostHog/posthog` - `roice3/Magic120Cell` @@ -274,10 +278,16 @@ These are not part of the current 71-repo shallow-eval set, but they are live in These currently live lanes are under permissive direct-donor posture and can be preserved with ordinary notice and attribution handling: - `Aarav2709/KubeTimr` +- `apache/echarts` - `abunickabhi/5style-Trainer` +- `google/model-viewer` - `Hypercubers/hypercubing.xyz` +- `mrdoob/three.js` +- `pmndrs/react-three-fiber` +- `pmndrs/xr` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` +- `met4citizen/TalkingHead` - `poliva/cubedex` - `newyork-anthonyng/rubiks-cross-trainer` @@ -312,7 +322,7 @@ That does not make them legally cleared or deeply audited. It only means this pa ## Recommended next implementation slice -The next clean bounded move is to preserve the eleven landed lanes as the current truth, keep the `onionhoney/roux-trainers` clean-room status explicit everywhere, and continue from the closed retained-set packet sequence with `Phase 3R-F`. After that, do a second pass focused on the additional live non-71 surfaces (`SpeedCubeDB` and `CubingApp`) so the active training catalog has a complete provenance board before any further widening work resumes. +The next clean bounded move is to preserve the fourteen landed lanes as the current truth, keep the `onionhoney/roux-trainers` clean-room status explicit everywhere, and continue from the closed retained-set packet sequence with `Phase 4R-A` for `cubing/cubing.js`, while leaving the optional `Phase 3R-G` browser comparison lane deferred unless the landed primary browser spatial stack exposes a real gap. After that, do a second pass focused on the additional live non-71 surfaces (`SpeedCubeDB` and `CubingApp`) so the active training catalog has a complete provenance board before any further widening work resumes. For the readable all-rows follow-up board that pairs this audit with the reset schedule, use: diff --git a/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md b/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md index 885802b..660fe93 100644 --- a/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md +++ b/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md @@ -38,17 +38,20 @@ Current handling: The current reconciled HyperTwist truth is: - current curated HyperTwist shallow-eval set: `71` repos -- currently verified live in checked `UnrealHyperTwist` surfaces: `11` -- currently verified live permissive lanes: `10` +- currently verified live in checked `UnrealHyperTwist` surfaces: `14` +- currently verified live permissive lanes: `13` - currently verified live restrictive lanes: `1` -The ten currently verified live permissive lanes are: +The thirteen currently verified live permissive lanes are: - `Aarav2709/KubeTimr` - `apache/echarts` - `abunickabhi/5style-Trainer` - `google/model-viewer` - `Hypercubers/hypercubing.xyz` +- `mrdoob/three.js` +- `pmndrs/react-three-fiber` +- `pmndrs/xr` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` - `met4citizen/TalkingHead` @@ -151,14 +154,14 @@ Use the following only as lineage or historical context unless a restart doc exp The restart is not a mass revert. -It is a provenance and planning reset around the remaining `60` current non-live rows while preserving the eleven already-landed lanes. +It is a provenance and planning reset around the remaining `57` current non-live rows while preserving the fourteen already-landed lanes. Required standing rules: -- preserve the eleven landed lanes +- preserve the fourteen landed lanes - preserve `onionhoney/roux-trainers` as the only currently verified landed restrictive clean-room lane - do not collapse `selected`, `retained`, `integrate`, `repurpose`, or `donor bench` into `already implemented` -- do not widen new donor-shaped implementation from the remaining `60` current non-live rows until the closed packet sequence routes it +- do not widen new donor-shaped implementation from the remaining `57` current non-live rows until the closed packet sequence routes it - before implementing any retained repo, read the packet-level deep-source authority doc for that repo class if one exists ## 2026-05-12 packet-depth correction @@ -482,12 +485,15 @@ Result: - `apache/echarts` is now the eighth permissive live lane and ninth live row overall - `google/model-viewer` is now the ninth permissive live lane and tenth live row overall - `met4citizen/TalkingHead` is now the tenth permissive live lane and eleventh live row overall +- `mrdoob/three.js` is now the eleventh permissive live lane and twelfth live row overall +- `pmndrs/react-three-fiber` is now the twelfth permissive live lane and thirteenth live row overall +- `pmndrs/xr` is now the thirteenth permissive live lane and fourteenth live row overall - `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, and `roice3/MagicTile` remain packetized for `Phase 6R` - `Hypercubers/hypercubing.xyz` is now a landed permissive knowledge/curriculum/community lane rather than the next straight permissive candidate - `apache/echarts` is now a landed permissive analytics/reporting lane rather than the next straight permissive candidate - `google/model-viewer` plus `KhronosGroup/glTF-Sample-Viewer` are now the landed browser presentation/editor and standards-QA `3R-D` lane - `met4citizen/TalkingHead` is now the landed embodied companion `3R-E` lane -- `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` now define the retained browser `3D` / XR support `3R-F` lane +- `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` are now the landed browser spatial owner trio through `3R-F` - `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` now form the retained `6R-E` recognition-comparison adjunct lane - `NuiLab/code-vr` now forms the retained `6R-F` symbolic-to-spatial XR pedagogy experiment lane - `pissang/claygl` and `pissang/clay-viewer` now form the retained optional `3R-G` alternative browser comparison lane @@ -500,7 +506,7 @@ License-tracking boundary: - `docs/REPO_LICENSE_TRACKING.md` is the canonical repo-row legal and attribution ledger - `docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md` is policy-only and must not become a second repo-row legal ledger -- `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` is the source-backed preservation authority for the eleven already-live rows +- `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` is the source-backed preservation authority for the fourteen already-live rows - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` is the packet authority for the five core retained permissive rows once source extraction has already been read - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` is the packet authority for the primary retained permissive support-plane rows once source extraction has already been read - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` is the packet authority for the final residual permissive `0R-B` adjunct and alternative-support rows once source extraction has already been read @@ -514,7 +520,7 @@ License-tracking boundary: The next bounded move is: -1. preserve the eleven landed rows as the current truth -2. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, and `met4citizen/TalkingHead` on preserve-and-enhance footing through their landed packets -3. open `Phase 3R-F` -4. widen `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` as the retained browser `3D`, XR session, and spatial-support lane +1. preserve the fourteen landed rows as the current truth +2. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, `met4citizen/TalkingHead`, `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` on preserve-and-enhance footing through their landed packets +3. open `Phase 4R-A` +4. widen `cubing/cubing.js` through the retained `MPL`-aware dependency or adapter lane, while keeping the optional `Phase 3R-G` browser comparison lane deferred unless the landed primary browser spatial stack exposes a real gap diff --git a/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md b/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md index 1233022..393d898 100644 --- a/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md +++ b/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md @@ -6,12 +6,12 @@ Created on `2026-05-13` This audit is `closed`. -It is the canonical source-backed preservation authority for the eleven HyperTwist rows that are already live in checked first-party Unreal surfaces. +It is the canonical source-backed preservation authority for the fourteen HyperTwist rows that are already live in checked first-party Unreal surfaces. It closes the symmetry gap that remained after `Phase 0R` and `Phase 1R`: -- the `60` non-live rows already have source-backed authority through `Packet 0R-A` through `Packet 0R-E` -- the `11` live rows now have source-backed authority through this live-lane preservation audit +- the `57` non-live rows already have source-backed authority through `Packet 0R-A` through `Packet 0R-E` +- the `14` live rows now have source-backed authority through this live-lane preservation audit ## Purpose @@ -27,7 +27,7 @@ Use this document to answer the live-lane questions that the `0R-*` packets do n This document intentionally separates permissive and restrictive handling: -- the ten permissive live lanes below are documented from donor mirror source plus first-party Unreal outputs +- the thirteen permissive live lanes below are documented from donor mirror source plus first-party Unreal outputs - the one restrictive live lane, `onionhoney/roux-trainers`, is documented here only from first-party Unreal outputs, `REPO_LICENSE_TRACKING.md`, and scrubbed clean-room materials Do not use this document as permission for `Model B` to read the restrictive mirror. @@ -37,19 +37,19 @@ Do not use this document as permission for `Model B` to read the restrictive mir Current result: - current curated HyperTwist shallow-eval set: `71` -- already covered by `0R-A` through `0R-E`: `60` current non-live rows -- covered by this audit: `11` live rows +- already covered by `0R-A` through `0R-E`: `57` current non-live rows +- covered by this audit: `14` live rows - total rows with source-backed authority now visible in canonical docs: `71` -- live permissive preserve lanes: `10` +- live permissive preserve lanes: `13` - live restrictive clean-room preserve lanes: `1` -- additional live rows discovered beyond the original six from the 2026-05-11 audit: `5` +- additional live rows discovered beyond the original six from the 2026-05-11 audit: `8` ## Authority order For future work on the already-live lanes, read in this order: 1. this live-lane audit -2. the relevant landed implementation packet where one exists, currently [HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md:1) for `Aarav2709/KubeTimr`, [HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md:1) for `Hypercubers/hypercubing.xyz`, [HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md:1) for `apache/echarts`, [HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md:1) for `google/model-viewer`, and [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) for `met4citizen/TalkingHead` +2. the relevant landed implementation packet where one exists, currently [HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md:1) for `Aarav2709/KubeTimr`, [HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md:1) for `Hypercubers/hypercubing.xyz`, [HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md:1) for `apache/echarts`, [HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md:1) for `google/model-viewer`, [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) for `met4citizen/TalkingHead`, and [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) for `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` 3. [HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md:1) 4. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) 5. [MODEL_B_SOURCE_ACCESS_BOUNDARY.md](C:/HyperTwist/docs/MODEL_B_SOURCE_ACCESS_BOUNDARY.md:1) for the `onionhoney/roux-trainers` lane @@ -62,6 +62,9 @@ For future work on the already-live lanes, read in this order: | `Hypercubers/hypercubing.xyz` | `MIT` | landed taxonomy, notation, progression, software-reference, and leaderboard-contract lane | the main landed permissive hypercubing knowledge and community-reference preserve lane | runtime simulation, solver execution, recognition, or timer ownership | | `apache/echarts` | `Apache-2.0` | landed analytics, reporting, export, and progress-visualization lane | the main landed permissive analytics and report-contract preserve lane | gameplay/runtime ownership, generic BI shell ownership, or separate live-lane claims for `zrender` / `echarts-gl` | | `google/model-viewer` | `Apache-2.0` | landed browser presentation, compact editor, and standards-aware asset-QA lane | the main landed permissive browser viewer and support-plane asset-QA preserve lane | gameplay/runtime ownership, donor docs/demo shell ownership, mixed-asset shipping from `shared-assets`, or separate live-lane claims for the subordinate package rows and Khronos sidecars | +| `mrdoob/three.js` | `MIT` | landed browser scene, renderer, camera, and controller-space substrate lane | the main landed permissive browser `3D` substrate preserve lane | gameplay/runtime ownership, browser-first product-shell ownership, or separate live-lane claims for subordinate helper packages | +| `pmndrs/react-three-fiber` | `MIT` | landed React-side browser renderer, frameloop, store, and event-bridge lane | the main landed permissive React-side browser renderer preserve lane | gameplay/runtime ownership, generic app-state ownership, or standalone product-shell ownership | +| `pmndrs/xr` | `MIT` | landed browser XR session, controller, hand, gaze, and immersive interaction lane | the main landed permissive browser XR session and immersive interaction preserve lane | gameplay/runtime ownership, generic VR showroom ownership, or separate live-lane claims for subordinate UI, gesture, or motion helpers | | `met4citizen/TalkingHead` | `MIT` | landed embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane | the main landed permissive embodied coach and companion preserve lane | generic speech-engine ownership, sample-asset shipping assumptions, donor example-shell ownership, or vendor lock-in | | `tao-yu/Alg-Trainer` | `MIT` | broad algorithm-training shell and case-corpus foundation | the main landed permissive algorithm-trainer foundation | persisted coaching backend or smartcube-first review shell | | `Lykos/cube_trainer` | `MIT` | persisted coaching, weighted sampling, and BLD-domain lane | the main landed permissive training-session and coaching lane | broad front-end training-shell ownership | @@ -481,6 +484,165 @@ Future widening rule: - keep the sample-asset and external-service provenance caveat visible - read the landed [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) before treating this lane as an open donor candidate again +### `mrdoob/three.js` + +Current status: + +- `implemented_live_permissive` +- preserve as a landed first-party permissive lane + +Licensing posture: + +- `MIT` +- preserve the checked local MIT notice in third-party notices or equivalent release/legal materials + +Source surfaces inspected: + +- [package.json](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/package.json:1) +- [README.md](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/README.md:1) +- [src/Three.Core.js](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/src/Three.Core.js:1) +- [src/renderers/WebGLRenderer.js](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/src/renderers/WebGLRenderer.js:1) +- [src/renderers/webxr/WebXRManager.js](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/src/renderers/webxr/WebXRManager.js:1) + +First-party live evidence: + +- [HyperTwistTrainingSpatialLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h:1) +- [HyperTwistTrainingSpatialLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp:1) +- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1) +- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1) +- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1) +- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1) +- [browser-spatial-support-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl:1) + +Preserved landed value: + +- first-party browser scene graph, renderer, camera, and render-loop substrate boundaries +- first-party WebXR manager and controller-space contract surfaces for browser-side spatial support +- first-party package ownership records that keep `three.js` as the browser `3D` base beneath higher-level helper and XR lanes + +Excluded or non-promotion boundary: + +- do not promote this lane into gameplay/runtime ownership +- do not treat it as a reason to displace the Unreal-first runtime stance +- do not flatten subordinate helper packages into separate live claims because this substrate is landed + +Rationale: + +- this repo is valuable because it is the strongest bounded browser `3D` substrate in the retained stack +- its strongest landed value is scene, renderer, and WebXR substrate behavior rather than product-shell ownership + +Future widening rule: + +- widen only through ordinary first-party enhancement work +- preserve the MIT notice in redistributed builds +- read the landed [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) before treating this lane as an open donor candidate again + +### `pmndrs/react-three-fiber` + +Current status: + +- `implemented_live_permissive` +- preserve as a landed first-party permissive lane + +Licensing posture: + +- `MIT` +- preserve the checked local MIT notice in third-party notices or equivalent release/legal materials + +Source surfaces inspected: + +- [packages/fiber/package.json](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/package.json:1) +- [packages/fiber/readme.md](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/readme.md:1) +- [packages/fiber/src/web/Canvas.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/src/web/Canvas.tsx:1) +- [packages/fiber/src/core/renderer.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/src/core/renderer.tsx:1) +- [packages/fiber/src/core/events.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/src/core/events.ts:1) + +First-party live evidence: + +- [HyperTwistTrainingSpatialLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h:1) +- [HyperTwistTrainingSpatialLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp:1) +- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1) +- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1) +- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1) +- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1) +- [browser-spatial-support-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl:1) + +Preserved landed value: + +- first-party React-side canvas-root, createRoot, frameloop invalidation, and renderer/store lifecycle contracts +- first-party event-bridge and raycaster ownership boundaries above the landed `three.js` substrate +- explicit runtime-library accessors and reference targets for the React-side browser spatial stack + +Excluded or non-promotion boundary: + +- do not promote this lane into gameplay/runtime ownership +- do not treat it as generic app-state or browser-product ownership +- do not flatten helper abstractions above it into separate live claims + +Rationale: + +- this repo is valuable because it is the strongest retained React-side browser renderer in the set +- its strongest landed value is renderer lifecycle, store, and event-bridge behavior rather than product-shell ownership + +Future widening rule: + +- widen only through ordinary first-party enhancement work +- preserve the MIT notice in redistributed builds +- read the landed [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) before treating this lane as an open donor candidate again + +### `pmndrs/xr` + +Current status: + +- `implemented_live_permissive` +- preserve as a landed first-party permissive lane + +Licensing posture: + +- `MIT` +- preserve the checked local MIT notice in third-party notices or equivalent release/legal materials + +Source surfaces inspected: + +- [packages/xr/src/store.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/xr/src/store.ts:1) +- [packages/react/xr/src/xr.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/react/xr/src/xr.tsx:1) +- [packages/react/xr/src/dom-overlay.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/react/xr/src/dom-overlay.tsx:1) +- [packages/react/xr/src/controller-locomotion.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/react/xr/src/controller-locomotion.ts:1) +- [packages/pointer-events/src/index.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/pointer-events/src/index.ts:1) + +First-party live evidence: + +- [HyperTwistTrainingSpatialLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h:1) +- [HyperTwistTrainingSpatialLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp:1) +- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1) +- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1) +- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1) +- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1) +- [browser-spatial-support-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl:1) + +Preserved landed value: + +- first-party XR session, visibility, controller, hand, gaze, and screen-input contract surfaces +- first-party pointer-routing and immersive interaction boundaries above the landed browser scene and renderer stack +- explicit support boundaries that keep spatial UI, gesture, and motion helpers subordinate beneath the landed XR owner + +Excluded or non-promotion boundary: + +- do not promote this lane into gameplay/runtime ownership +- do not treat it as a generic VR showroom or browser-first product shell +- do not flatten subordinate UI, gesture, or motion helpers into separate live claims + +Rationale: + +- this repo is valuable because it is the strongest retained browser XR session and immersive interaction donor in the set +- its strongest landed value is session-store, input-routing, and immersive interaction behavior rather than product-shell ownership + +Future widening rule: + +- widen only through ordinary first-party enhancement work +- preserve the MIT notice in redistributed builds +- read the landed [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) before treating this lane as an open donor candidate again + ### `Lykos/cube_trainer` Current status: @@ -680,7 +842,7 @@ Future widening rule: HyperTwist now has symmetric source-backed authority across the current `71`-row curated set: -- `60` current non-live rows through `Packet 0R-A` through `Packet 0R-E` -- `11` live rows through this live-lane preservation audit +- `57` current non-live rows through `Packet 0R-A` through `Packet 0R-E` +- `14` live rows through this live-lane preservation audit For live-lane work, the next instance should not start from stale donor labels or from the raw mirror alone. It should start from this document, then the retained-set contract, then the repo-row license tracker. diff --git a/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md b/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md index d45b9d0..7e048da 100644 --- a/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md +++ b/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md @@ -66,20 +66,20 @@ Document responsibilities are now strict: Current post-`Phase 1R` truth: - curated HyperTwist shallow-eval set: `71` -- currently verified live in checked Unreal surfaces: `11` +- currently verified live in checked Unreal surfaces: `14` - rows with source-backed authority now visible in canonical docs: `71` - retained rows total: `68` - discarded from the active retained set: `3` Retained split: -- landed/live preserve lanes: `11` -- non-live active implementation-board rows: `48` +- landed/live preserve lanes: `14` +- non-live active implementation-board rows: `45` - non-live benchmark, oracle, or clean-room-later rows outside the active implementation board: `9` -The `48` non-live active implementation-board rows break down as: +The `45` non-live active implementation-board rows break down as: -- straight permissive implementation candidates: `38` +- straight permissive implementation candidates: `35` - boundary-sensitive adapter or sidecar candidates: `6` - restrictive clean-room-only candidates: `4` @@ -87,9 +87,9 @@ The `48` non-live active implementation-board rows break down as: | Class | Count | Earliest next phase | Meaning | | --- | --- | --- | --- | -| `landed_permissive_preserve` | `10` | ordinary first-party enhancement only | Already live. Preserve notices and attribution. Do not treat as speculative donor backlog. | +| `landed_permissive_preserve` | `13` | ordinary first-party enhancement only | Already live. Preserve notices and attribution. Do not treat as speculative donor backlog. | | `landed_clean_room_preserve` | `1` | ordinary first-party enhancement only | Already live. Preserve the clean-room chain and work from first-party outputs, not the restrictive mirror. | -| `phase3r_permissive_candidate` | `38` | `Phase 3R` | Retained for direct permissive implementation or bounded first-party adaptation. No clean-room lane is needed. | +| `phase3r_permissive_candidate` | `35` | `Phase 3R` | Retained for direct permissive implementation or bounded first-party adaptation. No clean-room lane is needed. | | `phase4r_boundary_candidate` | `6` | `Phase 4R` | Retained only through explicit adapter, allowlist, sidecar, or notice-sensitive use. | | `phase5r_clean_room_candidate` | `4` | `Phase 5R` | Retained only through refreshed Model A / Model B clean-room work. | | `benchmark_oracle_only` | `9` | outside the active implementation board | Retained only for validation, parity, oracle behavior, or a later explicitly reopened clean-room-later lane. | @@ -106,7 +106,7 @@ The `48` non-live active implementation-board rows break down as: ## Landed preserve lanes -These eleven rows are the only currently verified live rows in checked Unreal surfaces. +These fourteen rows are the only currently verified live rows in checked Unreal surfaces. ### Landed permissive preserve @@ -117,7 +117,10 @@ These eleven rows are the only currently verified live rows in checked Unreal su - `Hypercubers/hypercubing.xyz` — `MIT` - `Lykos/cube_trainer` — `MIT` - `met4citizen/TalkingHead` — `MIT` +- `mrdoob/three.js` — `MIT` - `newyork-anthonyng/rubiks-cross-trainer` — `MIT` +- `pmndrs/react-three-fiber` — `MIT` +- `pmndrs/xr` — `MIT` - `poliva/cubedex` — `MIT` - `tao-yu/Alg-Trainer` — `MIT` @@ -171,6 +174,8 @@ Contract: `met4citizen/TalkingHead` has now also completed `Phase 3R-E` and moved into the landed preserve set. +`mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` have now also completed `Phase 3R-F` and moved into the landed preserve set. + The remaining non-live support-plane rows covered by `2R-B` are: - `ecomfe/zrender` -> subordinate beneath landed `Phase 3R-C` @@ -181,7 +186,6 @@ The remaining non-live support-plane rows covered by `2R-B` are: - `google/model-viewer/packages/space-opera` -> subordinate beneath landed `Phase 3R-D` - `KhronosGroup/glTF-Sample-Renderer` -> subordinate beneath landed `Phase 3R-D` - `KhronosGroup/glTF-Sample-Viewer` -> subordinate beneath landed `Phase 3R-D` -- `mrdoob/three.js` - `@react-spring/animated` - `@react-spring/core` - `@react-spring/parallax` @@ -194,11 +198,9 @@ The remaining non-live support-plane rows covered by `2R-B` are: - `pmndrs/postprocessing` - `pmndrs/react-postprocessing` - `pmndrs/react-spring` -- `pmndrs/react-three-fiber` - `pmndrs/three-stdlib` - `pmndrs/uikit` - `pmndrs/use-gesture` -- `pmndrs/xr` - `pmndrs/zustand` -> `Phase 3R-F` Residual `0R-B` rows are still retained but not closed by `2R-B`: @@ -225,6 +227,7 @@ Contract: - read [HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `Hypercubers/hypercubing.xyz` lane further - read [HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `apache/echarts` lane further - read [HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `google/model-viewer` lane further +- read [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed browser spatial owner trio further - treat `2R-B` rows as support-plane owners, subordinate packages, or helper/dependency lanes according to the packet, not as equal foundation owners - treat `2R-C` rows as comparison adjuncts, symbolic-to-spatial experiment donors, or alternative browser comparison lanes rather than equal support-plane owners @@ -324,9 +327,9 @@ Do not: ## Next move -`Phase 2R` is now closed and `Phase 3R-A`, `Phase 3R-B`, `Phase 3R-C`, and `Phase 3R-D` are now also closed. +`Phase 2R` is now closed and `Phase 3R-A` through `Phase 3R-F` are now also closed for the primary straight-permissive widening path. -The next bounded move after those closures is `Phase 3R-F`: +The next bounded move after those closures is `Phase 4R-A`: -- widen `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` as the retained browser `3D`, XR session, and spatial-support lane -- preserve `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, and `google/model-viewer` as landed permissive lanes rather than reclassifying any of them as open candidates +- widen `cubing/cubing.js` through the retained `MPL`-aware adapter or dependency lane +- keep the optional `Phase 3R-G` `pissang/claygl` and `pissang/clay-viewer` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap that requires it diff --git a/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md b/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md new file mode 100644 index 0000000..30d7127 --- /dev/null +++ b/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md @@ -0,0 +1,198 @@ +# HyperTwist Phase 3R Packet 3R-F Browser Spatial Support Implementation + +Created on `2026-05-13` + +## Status + +`Phase 3R / Packet 3R-F` is now `closed`. + +This packet converts the retained browser spatial owner trio: + +- `mrdoob/three.js` +- `pmndrs/react-three-fiber` +- `pmndrs/xr` + +from retained browser-support anchors into landed first-party HyperTwist browser spatial support lanes. + +It does not reopen `Phase 0R`, `Phase 1R`, or `Phase 2R-B`. + +Those earlier packets still own source-value extraction, retained-set routing, and ownership boundaries. + +This packet owns the next question instead: + +- what first-party browser spatial implementation actually landed +- which retained donor value was realized +- which rows are now live owners versus subordinate helpers +- what remains explicitly out of scope for this lane +- what validation was completed +- what the next bounded implementation move is after this landing + +## Authority order + +For future work on the browser spatial support lane, read in this order: + +1. this packet for first-party landing scope, accepted widening, and validation result +2. [HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md:1) for live-lane preserve posture +3. [HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md:1) for ownership boundaries and pre-widening acceptance markers +4. [HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md:1) for source-value extraction and non-promotion rationale +5. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) for license, notice, and provenance obligations + +## Packet licensing snapshot + +Owner rows widened by this packet: + +- `mrdoob/three.js`: `MIT` +- `pmndrs/react-three-fiber`: `MIT` +- `pmndrs/xr`: `MIT` + +Subordinate retained support rows referenced by this packet: + +- `pmndrs/uikit`: `MIT` +- `pmndrs/postprocessing`: `Zlib` +- `pmndrs/react-postprocessing`: `MIT` +- `pmndrs/drei`: `MIT` +- `pmndrs/three-stdlib`: `MIT` +- `pmndrs/maath`: `MIT` +- `pmndrs/zustand`: `MIT` +- `pmndrs/leva`: `MIT` +- `pmndrs/use-gesture`: `MIT` +- `pmndrs/react-spring`: `MIT` +- `@react-spring/core`: `MIT` +- `@react-spring/shared`: `MIT` +- `@react-spring/types`: `MIT` +- `@react-spring/parallax`: `MIT` +- `@react-spring/rafz`: `MIT` +- `@react-spring/animated`: `MIT` + +Checked local notice surfaces: + +- [mrdoob/three.js package.json](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/package.json:1) +- [pmndrs/react-three-fiber package.json](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/package.json:1) +- [pmndrs/xr package.json](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/react/xr/package.json:1) +- [pmndrs/postprocessing LICENSE.md](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/postprocessing/LICENSE.md:1) + +## Packet result + +`3R-F` lands the browser spatial owner trio as: + +- `mrdoob/three.js` -> `implemented_live_permissive` +- `pmndrs/react-three-fiber` -> `implemented_live_permissive` +- `pmndrs/xr` -> `implemented_live_permissive` + +All three are now `landed_permissive_preserve`. + +Current portfolio effect: + +- curated HyperTwist shallow-eval set: `71` +- currently verified live in checked Unreal surfaces: `14` +- permissive live lanes: `13` +- restrictive live clean-room lanes: `1` +- active non-live implementation-board rows: `45` + +## Donor source surfaces read + +The source read for this widening remained bounded to browser scene substrate, React-side renderer lifecycle, XR session and input state, spatial UI support, post-effect boundaries, and motion/state helper seams: + +- [src/renderers/webxr/WebXRManager.js](C:/Workspaces/HyperTwist/mirrors/permissive/mrdoob/three.js/src/renderers/webxr/WebXRManager.js:1) +- [packages/fiber/src/core/renderer.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-three-fiber/packages/fiber/src/core/renderer.tsx:1) +- [packages/react/xr/src/xr.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/react/xr/src/xr.tsx:1) +- [packages/xr/src/store.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/xr/packages/xr/src/store.ts:1) +- [packages/uikit/src/panel/index.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/uikit/packages/uikit/src/panel/index.ts:1) +- [src/core/EffectComposer.js](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/postprocessing/src/core/EffectComposer.js:1) +- [src/EffectComposer.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-postprocessing/src/EffectComposer.tsx:1) +- [src/web/View.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/drei/src/web/View.tsx:1) +- [src/web/Html.tsx](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/drei/src/web/Html.tsx:1) +- [src/webxr/XRControllerModelFactory.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/three-stdlib/src/webxr/XRControllerModelFactory.ts:1) +- [packages/maath/src/easing.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/maath/packages/maath/src/easing.ts:1) +- [src/vanilla.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/zustand/src/vanilla.ts:1) +- [packages/leva/src/useControls.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/leva/packages/leva/src/useControls.ts:1) +- [packages/react/src/useGesture.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/use-gesture/packages/react/src/useGesture.ts:1) +- [packages/core/src/hooks/useSpring.ts](C:/Workspaces/HyperTwist/mirrors/permissive/pmndrs/react-spring/packages/core/src/hooks/useSpring.ts:1) + +## First-party landing surfaces + +The landed first-party Unreal surfaces are: + +- [HyperTwistTrainingSpatialLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.h:1) +- [HyperTwistTrainingSpatialLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSpatialLibrary.cpp:1) +- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1) +- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1) +- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1) +- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1) +- [browser-spatial-support-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/browser-spatial-support-reference-pages.jsonl:1) + +## Landed implementation scope + +What landed: + +- a first-party compiled browser spatial reference bundle with explicit package ownership records for browser scene substrate, React-side renderer, XR session stack, spatial UI support, effect boundaries, and state/motion support +- a first-party scene contract for browser-side scene graph, camera, render-loop, and controller-space lifecycle boundaries +- a first-party XR session contract for immersive session modes, controller/hand/gaze input surfaces, pointer routing, and session visibility boundaries +- a first-party spatial UI contract for world-anchored panel families, state-bearing browser-side controls, and explicit non-ownership exclusions +- a first-party post-effect boundary for bounded render-pass and emphasis ownership beneath the browser support plane +- a first-party state/motion contract for store, gesture, control-panel, and spring-motion support beneath the browser spatial owner trio +- first-party runtime-library accessors and TSV checklist export for the new browser spatial bundle +- bundled first-party reference targets and raw source-reference capture for browser scene, renderer, XR session, UI, effects, helpers, and state/motion reference families + +What that means in practice: + +- `mrdoob/three.js` now owns the landed permissive browser `3D` substrate preserve lane in HyperTwist +- `pmndrs/react-three-fiber` now owns the landed permissive React-side browser renderer and event-bridge preserve lane in HyperTwist +- `pmndrs/xr` now owns the landed permissive browser XR session and immersive interaction preserve lane in HyperTwist +- the landed surface is a first-party Unreal spatial contract and runtime API, not a vague future donor note +- `pmndrs/uikit`, `pmndrs/postprocessing`, `pmndrs/react-postprocessing`, `pmndrs/drei`, `pmndrs/three-stdlib`, `pmndrs/maath`, `pmndrs/zustand`, `pmndrs/leva`, `pmndrs/use-gesture`, `pmndrs/react-spring`, and `@react-spring/*` remain retained subordinate support rows beneath the landed owner trio and are not separately live + +## Preserved landed value + +The donor value that was actually promoted is: + +- explicit browser-side scene, renderer, camera, render-target, and controller-space substrate boundaries +- explicit React-side canvas-root, frameloop invalidation, store, raycaster, and event-bridge behavior +- explicit XR session, visibility, controller/hand/gaze/screen input, pointer routing, and immersive interaction contracts +- explicit subordinate spatial UI, effect-composer, helper, state, gesture, and spring-motion support seams beneath the landed owner trio +- explicit first-party exclusion boundaries so browser-side spatial support does not silently become gameplay, simulation, or general runtime ownership + +## Excluded or non-promotion boundary + +Do not promote this packet into: + +- a replacement for the Unreal-first runtime stance +- gameplay, puzzle-state, recognition, or training-platform ownership +- a claim that every helper package in the browser spatial stack is now separately live +- donor demo-shell, editor-shell, or browser-first app-shell ownership + +Rationale: + +- this packet was retained and widened because the owner trio is the strongest bounded browser spatial stack in the set +- its highest value is scene substrate, React-side rendering, XR session behavior, and explicit support boundaries, not a broad browser product shell +- the helper packages remain useful precisely because they stay subordinate to the landed owners instead of being flattened into separate live-lane claims + +## Acceptance markers satisfied + +The `2R-B` acceptance markers for this lane are now satisfied in first-party Unreal surfaces: + +- a first-party browser scene contract exists for scene graph, camera, renderer, WebXR manager, and controller-space lifecycle seams +- a first-party browser XR session contract exists for immersive mode, session state, visibility, input routing, and interaction boundaries +- a first-party browser spatial UI contract exists for panel families, world-anchored control surfaces, and state-bearing browser-side UI seams +- a first-party browser post-effect boundary exists for bounded effect-composer, pass-ordering, and emphasis ownership +- a first-party browser state/motion contract exists for store, gesture, parameter-panel, and spring-motion support beneath the landed owner trio + +## Validation + +Validation completed for this packet: + +- `git diff --check` passed apart from CRLF conversion warnings +- JSON validation passed for the updated materialized-catalog files and workspace manifest +- Unreal build succeeded with: + - `C:\Program Files\Epic Games\UE_5.7\Engine\Build\BatchFiles\Build.bat UnrealHyperTwistEditor Win64 Development C:\HyperTwist\UnrealHyperTwist\UnrealHyperTwist.uproject -WaitMutex -NoHotReloadFromIDE` + +Build result: + +- `Succeeded` on `2026-05-13` + +## Next move + +The next bounded move is `Phase 4R-A`: + +- widen `cubing/cubing.js` through the retained `MPL`-aware adapter or dependency lane rather than reopening broad permissive browser comparison work +- keep the optional `Phase 3R-G` `pissang/claygl` and `pissang/clay-viewer` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap that requires it diff --git a/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md b/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md index 4064a1f..189af1c 100644 --- a/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md +++ b/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md @@ -442,6 +442,35 @@ Next packet: - `3R-F` +## 2026-05-13 Phase 3R-F status + +`Phase 3R / Packet 3R-F` is now closed. + +- `Phase 3R-F` result doc: + - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md` + +Implementation result: + +- `mrdoob/three.js` is now landed as a first-party browser `3D` substrate lane +- `pmndrs/react-three-fiber` is now landed as a first-party React-side browser renderer and event-bridge lane +- `pmndrs/xr` is now landed as a first-party browser XR session and immersive interaction lane +- all three rows are now `implemented_live_permissive` +- `pmndrs/uikit`, `pmndrs/postprocessing`, `pmndrs/react-postprocessing`, `pmndrs/drei`, `pmndrs/three-stdlib`, `pmndrs/maath`, `pmndrs/zustand`, `pmndrs/leva`, `pmndrs/use-gesture`, `pmndrs/react-spring`, and the `@react-spring/*` packages remain retained subordinate support rows beneath the landed owner trio and are not separately live +- current verified live rows are now: + - `14` total + - `13` permissive + - `1` restrictive clean-room +- active non-live implementation-board rows are now `45` +- the primary retained browser spatial support stack is no longer a queued `Phase 3R` candidate; it is a landed live owner stack + +Validation result: + +- `UnrealHyperTwistEditor` build succeeded for the landed widening packet + +Next packet: + +- `4R-A` + Mandatory read rule before implementing, benchmarking against, or clean-rooming any `0R-E` repo: 1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md` @@ -469,20 +498,20 @@ Current curated HyperTwist shallow-eval set: Current verified live implementation state in checked `UnrealHyperTwist` source and materialized training surfaces: -- `11` repos are implemented/live -- `10` of those are permissive `MIT` or `Apache-2.0` lanes +- `14` repos are implemented/live +- `13` of those are permissive `MIT` or `Apache-2.0` lanes - `1` of those is a restrictive repo that was properly clean-roomed and then implemented Current 2026-05-11 repo-row reset counts: -- `implemented_live_permissive`: `10` +- `implemented_live_permissive`: `13` - `implemented_live_clean_room_verified`: `1` -- `selected_not_live_permissive_candidate`: `38` +- `selected_not_live_permissive_candidate`: `35` - `selected_not_live_boundary_sensitive`: `6` - `selected_not_live_clean_room_candidate`: `4` - `not_live_reference_or_discard_candidate`: `12` -### The eleven currently implemented/live repos +### The fourteen currently implemented/live repos Permissive `MIT` or `Apache-2.0` lanes already implemented/live: @@ -491,6 +520,9 @@ Permissive `MIT` or `Apache-2.0` lanes already implemented/live: - `abunickabhi/5style-Trainer` - `google/model-viewer` - `Hypercubers/hypercubing.xyz` +- `mrdoob/three.js` +- `pmndrs/react-three-fiber` +- `pmndrs/xr` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` - `met4citizen/TalkingHead` @@ -545,17 +577,17 @@ At the moment, only one HyperTwist repo should be described this way: HyperTwist should now proceed from the following rule: -- preserve the eleven live lanes +- preserve the fourteen live lanes - do not reopen the `onionhoney/roux-trainers` lane as if it were an unresolved accidental donor import -- do not treat the remaining `60` current non-live rows as already implemented +- do not treat the remaining `57` current non-live rows as already implemented - keep `Phase 0R`, `Phase 1R`, and `Phase 2R` closed as completed packet classes -- continue later-phase widening from the closed packet sequence, currently `Phase 3R-F` +- continue later-phase widening from the closed packet sequence, with `Phase 4R-A` as the next non-optional move and `Phase 3R-G` deferred unless a real browser comparison gap appears In practical terms: -- no, do **not** mass-revert the eleven landed lanes -- no, do **not** pretend the remaining `61` current non-live rows are already implemented -- yes, preserve the landed `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, and `met4citizen/TalkingHead` lanes as normal first-party enhancement surfaces +- no, do **not** mass-revert the fourteen landed lanes +- no, do **not** pretend the remaining `57` current non-live rows are already implemented +- yes, preserve the landed `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, `met4citizen/TalkingHead`, `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` lanes as normal first-party enhancement surfaces - yes, widen the next retained permissive lane only through its closed packet stack ## Phase reset sequence @@ -921,9 +953,9 @@ Only after that: The clean practical sequence is: -1. preserve the eleven landed lanes +1. preserve the fourteen landed lanes 2. make the current truth explicit everywhere -3. deep-evaluate the remaining `65` +3. deep-evaluate the remaining `57` 4. discard what should not survive 5. re-schedule what remains by permissive, boundary-sensitive, clean-room, and benchmark lanes 6. resume later-phase widening from that corrected retained set @@ -939,7 +971,8 @@ Current status: - `Phase 3R-C` is now also complete - `Phase 3R-D` is now also complete - `Phase 3R-E` is now also complete -- the next bounded move is `Phase 3R-F` for `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` +- `Phase 3R-F` is now also complete +- the next bounded move is `Phase 4R-A` for `cubing/cubing.js`, with the optional `Phase 3R-G` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap ## Companion docs diff --git a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md index 8aaf4fe..c48e44f 100644 --- a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md +++ b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md @@ -7,14 +7,14 @@ This board is the readable row-by-row companion to the v6.3 CSVs. It is derived ## Canonical summary - Current curated HyperTwist shallow-eval set: `71` repos -- Currently verified live in checked `UnrealHyperTwist` surfaces: `11` repos -- Live permissive lanes: `10` +- Currently verified live in checked `UnrealHyperTwist` surfaces: `14` repos +- Live permissive lanes: `13` - Live restrictive clean-room lanes: `1` - Remaining rows requiring `Phase 0R` deep repo evaluation: `0` ## 2026-05-13 packet and contract overlay -The baseline live-state counts above now include the landed `Phase 3R-C` analytics lane, the landed `Phase 3R-D` browser viewer lane, and the landed `Phase 3R-E` embodied companion lane, while `Phase 0R` and `Phase 1R` remain closed. +The baseline live-state counts above now include the landed `Phase 3R-C` analytics lane, the landed `Phase 3R-D` browser viewer lane, the landed `Phase 3R-E` embodied companion lane, and the landed `Phase 3R-F` browser spatial owner stack, while `Phase 0R` and `Phase 1R` remain closed. Read together with: @@ -33,6 +33,7 @@ Read together with: - [HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md:1) - [HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md:1) - [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) +- [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) That overlay closes evaluation for: @@ -52,7 +53,7 @@ Important authority correction: - `Packet 0R-C` is now the deep-source value-extraction and exclusion-rationale authority for its six boundary-sensitive repos - `Packet 0R-D` is now the governance and Model A authority for its four restrictive clean-room repos - `Packet 0R-E` is now the deep-source benchmark, reference, clean-room-later, and discard authority for its twelve rows -- the live-lane preservation audit is now the source-backed authority for the eleven already-landed rows +- the live-lane preservation audit is now the source-backed authority for the fourteen already-landed rows - `Phase 1R` is now the retained-set contract and handoff authority for all post-`Phase 0R` routing - `Phase 2R-A` is now the core ownership and acceptance authority for the five retained core permissive rows - `Phase 2R-B` is now the support-plane ownership and acceptance authority for the primary retained permissive support rows @@ -62,7 +63,8 @@ Important authority correction: - `Phase 3R-C` is now the landed implementation authority for `apache/echarts` - `Phase 3R-D` is now the landed implementation authority for `google/model-viewer` - `Phase 3R-E` is now the landed implementation authority for `met4citizen/TalkingHead` -- future enhancement or preservation work for the eleven landed rows should start from the live-lane audit, then the repo-specific landed packet where one exists, not from this board alone +- `Phase 3R-F` is now the landed implementation authority for `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` +- future enhancement or preservation work for the fourteen landed rows should start from the live-lane audit, then the repo-specific landed packet where one exists, not from this board alone - future implementation of those seven repos should start from `Packet 0R-A`, not from this board alone - future implementation of the `0R-B` permissive set should start from `Packet 0R-B`, then the relevant closed `2R-B` or `2R-C` ownership packet, not from this board alone - future implementation of those six boundary-sensitive repos should start from `Packet 0R-C`, not from this board alone @@ -77,7 +79,7 @@ Packet overlay result: - all `6` boundary-sensitive rows have now been packet-evaluated - all `4` restrictive clean-room rows have now been packet-evaluated - all `12` reference, benchmark, reserve, and discard rows have now been packet-evaluated -- all `11` live rows now also have symmetric source-backed preservation authority +- all `14` live rows now also have symmetric source-backed preservation authority - `Phase 2R-A` is now closed for the five core retained permissive rows - `Phase 2R-B` is now closed for the retained permissive support-plane owners, subordinate packages, and helper/dependency lanes in scope - `Phase 2R-C` is now closed for the final retained permissive `0R-B` residual rows @@ -86,24 +88,28 @@ Packet overlay result: - `Phase 3R-C` is now closed for the `apache/echarts` analytics, reporting, export, and progress-visualization lane - `Phase 3R-D` is now closed for the `google/model-viewer` browser presentation, compact editor, and standards-aware asset-QA lane - `Phase 3R-E` is now closed for the `met4citizen/TalkingHead` embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane +- `Phase 3R-F` is now closed for the `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` browser spatial owner trio - `Phase 2R` is now fully closed for the retained permissive set - `Aarav2709/KubeTimr` is now newly proven live in checked Unreal surfaces through `Phase 3R-A` - `Hypercubers/hypercubing.xyz` is now newly proven live in checked Unreal surfaces through `Phase 3R-B` - `apache/echarts` is now newly proven live in checked Unreal surfaces through `Phase 3R-C` - `google/model-viewer` is now newly proven live in checked Unreal surfaces through `Phase 3R-D` - `met4citizen/TalkingHead` is now newly proven live in checked Unreal surfaces through `Phase 3R-E` +- `mrdoob/three.js` is now newly proven live in checked Unreal surfaces through `Phase 3R-F` +- `pmndrs/react-three-fiber` is now newly proven live in checked Unreal surfaces through `Phase 3R-F` +- `pmndrs/xr` is now newly proven live in checked Unreal surfaces through `Phase 3R-F` - `Phase 0R` is now fully closed - `Phase 1R` is now fully closed - the `0R-E` result split is: - `9` retained benchmark, oracle, or clean-room-later rows - `3` discarded active-set rows -- the next bounded move is `Phase 3R-F` +- the next bounded move is `Phase 4R-A` ## Count by live-state class -- `implemented_live_permissive`: `10` +- `implemented_live_permissive`: `13` - `implemented_live_clean_room_verified`: `1` -- `selected_not_live_permissive_candidate`: `38` +- `selected_not_live_permissive_candidate`: `35` - `selected_not_live_boundary_sensitive`: `6` - `selected_not_live_clean_room_candidate`: `4` - `not_live_reference_or_discard_candidate`: `12` @@ -119,7 +125,7 @@ Packet overlay result: These are currently verified live in checked Unreal surfaces and are permissive lanes already implemented. -Count: `10` +Count: `13` | Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step | | --- | --- | --- | --- | --- | --- | --- | @@ -130,7 +136,10 @@ Count: `10` | `Hypercubers/hypercubing.xyz` | `MIT` | Locked Strategic Donor | `repurpose` | `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`. | | `Lykos/cube_trainer` | `MIT` | Locked Strategic Donor | `integrate` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | | `met4citizen/TalkingHead` | `MIT` | Donor Bench | `repurpose` | `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`. | +| `mrdoob/three.js` | `MIT` | Donor Bench | `repurpose` | `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`. | | `newyork-anthonyng/rubiks-cross-trainer` | `MIT` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | +| `pmndrs/react-three-fiber` | `MIT` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-F` closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the `3R-F` implementation packet, then `REPO_LICENSE_TRACKING.md`. | +| `pmndrs/xr` | `MIT` | Donor Bench | `repurpose` | `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`. | | `poliva/cubedex` | `MIT` | Locked Strategic Donor | `integrate` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | | `tao-yu/Alg-Trainer` | `MIT` | Locked Parallel Foundation | `integrate` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | @@ -148,7 +157,7 @@ Count: `1` These rows are retained, not currently proven live, and have now cleared `Phase 0R` deep evaluation. `Phase 1R` places them on the active implementation board with earliest re-entry through `Phase 3R`. -Count: `38` +Count: `35` | Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step | | --- | --- | --- | --- | --- | --- | --- | @@ -169,7 +178,6 @@ Count: `38` | `KhronosGroup/glTF-Sample-Renderer` | `Apache-2.0` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed `google/model-viewer` asset-QA lane; do not treat it as separately live. | | `KhronosGroup/glTF-Sample-Viewer` | `Apache-2.0` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed `google/model-viewer` lane; do not treat it as separately live. | | `kkoomen/qbr` | `MIT` | Locked Foundation | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-A` closed. Freeze as the `Phase 6R-B` calibration, perceptual color matching, contour ordering, and scan-state extraction anchor; keep browser-side correction ownership with `vivaansinghvi07/rubix-cube-solver`. | -| `mrdoob/three.js` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the commodity `Phase 3R-F` browser `3D` substrate beneath higher-level support surfaces; do not let it displace the Unreal-first runtime stance. | | `NuiLab/code-vr` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as the `Phase 6R-F` symbolic-to-spatial XR pedagogy experiment lane only; do not let it own the practical browser XR runtime. | | `pissang/clay-viewer` | `BSD-3-Clause` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as part of the optional `Phase 3R-G` alternative browser viewer/editor comparison lane subordinate to `google/model-viewer`; widen only if a real sidecar gap remains after the primary browser stack exists. | | `pissang/claygl` | `BSD-style permissive (see LICENSE)` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as part of the optional `Phase 3R-G` alternative browser `3D` comparison lane subordinate to `mrdoob/three.js`; widen only if a real sidecar gap remains after the primary browser stack exists. | @@ -179,11 +187,9 @@ Count: `38` | `pmndrs/postprocessing` | `Zlib` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the browser post-effect substrate inside `Phase 3R-F`; keep it beneath viewer/editor lanes rather than treating it as a product foundation. | | `pmndrs/react-postprocessing` | `MIT` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the React wrapper above `pmndrs/postprocessing` inside `Phase 3R-F`; use only if React-side browser tooling is actually justified. | | `pmndrs/react-spring` | `MIT` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the browser-side motion substrate inside `Phase 3R-F`; widen only where browser sidecars actually need motion behavior. | -| `pmndrs/react-three-fiber` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Freeze as the React-side renderer substrate inside `Phase 3R-F`; keep `mrdoob/three.js` as the lower-level browser `3D` base beneath it. | | `pmndrs/three-stdlib` | `MIT` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the shared utility shelf inside `Phase 3R-F`; use it only as infrastructure beneath higher-level browser lanes. | | `pmndrs/uikit` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Freeze as the browser spatial UI layer inside `Phase 3R-F` beside `pmndrs/xr`; do not promote it into a standalone product lane. | | `pmndrs/use-gesture` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the gesture/input substrate inside `Phase 3R-F`; widen only where browser sidecars actually need it. | -| `pmndrs/xr` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Freeze as the `Phase 3R-F` browser XR session and immersive interaction anchor; widen only from the `2R-B` ownership contract, then `0R-B`, then `REPO_LICENSE_TRACKING.md`. | | `pmndrs/zustand` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the browser-side state substrate inside `Phase 3R-F`; use only where browser sidecars actually need local/editor state. | | `roice3/Magic120Cell` | `MIT` | Locked Strategic Donor | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 1R` closed. Retain as a `Phase 3R` permissive implementation candidate; implement only from the packet authority for this row and the retained-set contract. | | `roice3/MagicCube5D` | `MIT` | Locked Strategic Donor | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 1R` closed. Retain as a `Phase 3R` permissive implementation candidate; implement only from the packet authority for this row and the retained-set contract. | @@ -242,8 +248,8 @@ Count: `12` ## Implementation rule going forward -- Preserve the eleven landed lanes as current truth. +- Preserve the fourteen landed lanes as current truth. - Keep `onionhoney/roux-trainers` explicitly marked as the only currently verified restrictive clean-room lane already implemented. -- `Phase 0R` is now fully closed for the remaining `60` non-live rows. +- `Phase 0R` is now fully closed for the remaining `57` non-live rows. - `Phase 1R` is now the routing authority for retained-set widening and benchmark exclusion. -- The next bounded move is `Phase 3R-F` for the retained `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` browser `3D`, XR session, and spatial-support lane. +- The next bounded move is `Phase 4R-A` for the retained `cubing/cubing.js` `MPL`-aware dependency or adapter lane, while the optional `Phase 3R-G` browser comparison lane remains deferred unless the landed primary browser spatial stack exposes a real gap. diff --git a/docs/HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md b/docs/HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md index 708215e..20438e0 100644 --- a/docs/HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md +++ b/docs/HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md @@ -30,16 +30,16 @@ Implication: Current verified truth: - current curated HyperTwist shallow-eval set: `71` repos -- currently verified live/implemented in checked `UnrealHyperTwist` surfaces: `6` -- permissive already live: `5` +- currently verified live/implemented in checked `UnrealHyperTwist` surfaces: `14` +- permissive already live: `13` - restrictive already live through proper clean-room implementation: `1` - the restrictive landed repo is `onionhoney/roux-trainers` -- the remaining `65` are not yet to be treated as already implemented +- the remaining `57` are not yet to be treated as already implemented Implication: -- future roadmap widening must not assume Phase `0` and Phase `1` are closed strongly enough for the remaining donor portfolio -- the correct next move is a deliberate `Phase 0R` repo deep source integration evaluation reset, followed by `Phase 1R` contract and handoff overhaul +- future roadmap widening must continue from the closed `Phase 0R`, `Phase 1R`, `Phase 2R`, and `Phase 3R-A` through `Phase 3R-F` authority stack rather than from the pre-reset phase ordering +- the correct next move is `Phase 4R-A` for `cubing/cubing.js`, with the optional `Phase 3R-G` browser comparison lane still deferred unless the landed primary browser spatial stack exposes a real gap ## Product-level call @@ -93,10 +93,10 @@ Current correction call from the source-exposed audit, current execution refresh - preserve the roadmap direction - update the canonical planning docs so they reflect: - - the verified implementation truth that only `6` of the current `71` HyperTwist repos are live right now in checked Unreal surfaces - - the fact that `5` of those `6` are permissive `MIT` lanes + - the verified implementation truth that `14` of the current `71` HyperTwist repos are live right now in checked Unreal surfaces + - the fact that `13` of those `14` are permissive lanes - the fact that `onionhoney/roux-trainers` is the only currently verified restrictive repo that was properly clean-roomed and then implemented - - the fact that the remaining `65` require repo deep source integration evaluation before new widening work should assume they are implementation-ready + - the fact that the remaining `57` are still not live, with `45` active implementation-board rows plus `9` retained benchmark/oracle rows outside that board - the reconciled `14`-family feature set - manifest and custody governance gaps - pre-Phase-5 speech governance gates @@ -125,7 +125,7 @@ Current correction call from the source-exposed audit, current execution refresh - selected high-value permissive repos are not just inspiration; they are intended full implementation targets inside first-party HyperTwist, executed packet by packet rather than through one bulk import event - selected high-value restrictive repos are not just archival references; they are intended clean-room implementation targets when they remain selected after portfolio triage - donor or reference status does not by itself mean a selected repo is discarded; selected repos may still be full implementation targets, bounded donor lanes, bounded clean-room lanes, or benchmark/reference lanes depending on phase and licensing posture -- repo-portfolio intake/classification, mirror custody boundaries, model allowlists, and first-pass donor evaluation do exist, but the stronger repo-by-repo deep source integration closure needed for safe future widening is not closed for the remaining `65` +- repo-portfolio intake/classification, mirror custody boundaries, model allowlists, and repo-by-repo deep source integration closure are now closed through `Phase 0R` and `Phase 1R` for the current retained set, but the remaining `57` non-live rows still require packet-disciplined widening - owned contract extraction from chosen donors is materially present in landed first-party code, but the contract/handoff layer now needs a deliberate `Phase 1R` overhaul so it reflects only the verified landed set plus the retained post-evaluation backlog - portfolio-level sorting/classification is largely done, but deep source-level audit of every still-selected repo is not globally closed and must now be resumed as a first-class reset packet rather than treated as incidental background work - clean-room work belongs first to governance and contract shaping, then to bounded first-party implementation; at the moment, `onionhoney/roux-trainers` is the only currently verified restrictive repo that has both a proper clean-room chain and a landed implementation surface diff --git a/docs/REPO_LICENSE_TRACKING.md b/docs/REPO_LICENSE_TRACKING.md index 67d7127..a4dd140 100644 --- a/docs/REPO_LICENSE_TRACKING.md +++ b/docs/REPO_LICENSE_TRACKING.md @@ -53,17 +53,20 @@ Do not use it as the primary architecture ledger. The architecture and donor dec This file now also preserves the current truth that future models must not lose: - current curated HyperTwist shallow-eval set: `71` repos -- currently verified live/implemented in checked `UnrealHyperTwist` surfaces: `11` -- permissive live lanes: `10` +- currently verified live/implemented in checked `UnrealHyperTwist` surfaces: `14` +- permissive live lanes: `13` - restrictive live lanes: `1` -The ten permissive live lanes are: +The thirteen permissive live lanes are: - `Aarav2709/KubeTimr` - `apache/echarts` - `abunickabhi/5style-Trainer` - `google/model-viewer` - `Hypercubers/hypercubing.xyz` +- `mrdoob/three.js` +- `pmndrs/react-three-fiber` +- `pmndrs/xr` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` - `met4citizen/TalkingHead` @@ -87,7 +90,7 @@ Interpretation rule: Reset rule: -- preserve the nine landed/live lanes +- preserve the fourteen landed/live lanes - do not treat the remaining non-live rows as already absorbed - route all non-live rows only through the closed `Phase 1R` retained-set contract and the relevant `0R-*` packet @@ -119,7 +122,8 @@ Current practical interpretation: - the landed `apache/echarts` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md` - the landed `google/model-viewer` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md` - the landed `met4citizen/TalkingHead` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md` -- the next bounded move is `Phase 3R-F` +- the landed `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md` +- the next bounded move is `Phase 4R-A` Companion docs: @@ -133,6 +137,7 @@ Companion docs: - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md` - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md` +- `docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md` - `docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md` ## Landed live-lane legal records @@ -1833,12 +1838,13 @@ Approved working posture: Decision date: - `2026-04-24` +- refreshed on `2026-05-13` Current licensing judgment: - repo code is usable for HyperTwist under `MIT` - not a clean-room case -- treat as a commodity browser `3D` substrate and strategic dependency beneath multiple browser-side lanes +- treat as the landed permissive browser `3D` substrate preserve lane through `Phase 3R-F` Source basis: @@ -1861,7 +1867,8 @@ Important distinction: Approved working posture: - HyperTwist may use the repo directly under the `MIT` code posture -- treat it as a commodity strategic dependency for browser-side `3D` work +- preserve it as the landed first-party browser `3D` substrate lane +- future widening should start from the live-lane audit, then `HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`, then this file - keep it beneath the higher-level browser packages and do not let it get mistaken for HyperTwist's owned runtime foundation ### `pmndrs/postprocessing` @@ -1941,12 +1948,13 @@ Approved working posture: Decision date: - `2026-04-24` +- refreshed on `2026-05-13` Current licensing judgment: - repo code is usable for HyperTwist under `MIT` - not a clean-room case -- treat as the commodity React renderer substrate above `mrdoob/three.js` +- treat as the landed permissive React-side browser renderer preserve lane through `Phase 3R-F` Source basis: @@ -1972,7 +1980,8 @@ Important distinction: Approved working posture: - HyperTwist may use the repo directly under the `MIT` code posture -- treat it as the React-side renderer substrate above `mrdoob/three.js` +- preserve it as the landed first-party React-side browser renderer lane +- future widening should start from the live-lane audit, then `HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`, then this file - keep it beneath the higher-level browser-side support packages and do not let it get mistaken for a gameplay, simulation, or runtime-foundation lane ### `pmndrs/drei` @@ -2018,12 +2027,13 @@ Approved working posture: Decision date: - `2026-04-24` +- refreshed on `2026-05-13` Current licensing judgment: - repo code is usable for HyperTwist under `MIT` - not a clean-room case -- treat as a strategic donor for browser XR interaction and immersive UI substrate +- treat as the landed permissive browser XR session and immersive interaction preserve lane through `Phase 3R-F` Source basis: @@ -2049,7 +2059,8 @@ Important distinction: Approved working posture: - HyperTwist may use the repo directly under the `MIT` code posture -- treat it as the strongest current browser XR interaction donor in the set +- preserve it as the landed first-party browser XR session and immersive interaction lane +- future widening should start from the live-lane audit, then `HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`, then this file - keep it in the browser XR and immersive-support lane, and do not let it get mistaken for a gameplay, simulation, or runtime-foundation lane ### `pmndrs/uikit` diff --git a/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv b/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv index 0b5d533..18d8c9f 100644 --- a/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv +++ b/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv @@ -1,76 +1,76 @@ -repo,primary_url,best_fit_project_v2,phase_g_bucket,portfolio_role_v3,recommended_action_v2,repurposing_potential_v2,v6_license_annotation,v6_license_annotation_status,v6_license_annotation_source,copyleft_relevance_v6_1,copyleft_strategy_v6_1,copyleft_rationale_v6_1,copyleft_strategy_confidence_v6_1,copyleft_manual_review_trigger_v6_1,v6_3_source_of_truth,v6_3_live_state_2026_05_11,v6_3_reset_lane_2026_05_11,v6_3_reset_next_step_2026_05_11 -HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,,locked core candidate,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.",high,model-artifact-review-required,v6.3_final_source_of_truth,,, -cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,Donor Bench,donor bench,repurpose,architecture only,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,high,gpl-clean-room-donor,v6.3_final_source_of_truth,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract. -cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,Donor Bench,donor bench,repurpose,architecture only,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",high,gpl-clean-room-donor,v6.3_final_source_of_truth,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract. -HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,Donor Bench,donor bench,repurpose,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.,high,gpl-clean-room-donor,v6.3_final_source_of_truth,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier. -kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,,locked core candidate,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,,donor bench,repurpose,moderate modification,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.",medium,model-license-selection-required,v6.3_final_source_of_truth,,, -vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,Locked Parallel Foundation,locked core candidate,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.,high,model-artifact-review-recommended,v6.3_final_source_of_truth,,, -tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,,locked core candidate,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -rhasspy/piper,https://github.com/rhasspy/piper,multi-project,,donor bench,repurpose,moderate modification,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",high,voice-artifact-review-required,v6.3_final_source_of_truth,,, -cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,Locked Strategic Donor,locked strategic donor,integrate,direct,MPL-2.0 OR GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,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.",high,dual-license-boundary-review,v6.3_final_source_of_truth,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable. -cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,Locked Strategic Donor,locked strategic donor,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,Locked Strategic Donor,locked strategic donor,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,Locked Strategic Donor,locked strategic donor,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,Locked Strategic Donor,locked strategic donor,integrate,direct,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,architecture only,GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.",high,license-contradiction-clean-room-donor,v6.3_final_source_of_truth,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,"Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." -cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,moderate modification,Custom broad-use license with attribution requested,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,direct_incorporation_ok,"The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.",medium,custom-license-attribution-review,v6.3_final_source_of_truth,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly. -roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,high,permissive-specialized-donor,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,high,permissive-specialized-donor,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -cs0x7f/cstimer,https://github.com/cs0x7f/cstimer,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.",high,gpl-timer-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle. -aMonteSl/CodeXR,https://github.com/aMonteSl/CodeXR,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0-only,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,pattern_only_preferred,The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.,high,gpl-reference-only-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows. -brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,pattern_only_preferred,The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.,high,strategic-or-implemented-component,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope. -abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -MathewKJ2048/Rubiks-cube-simulator,https://github.com/MathewKJ2048/Rubiks-cube-simulator,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.",high,gpl-clean-room-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." -NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,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.",high,below-core-mit-donor,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -ShellPuppy/RCube,https://github.com/ShellPuppy/RCube,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.",high,gpl-large-n-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." -brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,high,gpl-oracle-clean-room-review,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." -newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubiks-cross-trainer,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -vwcwong/CubeSim,https://github.com/vwcwong/CubeSim,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.,high,gpl-clean-room-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use. -AviKaufman/Rubix-cube-trainer,https://github.com/AviKaufman/Rubix-cube-trainer,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,All Rights Reserved,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.,high,all-rights-reserved-clean-room-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design. -alinen/cube,https://github.com/alinen/cube,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,license_unknown_pending,reverse_engineer_preferred,No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.,medium,no-license-clean-room-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly." -ambisinister/blindsolve,https://github.com/ambisinister/blindsolve,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,license_unknown_pending,reverse_engineer_preferred,No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.,medium,no-license-clean-room-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only." -efrantar/rob-twophase,https://github.com/efrantar/rob-twophase,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code.",high,gpl-solver-oracle-benchmark,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code." -onionhoney/roux-trainers,https://github.com/onionhoney/roux-trainers,HyperTwist,Donor Bench,donor bench,repurpose,architecture only,GPL-3.0,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is 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.,high,gpl-clean-room-donor,v6.3_final_source_of_truth,implemented_live_clean_room_verified,landed_clean_room_preserve,Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs. -yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,Reserve Bench,Reserve Bench,future candidate,architecture only,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,pattern_only_preferred,"The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.",high,strategic-or-implemented-component,v6.3_final_source_of_truth,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." -Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.,high,permissive-knowledge-donor,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." -Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.",high,routine-review-only,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." -roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,high,permissive-top-tier-donor,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,,donor bench,repurpose,moderate modification,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.",high,mixed-license-path-review-required,v6.3_final_source_of_truth,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,high,standard-notice-review,v6.3_markdown_backfill,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." -apache/echarts,https://github.com/apache/echarts,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,high,notice-file-review,v6.3_markdown_backfill,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." -ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." -KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer,https://github.com/google/model-viewer,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,high,notice-file-review,v6.3_markdown_backfill,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." -mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,Zlib,known_from_reference_material,uploaded_reference_docs,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.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,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.,high,mixed-license-path-review-required,v6.3_markdown_backfill,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." -remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,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.,high,commercial-license-sidecar-review,v6.3_markdown_backfill,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use. -ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,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.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live." -pissang/claygl,https://github.com/pissang/claygl,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,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.,medium,license-text-normalization-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,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.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." -google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." -google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,Donor Bench,donor bench,repurpose,architecture only,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",high,mixed-asset-whitelist-review,v6.3_markdown_backfill,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use. -pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"repo","primary_url","best_fit_project_v2","phase_g_bucket","portfolio_role_v3","recommended_action_v2","repurposing_potential_v2","v6_license_annotation","v6_license_annotation_status","v6_license_annotation_source","copyleft_relevance_v6_1","copyleft_strategy_v6_1","copyleft_rationale_v6_1","copyleft_strategy_confidence_v6_1","copyleft_manual_review_trigger_v6_1","v6_3_source_of_truth","v6_3_live_state_2026_05_11","v6_3_reset_lane_2026_05_11","v6_3_reset_next_step_2026_05_11" +"HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","HyperTwist","","locked core candidate","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"SYSTRAN/faster-whisper","https://github.com/SYSTRAN/faster-whisper","multi-project","","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.","high","model-artifact-review-required","v6.3_final_source_of_truth","","","" +"cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","high","gpl-clean-room-donor","v6.3_final_source_of_truth","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","high","gpl-clean-room-donor","v6.3_final_source_of_truth","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"HactarCE/2x2x2x2-Scrambler","https://github.com/HactarCE/2x2x2x2-Scrambler","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.","high","gpl-clean-room-donor","v6.3_final_source_of_truth","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier." +"kkoomen/qbr","https://github.com/kkoomen/qbr","HyperTwist","","locked core candidate","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"coqui-ai/TTS","https://github.com/coqui-ai/TTS","multi-project","","donor bench","repurpose","moderate modification","MPL-2.0 code; mixed model payload licenses","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.","medium","model-license-selection-required","v6.3_final_source_of_truth","","","" +"vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","Locked Parallel Foundation","locked core candidate","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"ggml-org/whisper.cpp","https://github.com/ggml-org/whisper.cpp","multi-project","","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.","high","model-artifact-review-recommended","v6.3_final_source_of_truth","","","" +"tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","","locked core candidate","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"rhasspy/piper","https://github.com/rhasspy/piper","multi-project","","donor bench","repurpose","moderate modification","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","high","voice-artifact-review-required","v6.3_final_source_of_truth","","","" +"cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","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.","high","dual-license-boundary-review","v6.3_final_source_of_truth","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable." +"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","Locked Strategic Donor","locked strategic donor","integrate","direct","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","architecture only","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","high","license-contradiction-clean-room-donor","v6.3_final_source_of_truth","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." +"cutelyaware/magiccube4d","https://github.com/cutelyaware/magiccube4d/tree/master","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","medium","custom-license-attribution-review","v6.3_final_source_of_truth","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly." +"roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","high","permissive-specialized-donor","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","high","permissive-specialized-donor","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"cs0x7f/cstimer","https://github.com/cs0x7f/cstimer","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","high","gpl-timer-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle." +"aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0-only","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","high","gpl-reference-only-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows." +"brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope." +"abunickabhi/5style-Trainer","https://github.com/abunickabhi/5style-Trainer","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"MathewKJ2048/Rubiks-cube-simulator","https://github.com/MathewKJ2048/Rubiks-cube-simulator","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.","high","gpl-clean-room-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." +"NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","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.","high","below-core-mit-donor","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"ShellPuppy/RCube","https://github.com/ShellPuppy/RCube","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","high","gpl-large-n-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." +"brownan/Rubiks-Cube-Solver","https://github.com/brownan/Rubiks-Cube-Solver","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.","high","gpl-oracle-clean-room-review","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." +"newyork-anthonyng/rubiks-cross-trainer","https://github.com/newyork-anthonyng/rubiks-cross-trainer","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"vwcwong/CubeSim","https://github.com/vwcwong/CubeSim","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.","high","gpl-clean-room-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use." +"AviKaufman/Rubix-cube-trainer","https://github.com/AviKaufman/Rubix-cube-trainer","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","All Rights Reserved","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.","high","all-rights-reserved-clean-room-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design." +"alinen/cube","https://github.com/alinen/cube","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.","medium","no-license-clean-room-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly." +"ambisinister/blindsolve","https://github.com/ambisinister/blindsolve","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.","medium","no-license-clean-room-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only." +"efrantar/rob-twophase","https://github.com/efrantar/rob-twophase","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code.","high","gpl-solver-oracle-benchmark","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code." +"onionhoney/roux-trainers","https://github.com/onionhoney/roux-trainers","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","GPL-3.0","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is 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.","high","gpl-clean-room-donor","v6.3_final_source_of_truth","implemented_live_clean_room_verified","landed_clean_room_preserve","Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs." +"yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","Reserve Bench","Reserve Bench","future candidate","architecture only","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.","high","strategic-or-implemented-component","v6.3_final_source_of_truth","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." +"Hypercubers/hypercubing.xyz","https://github.com/Hypercubers/hypercubing.xyz","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.","high","permissive-knowledge-donor","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." +"Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","high","routine-review-only","v6.3_final_source_of_truth","implemented_live_permissive","landed_permissive_preserve","Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." +"roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","Locked Strategic Donor","locked strategic donor","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","high","permissive-top-tier-donor","v6.3_final_source_of_truth","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","","donor bench","repurpose","moderate modification","MIT outside ee/; enterprise-restricted in ee/","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","high","mixed-license-path-review-required","v6.3_final_source_of_truth","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed." +"met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","high","standard-notice-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +"apache/echarts","https://github.com/apache/echarts","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","high","notice-file-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." +"ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." +"KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","high","notice-file-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer","https://github.com/google/model-viewer","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.","high","notice-file-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." +"mrdoob/three.js","https://github.com/mrdoob/three.js","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.","high","standard-notice-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","Zlib","known_from_reference_material","uploaded_reference_docs","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.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser post-effect substrate beneath the landed browser spatial owner trio; do not treat it as separately live." +"pmndrs/react-three-fiber","https://github.com/pmndrs/react-three-fiber","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.","high","standard-notice-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/xr","https://github.com/pmndrs/xr","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.","high","standard-notice-review","v6.3_markdown_backfill","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser spatial UI layer beside the landed pmndrs/xr lane; do not treat it as separately live." +"pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side motion substrate inside the landed browser spatial support stack; do not treat it as separately live." +"screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","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.","high","mixed-license-path-review-required","v6.3_markdown_backfill","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." +"remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","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.","high","commercial-license-sidecar-review","v6.3_markdown_backfill","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use." +"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","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.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live." +"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","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.","medium","license-text-normalization-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","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.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","high","notice-file-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." +"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","high","notice-file-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","high","notice-file-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","high","notice-file-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","Apache-2.0","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","high","notice-file-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." +"google/model-viewer/packages/shared-assets","https://github.com/google/model-viewer/tree/main/packages/shared-assets","HyperTwist","Donor Bench","donor bench","repurpose","architecture only","Apache-2.0 container; mixed per-asset terms","known_from_reference_material","uploaded_reference_docs","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.","high","mixed-asset-whitelist-review","v6.3_markdown_backfill","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use." +"pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate React wrapper above pmndrs/postprocessing inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate shared utility shelf beneath the landed browser spatial owner trio; do not treat it as separately live." +"pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate math-helper layer inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side state substrate inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate authoring and debug control sidecar inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser gesture and pointer-input substrate inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate layered-motion sidecar beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate animatable-component package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","Donor Bench","donor bench","repurpose","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate spring-runtime core beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","Merge Bench","merge bench","integrate","moderate modification","MIT","known_from_reference_material","uploaded_reference_docs","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","high","standard-notice-review","v6.3_markdown_backfill","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate type-contract package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." diff --git a/docs/repo_portfolio_unified_operational_v6_3.csv b/docs/repo_portfolio_unified_operational_v6_3.csv index e92cf8b..3759e49 100644 --- a/docs/repo_portfolio_unified_operational_v6_3.csv +++ b/docs/repo_portfolio_unified_operational_v6_3.csv @@ -1,76 +1,76 @@ -execution_queue_order,repo,primary_url,best_fit_project_v2,project_rank,portfolio_priority_score,execution_priority_score_v3,priority_band,taxonomy_hardened,archetype_primary,archetype_secondary,portfolio_role_v3,recommended_action_v2,repurposing_potential_v2,modification_scope_detail_v3,capability_extract,integration_realization_detail,consolidation_detail,repurpose_detail,realization_checklist,inspection_depth_recommendation,hidden_value_hypothesis,source_inspection_questions,source_code_audit_targets,coding_model_instruction_v3,merger_partner_1,merger_type_1,merger_rationale_1,merger_partner_2,merger_type_2,merger_rationale_2,merger_partner_3,merger_type_3,merger_rationale_3,cross_project_transfer_targets,cross_project_transfer_rationale,exclusion_discipline,exclusion_reasoning_v3,confidence_v3,confidence_rationale_v3,confidence_reassessed,confidence_rationale,licensing_filter_status,bookmark_project_sections,bookmark_heading_paths_top,bookmark_description_sample,memo_signal_sample,expanded_reasoning,source_attachments,in_bookmarks,in_memo,bookmark_occurrences,memo_mentions,cluster_tag,source_audit_packet_id,category_guess_v2,reasoning,best_fit_project,category_guess,recommended_action,repurposing_potential,confidence,_repo_norm,v5_primary_eval_project,v5_runtime_project,v5_scriptorium_override_status,v5_scriptorium_current_reality_status,v5_scriptorium_bucket,v5_scriptorium_stack_layer,v5_scriptorium_source_audit_priority,v5_scriptorium_actual_role,v5_scriptorium_integration_boundary,v5_scriptorium_evidence_summary,v5_scriptorium_design_language_notes,v5_scriptorium_recommended_context_packet,v5_scriptorium_supersedes_prior_assessment,v5_scriptorium_bucket_rank,v5_scriptorium_prio_rank,v5_scriptorium_sort_score,v5_source_of_truth,v6_license_annotation,v6_license_annotation_status,v6_license_annotation_source,v6_supplemental_intake_present,v6_supplemental_source_groups,v6_supplemental_source_sections,v6_supplemental_source_files,v6_reference_material_position,v6_kali_agent_access_relevance,v6_branch_seed_prompt_included,v6_branch_seed_scope,v6_intake_wave,v6_notes,project_rank_num,audit_rank_num,priority_num,phase_g_bucket,phase_g_project_stack_layer,phase_g_inclusion_status,phase_g_source_audit_priority,copyleft_relevance_v6_1,copyleft_strategy_v6_1,copyleft_rationale_v6_1,preferred_boundary_model_v6_1,open_compliance_if_used_as_is_v6_1,reverse_engineer_if_proprietary_core_needed_v6_1,copyleft_strategy_confidence_v6_1,copyleft_manual_review_trigger_v6_1,as_is_incorporation_sensible_v6_1,v6_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 -7701,HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,1.0,160.0,193.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs",HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,6.0,HT_hyper_engine,HT_hyper_engine_0001,hypercubing / nD simulation,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.,multi-project,hypercubing / nD simulation,integrate,direct,medium,hactarce/hyperspeedcube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,1.0,5,160.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,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." -7704,SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,1.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.",huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services,deep source audit,"Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.",Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0001,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,systran/faster-whisper,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,1.0,5,71.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.",Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.,"Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.",Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.,high,model-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -7705,cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.",cubing/alg.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect cubing/alg.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,"Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.",medium,"Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.",medium,Will increase only after direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.,HyperTwist,HyperTwist,,Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.,"cubing/alg.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.",HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0002,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/alg.js,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,,,,no,,,,v6_unified_source_of_truth,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,"Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.",Usually indirect,yes,v6 unified all-project source-of-truth pack,v6_supplemental_intake,New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).,2.0,1,95.0,Donor Bench,Focused restrictive clean-room donor target,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract. -7707,cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.",cubing/twisty.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect cubing/twisty.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,"Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.",medium,"Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.",medium,Will increase only after direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.,HyperTwist,HyperTwist,,Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.,"cubing/twisty.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.",HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0003,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/twisty.js,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,,,,no,,,,v6_unified_source_of_truth,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,"Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.",Usually indirect,yes,v6 unified all-project source-of-truth pack,v6_supplemental_intake,New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).,2.0,1,95.0,Donor Bench,Focused restrictive clean-room donor target,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract. -7709,HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,2.0,63.0,63.0,P2,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P2 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.",HactarCE/2x2x2x2-Scrambler may hide higher-value reusable components in its HactarCE family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect HactarCE/2x2x2x2-Scrambler at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,"Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.",low-to-medium,"Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.",low-to-medium,Will increase only after direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.,HyperTwist,HyperTwist,,Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.,"HactarCE/2x2x2x2-Scrambler enters the corpus through the v6 supplemental intake. It is treated as reserve bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.",HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0004,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.,HyperTwist,puzzle_simulation_training_donor,future candidate,architecture only,low-to-medium,hactarce/2x2x2x2-scrambler,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,,,,no,,,,v6_unified_source_of_truth,GPL-3.0,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,"Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.",Usually indirect,yes,v6 unified all-project source-of-truth pack,v6_supplemental_intake,New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).,2.0,3,63.0,Donor Bench,Focused restrictive clean-room donor target,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier. -7814,kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,2.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0001,computer vision / AR,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,kkoomen/qbr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,2.0,5,158.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,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." -7818,coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,2.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0002,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,coqui-ai/tts,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,2.0,5,71.0,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.",Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.,"Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.",Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.,medium,model-license-selection-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -8543,vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,3.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb",vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.,memo,False,True,0.0,10.0,HT_cube_vision,HT_cube_vision_0002,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,vivaansinghvi07/rubix-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,3.0,5,158.0,Locked Parallel Foundation,Parallel foundation and reconstruction companion donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,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." -8547,ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,3.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.,"Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0003,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,ggml-org/whisper.cpp,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,3.0,5,71.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.,"Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.",Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.,high,model-artifact-review-recommended,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -11766,tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,4.0,156.0,189.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_training_stack,HT_training_stack_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,tao-yu/alg-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,4.0,5,156.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -11769,rhasspy/piper,https://github.com/rhasspy/piper,multi-project,4.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.",Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.,"Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0004,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,rhasspy/piper,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,4.0,5,71.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.,"Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.",Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.,high,voice-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -11771,cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,5.0,152.0,185.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.",Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,"Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,medium-high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,1.0,HT_cube_semantics,HT_cube_semantics_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cubing/cubing.js,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MPL-2.0 OR GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,5.0,5,152.0,Locked Strategic Donor,Boundary-sensitive classic-cubing semantics and rendering donor,,P1,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.",Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.,Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.,Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.,high,dual-license-boundary-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable. -11848,cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,6.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0003,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,cahidenes/rubiks-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,6.0,5,148.0,Locked Strategic Donor,Active recognition-heuristics and validation donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,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." -11852,tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,7.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 7,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.",memo,False,True,0.0,7.0,HT_cube_vision,HT_cube_vision_0004,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,tentone/rubix-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,7.0,5,148.0,Locked Strategic Donor,Active native-CV donor and comparison bench,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,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." -11857,Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,8.0,145.0,171.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0002,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,lykos/cube_trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,8.0,5,145.0,Locked Strategic Donor,Top-tier persistent training-domain donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -11861,poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,9.0,145.0,171.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0016,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,poliva/cubedex,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,9.0,5,145.0,Locked Strategic Donor,Top-tier training UX and smartcube donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -11865,kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,10.0,145.0,171.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked strategic donor,repurpose,architecture only,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source,"kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.",memo,False,True,0.0,4.0,HT_hyper_engine,HT_hyper_engine_0002,cubing / algorithm training,"Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.",HyperTwist,hypercubing / nD simulation,integrate,direct,medium,kash/cubedesk,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,10.0,5,145.0,Locked Strategic Donor,Restrictive clean-room donor target,,P1,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.",Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.,Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.,Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.,high,license-contradiction-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,"Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." -11869,cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,11.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Automatically exported from code.google.com/p/magiccube4d,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Automatically exported from code.google.com/p/magiccube4d,,"cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0003,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cutelyaware/magiccube4d,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,Custom broad-use license with attribution requested,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,11.0,5,122.0,Locked Strategic Donor,"Top-tier 4D interaction, history, and macro donor with attribution obligations",,P1,mixed_or_boundary_sensitive_known,direct_incorporation_ok,"The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.",Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.,"Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.",Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.,medium,custom-license-attribution-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly. -11873,roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,12.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",4D Megaminx Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,4D Megaminx Analogue,,"roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0004,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,roice3/magic120cell,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,12.0,5,122.0,Locked Strategic Donor,Specialized 4D interaction and puzzle-UX donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"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." -11877,roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,13.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",5D Rubik's Cube Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,5D Rubik's Cube Analogue,,"roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0005,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magiccube5d,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,13.0,5,122.0,Locked Strategic Donor,"Specialized 5D cube interaction, progress, and macro donor",,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"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." -11881,cs0x7f/cstimer,https://github.com/cs0x7f/cstimer,HyperTwist,14.0,121.0,147.0,A,gold-standard timer benchmark,benchmark,Gold-standard timer benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.",Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.,"Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,behavior and acceptance-test benchmark review,"Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.,high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.",high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,cs0x7f/cstimer — GPL timer/training platform; keep only as the gold-standard timer benchmark.,"cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.",memo,False,True,0.0,5.0,HT_timer_training,HT_timer_training_0001,Gold-standard timer benchmark,"Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.",HyperTwist,Gold-standard timer benchmark,future candidate,architecture only,medium,cs0x7f/cstimer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,14.0,5,121.0,Reserve Bench,Gold-standard timer benchmark,Included,P2,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.,high,gpl-timer-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle. -11889,aMonteSl/CodeXR,https://github.com/aMonteSl/CodeXR,HyperTwist,16.0,119.0,134.0,B,reference-only XR benchmark,benchmark,Reference-only XR benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.",Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.,"Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.",Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,behavior-level benchmark review,"Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.",Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?,"Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.,high,Source-backed dossier and license verification collapse the old donor thesis.,high,Source-backed dossier and license verification collapse the old donor thesis.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,aMonteSl/CodeXR — GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.,"aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0005,Reference-only XR benchmark,Reference-only XR benchmark for HyperTwist; not a donor lane.,HyperTwist,Reference-only XR benchmark,future candidate,architecture only,medium,amontesl/codexr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0-only,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,16.0,5,119.0,Reserve Bench,Reference-only XR benchmark,Included,P3,mixed_or_boundary_sensitive_known,pattern_only_preferred,The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.,Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-reference-only-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows. -11893,brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,17.0,119.0,134.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 3,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0006,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,brianpeiris/riftsketch,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,17.0,5,119.0,Reserve Bench,XR interaction and spatial-UI bench,,,permissive_or_noncopyleft_known,pattern_only_preferred,The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.,Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope. -11897,abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,18.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0006,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,direct,medium,abunickabhi/5style-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,18.0,5,118.0,Donor Bench,Focused advanced-training donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -11900,MathewKJ2048/Rubiks-cube-simulator,https://github.com/MathewKJ2048/Rubiks-cube-simulator,HyperTwist,19.0,118.0,133.0,B,clean-room simulator benchmark,benchmark,Clean-room simulator benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.,Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in text-command grammar, move-history logging, and timed step playback.",Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.",Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,MathewKJ2048/Rubiks-cube-simulator — GPL-3.0 simulator; keep only as a clean-room simulator benchmark.,"MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.",memo,False,True,0.0,2.0,HT_training_clean_room,HT_training_clean_room_0004,Clean-room simulator benchmark,Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room simulator benchmark,future candidate,architecture only,medium,mathewkj2048/rubiks-cube-simulator,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,19.0,5,118.0,Reserve Bench,Clean-room simulator benchmark,Included,P3,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.",Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." -11903,NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,20.0,118.0,133.0,B,vision / perception / AR,subsystem donor,vision donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.",NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.,memo,False,True,0.0,2.0,HT_cube_vision,HT_cube_vision_0007,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,nuilab/code-vr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,20.0,5,118.0,Donor Bench,XR pedagogy and code-to-scene representation donor,,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,"The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.",Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.,high,below-core-mit-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.,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." -11906,ShellPuppy/RCube,https://github.com/ShellPuppy/RCube,HyperTwist,21.0,118.0,133.0,B,large-N solver benchmark,benchmark,Large-N solver benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.",Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.,Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,algorithm benchmark review,Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.,Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?,"Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,ShellPuppy/RCube — GPL large-N cube solver; keep only as a large-N solver benchmark.,ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.,memo,False,True,0.0,2.0,HT_solver_oracles,HT_solver_oracles_0001,Large-N solver benchmark,"Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.",HyperTwist,Large-N solver benchmark,future candidate,architecture only,medium,shellpuppy/rcube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,21.0,5,118.0,Reserve Bench,Large-N solver benchmark,Included,P3,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.,high,gpl-large-n-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." -11909,brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,22.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0007,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,brownan/rubiks-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,22.0,5,118.0,Reserve Bench,Benchmark oracle and clean-room optimal-solver candidate,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for any later first-party optimal-solver effort.,high,gpl-oracle-clean-room-review,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." -11915,newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubiks-cross-trainer,HyperTwist,24.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,newyork-anthonyng/rubiks-cross-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,24.0,5,118.0,Donor Bench,Focused donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -11918,vwcwong/CubeSim,https://github.com/vwcwong/CubeSim,HyperTwist,25.0,118.0,133.0,B,clean-room state/history benchmark,benchmark,Clean-room state/history benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: cleaner domain architecture for simulator state/history separation, parser/scramble modules, and replay/history behavior suitable for clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party state/history and replay behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in state/history separation, parser/scramble modularity, and replay-oriented architecture.",Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.",Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL simulator code and should remain only as a clean-room state/history benchmark.,high,The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.,high,The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,vwcwong/CubeSim — GPL simulator; keep only as a clean-room state/history benchmark.,"vwcwong/CubeSim is retained only as a clean-room state/history benchmark. Its value is architectural and behavioral, not donor code.",memo,False,True,0.0,2.0,HT_training_clean_room,HT_training_clean_room_0005,Clean-room state/history benchmark,Clean-room state/history benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room state/history benchmark,future candidate,architecture only,medium,vwcwong/cubesim,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,25.0,5,118.0,Reserve Bench,Clean-room state/history benchmark,Included,P3,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.,Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use. -11921,AviKaufman/Rubix-cube-trainer,https://github.com/AviKaufman/Rubix-cube-trainer,HyperTwist,26.0,117.0,132.0,B,clean-room pedagogy benchmark,benchmark,Clean-room pedagogy benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: beginner-method teaching flow, step guidance, and tutorial-state behavior worth preserving through a clean-room spec.",Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in beginner-method pedagogy flow, guidance cadence, and tutorial-state transitions.",Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.",Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is explicitly all-rights-reserved and should remain only as a clean-room pedagogy benchmark.,high,The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.,high,The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,AviKaufman/Rubix-cube-trainer — all rights reserved; keep only as a clean-room pedagogy benchmark.,"AviKaufman/Rubix-cube-trainer is retained only as a clean-room pedagogy benchmark. Its value is in teaching flow and tutorial behavior, not donor code.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0003,Clean-room pedagogy benchmark,Clean-room pedagogy benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room pedagogy benchmark,future candidate,architecture only,medium,avikaufman/rubix-cube-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,26.0,5,117.0,Reserve Bench,Clean-room pedagogy benchmark,Included,P3,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.,Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source or assets directly without separate rights.,Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary.,high,all-rights-reserved-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design. -11924,alinen/cube,https://github.com/alinen/cube,HyperTwist,27.0,117.0,132.0,B,clean-room planner benchmark,benchmark,Clean-room planner benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: guided lesson flow, cube-state handling, and bounded planner/search behavior suitable for first-party clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only.,Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,Hidden value sits in bounded planner/search flow and guided lesson state transitions.,Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.",Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo has no explicit license visible and should remain only as a clean-room planner benchmark.,medium,"The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.",medium,"The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,alinen/cube — no explicit license visible; keep only as a clean-room planner benchmark.,"alinen/cube is retained only as a clean-room planner benchmark. Its useful value is behavioral and architectural, not donor-grade.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0001,Clean-room planner benchmark,Clean-room planner benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room planner benchmark,future candidate,architecture only,medium,alinen/cube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,27.0,5,117.0,Reserve Bench,Clean-room planner benchmark,Included,P3,license_unknown_pending,reverse_engineer_preferred,No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.,Model A may inspect and summarize planner behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source directly without a confirmed license grant.,Yes — this is the preferred path if planner or lesson behavior later proves strategically necessary.,medium,no-license-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room planner benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly." -11927,ambisinister/blindsolve,https://github.com/ambisinister/blindsolve,HyperTwist,28.0,117.0,132.0,B,clean-room BLD memo benchmark,benchmark,Clean-room BLD memo benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Benchmark-only retained value: narrow memo-practice behavior and BLD training flow worth preserving through a clean-room spec.,Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,Hidden value sits in narrow memo-practice flow and user-feedback behavior.,Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.",Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo has no explicit license visible and does not justify donor treatment; retain only as a clean-room memo benchmark.,medium,"The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.",medium,"The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,ambisinister/blindsolve — no explicit license visible; keep only as a clean-room BLD memo benchmark.,"ambisinister/blindsolve is retained only as a clean-room BLD memo benchmark. Its value is in a narrow behavior slice, not in donor code.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0002,Clean-room BLD memo benchmark,Clean-room BLD memo benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room BLD memo benchmark,future candidate,architecture only,medium,ambisinister/blindsolve,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,28.0,5,117.0,Reserve Bench,Clean-room BLD memo benchmark,Included,P3,license_unknown_pending,reverse_engineer_preferred,No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.,Model A may inspect and summarize memo-practice behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source directly without a confirmed license grant.,Yes — this is the preferred path if a memo-practice micro-mode later proves strategically necessary.,medium,no-license-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room BLD memo benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only." -11930,efrantar/rob-twophase,https://github.com/efrantar/rob-twophase,HyperTwist,29.0,117.0,132.0,B,solver oracle / robot-metric benchmark,benchmark,Solver oracle and robot-metric benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: correctness oracle, robot/axial-metric comparisons, multiple-solution search expectations, and pruning-table performance baselines.","Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code.",Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests.,Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,oracle benchmark review,"Hidden value sits in metric handling, pruning-table organization, CLI oracle behavior, and multi-solution search expectations.","Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?","Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.","Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL solver code and should remain only as a correctness/performance oracle and robot-metric benchmark.,high,"Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.",high,"Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,efrantar/rob-twophase — GPL two-phase solver; keep only as solver oracle and robot-metric benchmark.,"efrantar/rob-twophase remains valuable because it is a strong correctness/performance oracle with robot-metric coverage. That value is benchmark authority, not donor code.",memo,False,True,0.0,1.0,HT_solver_oracles,HT_solver_oracles_0002,Solver oracle and robot-metric benchmark,"Solver oracle and robot-metric benchmark for HyperTwist; retained for acceptance testing, not donor use.",HyperTwist,Solver oracle and robot-metric benchmark,future candidate,architecture only,medium,efrantar/rob-twophase,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,29.0,5,117.0,Reserve Bench,Solver oracle and robot-metric benchmark,Included,P2,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code.",Reference only: use as a solver oracle and robot-metric benchmark without direct source incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow oracle behavior later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-solver-oracle-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed solver oracle benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code." -11933,onionhoney/roux-trainers,https://github.com/onionhoney/roux-trainers,HyperTwist,30.0,117.0,132.0,B,method-specific training donor,restrictive donor,clean-room donor,donor bench,repurpose,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Focused restrictive clean-room donor target. Retain the stage-specific training modes, solver-backed analyzer behavior, recognition masking, favorites/batch-drill flow, and 2D/3D training visualization ideas through Model A / Model B separation.","Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code.",Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary.,Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value sits in state-machine-driven training flows, solver-backed analyzer behavior, recognition masking, favorites persistence, and batch-drill mechanics.",Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?,"Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,HyperTwist only,"Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing.","exclude from direct code use, keep as clean-room donor","The repo is GPLv3 and too method-specific for direct incorporation, but it still contains real training/analyzer subsystem value worth preserving through a clean-room donor path.",high,"The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.",high,"The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"onionhoney/roux-trainers — GPLv3 Roux trainer; keep as a focused restrictive clean-room donor, not direct donor code.","onionhoney/roux-trainers remains valuable because it contains stage-specific training-state machines, solver-backed analyzer modes, recognition masking, and batch-drill patterns. That value should flow through a clean-room donor path, not direct incorporation.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0006,Focused restrictive clean-room donor target,"Focused restrictive clean-room donor target for HyperTwist; stronger than a passive benchmark, but still not direct donor code.",HyperTwist,Focused restrictive clean-room donor target,repurpose,architecture only,medium,onionhoney/roux-trainers,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,30.0,5,117.0,Donor Bench,Focused restrictive clean-room donor target,Included,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPLv3 and should not be used as direct donor code in the HyperTwist core. Its value is in selective behavior and subsystem extraction through a clean-room Model A / Model B process.,Model A inspects the restrictive source; Model B implements only from a scrubbed first-party specification and must not access the repo directly.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for selectively reproducing stage-specific training and analyzer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed focused restrictive clean-room donor status.,implemented_live_clean_room_verified,landed_clean_room_preserve,Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs. -11936,yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,31.0,117.0,132.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.",memo,False,True,0.0,1.0,HT_cube_vision,HT_cube_vision_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,yakupbilen/drl-rubiks-cube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,31.0,5,117.0,Reserve Bench,Search/training systems bench,,,permissive_or_noncopyleft_known,pattern_only_preferred,"The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.",Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." -11939,Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,HyperTwist,32.0,92.0,101.0,C,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Website for the Hypercubing community,"Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Website for the Hypercubing community,,"Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0006,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,hypercubers/hypercubing.xyz,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,32.0,5,92.0,Locked Strategic Donor,Knowledge and curriculum donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.,"Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.",Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.,high,permissive-knowledge-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." -11945,Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,34.0,88.0,97.0,C,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium,single-source signal; clear taxonomy; mostly donor/reference role,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0015,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,aarav2709/kubetimr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,34.0,5,88.0,Donor Bench,Focused subsystem donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,routine-review-only,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." -11951,roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,36.0,88.0,97.0,C,infra / runtime / observability / integration,subsystem donor,integration utility,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",Non-euclidean Rubik's Cube Analogues,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API,deep source audit,"Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Non-euclidean Rubik's Cube Analogues,,"roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0007,cubing / algorithm training,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magictile,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,36.0,5,88.0,Locked Strategic Donor,Top-tier non-Euclidean geometry and topology donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"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." -11967,PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,41.0,72.0,81.0,C,telemetry / replay / feature governance,subsystem donor,telemetry donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.",,"PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_control_plane,HT_control_plane_0001,cloud / infra / observability / api,"Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.",HyperTwist,telemetry / replay / feature governance,repurpose,moderate modification,medium,posthog/posthog,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,41.0,5,72.0,,Telemetry / replay / feature-governance donor,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.",Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.,"Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -,met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0001,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,met4citizen/talkinghead,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser embodied coach surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." -,apache/echarts,https://github.com/apache/echarts,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,"Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0002,analytics / visualization / reporting,Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.,HyperTwist,analytics / visualization / reporting,repurpose,moderate modification,medium,apache/echarts,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser analytics and reporting surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-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." -,ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,visualization donor,merge bench,integrate,moderate modification,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,"Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0003,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,ecomfe/echarts-gl,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser 3D analytics and explainer surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,"Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0004,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,khronosgroup/gltf-sample-viewer,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser asset validation and viewer surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer,https://github.com/google/model-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.",,"Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.",,,,"Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0005,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,google/model-viewer,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser 3D presentation and inspection surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,"Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.",Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." -,mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,,"Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,"Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0006,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,mrdoob/three.js,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser 3D substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,"Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0007,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/postprocessing,,,,,,,,,,,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser post-processing substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,"Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0008,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/react-three-fiber,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser React 3D substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,,"Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,"Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0009,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/drei,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser 3D helper and abstraction layer,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,donor bench,repurpose,moderate modification,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,"Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0010,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/xr,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser XR and immersive UI substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,"Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0011,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/uikit,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser spatial UI surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,merge bench,integrate,moderate modification,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",,"Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,"Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0012,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-spring,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser motion and animation layer,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,,,,,capture / replay / support-plane,subsystem donor,support donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0001,support plane / capture / replay,"Repurpose selectively for HyperTwist. Its source-backed role is a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.",HyperTwist,support plane / capture / replay,repurpose,moderate modification,medium,screenpipe/screenpipe,,,,,,,,,,,,,,,,,,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,,,,Donor Bench,"Support-plane capture, history, and replay sidecar",Included,P2,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.,Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.,Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.,"Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." -,remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,,,,,media / rendering / export,subsystem donor,media donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0002,media / rendering / export,"Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.",HyperTwist,media / rendering / export,repurpose,moderate modification,medium,remotion-dev/remotion,,,,,,,,,,,,,,,,,,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md,,,,Donor Bench,Commercially licensed media-export and explainer sidecar,Included,P3,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.,Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.,Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.,Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.,high,commercial-license-sidecar-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use. -,ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0001,browser / 2D / visualization,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",HyperTwist,browser / 2D / visualization,integrate,moderate modification,medium,ecomfe/zrender,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,,,,Merge Bench,Browser 2D render substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,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." -,pissang/claygl,https://github.com/pissang/claygl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0002,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/claygl,,,,,,,,,,,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,,,,Merge Bench,Browser WebGL substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,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." -,pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0003,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/clay-viewer,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,,,,Merge Bench,Browser viewer and editor sidecar,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,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." -,KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0004,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,khronosgroup/gltf-sample-renderer,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,,,,Merge Bench,Browser asset renderer substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." -,google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,editor donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0005,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/space-opera,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,,,,Merge Bench,Browser asset editor and inspection surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,qa donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0006,browser / QA / visual regression,"Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.",HyperTwist,browser / QA / visual regression,integrate,moderate modification,medium,google/model-viewer/packages/render-fidelity-tools,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,,,,Merge Bench,Browser fidelity QA harness,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,effect donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0007,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/model-viewer-effects,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,,,,Merge Bench,Browser emphasis and post-processing extension,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,docs donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0008,documentation / demos / examples,"Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.",HyperTwist,documentation / demos / examples,integrate,moderate modification,medium,google/model-viewer/packages/modelviewer.dev,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,,,,Merge Bench,Browser docs and demo surface,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." -,google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,,,,,asset / fixture / sample pack,subsystem donor,fixture donor,donor bench,repurpose,architecture only,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0009,asset / fixture / sample pack,"Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.",HyperTwist,asset / fixture / sample pack,integrate,moderate modification,medium,google/model-viewer/packages/shared-assets,,,,,,,,,,,,,,,,,,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md,,,,Donor Bench,Boundary-sensitive sample-asset and test-fixture pack,Included,P3,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.,Preserve container notices and review each selected asset attribution or usage condition separately before shipping.,"Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.",high,mixed-asset-whitelist-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use. -,pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0010,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-postprocessing,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,,,,Merge Bench,Browser React effect-wrapper layer,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,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." -,pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0011,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/three-stdlib,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,,,,Merge Bench,Browser 3D utility substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,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." -,pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0012,browser / utilities / math,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",HyperTwist,browser / utilities / math,integrate,moderate modification,medium,pmndrs/maath,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,,,,Merge Bench,Browser math-helper substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,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." -,pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0013,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/zustand,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,,,,Donor Bench,Browser state-management substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,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." -,pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0014,browser / state / interaction,"Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",HyperTwist,browser / state / interaction,integrate,moderate modification,medium,pmndrs/leva,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,,,,Merge Bench,Browser control-panel and parameter UI layer,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,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." -,pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0015,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/use-gesture,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,,,,Donor Bench,Browser gesture and pointer-input substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,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." -,@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0016,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,@react-spring/parallax,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,,,,Merge Bench,Browser layered-motion and explainer sidecar,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,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." -,@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0017,browser / utilities / scheduling,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",HyperTwist,browser / utilities / scheduling,integrate,moderate modification,medium,@react-spring/rafz,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,,,,Merge Bench,Browser frame-loop and scheduling utility,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,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." -,@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0018,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/animated,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,,,,Merge Bench,Browser animatable-component substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,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." -,@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0019,browser / utilities / animation,"Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",HyperTwist,browser / utilities / animation,repurpose,moderate modification,medium,@react-spring/core,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,,,,Donor Bench,Browser spring-runtime core,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,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." -,@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0020,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/shared,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,,,,Merge Bench,Browser motion utility substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,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." -,@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0021,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/types,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,,,,Merge Bench,Browser motion type-contract substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,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." +"execution_queue_order","repo","primary_url","best_fit_project_v2","project_rank","portfolio_priority_score","execution_priority_score_v3","priority_band","taxonomy_hardened","archetype_primary","archetype_secondary","portfolio_role_v3","recommended_action_v2","repurposing_potential_v2","modification_scope_detail_v3","capability_extract","integration_realization_detail","consolidation_detail","repurpose_detail","realization_checklist","inspection_depth_recommendation","hidden_value_hypothesis","source_inspection_questions","source_code_audit_targets","coding_model_instruction_v3","merger_partner_1","merger_type_1","merger_rationale_1","merger_partner_2","merger_type_2","merger_rationale_2","merger_partner_3","merger_type_3","merger_rationale_3","cross_project_transfer_targets","cross_project_transfer_rationale","exclusion_discipline","exclusion_reasoning_v3","confidence_v3","confidence_rationale_v3","confidence_reassessed","confidence_rationale","licensing_filter_status","bookmark_project_sections","bookmark_heading_paths_top","bookmark_description_sample","memo_signal_sample","expanded_reasoning","source_attachments","in_bookmarks","in_memo","bookmark_occurrences","memo_mentions","cluster_tag","source_audit_packet_id","category_guess_v2","reasoning","best_fit_project","category_guess","recommended_action","repurposing_potential","confidence","_repo_norm","v5_primary_eval_project","v5_runtime_project","v5_scriptorium_override_status","v5_scriptorium_current_reality_status","v5_scriptorium_bucket","v5_scriptorium_stack_layer","v5_scriptorium_source_audit_priority","v5_scriptorium_actual_role","v5_scriptorium_integration_boundary","v5_scriptorium_evidence_summary","v5_scriptorium_design_language_notes","v5_scriptorium_recommended_context_packet","v5_scriptorium_supersedes_prior_assessment","v5_scriptorium_bucket_rank","v5_scriptorium_prio_rank","v5_scriptorium_sort_score","v5_source_of_truth","v6_license_annotation","v6_license_annotation_status","v6_license_annotation_source","v6_supplemental_intake_present","v6_supplemental_source_groups","v6_supplemental_source_sections","v6_supplemental_source_files","v6_reference_material_position","v6_kali_agent_access_relevance","v6_branch_seed_prompt_included","v6_branch_seed_scope","v6_intake_wave","v6_notes","project_rank_num","audit_rank_num","priority_num","phase_g_bucket","phase_g_project_stack_layer","phase_g_inclusion_status","phase_g_source_audit_priority","copyleft_relevance_v6_1","copyleft_strategy_v6_1","copyleft_rationale_v6_1","preferred_boundary_model_v6_1","open_compliance_if_used_as_is_v6_1","reverse_engineer_if_proprietary_core_needed_v6_1","copyleft_strategy_confidence_v6_1","copyleft_manual_review_trigger_v6_1","as_is_incorporation_sensible_v6_1","v6_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" +"7701","HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","HyperTwist","1.0","160.0","193.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs","HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","6.0","HT_hyper_engine","HT_hyper_engine_0001","hypercubing / nD simulation","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.","multi-project","hypercubing / nD simulation","integrate","direct","medium","hactarce/hyperspeedcube","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","1.0","5","160.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"7704","SYSTRAN/faster-whisper","https://github.com/SYSTRAN/faster-whisper","multi-project","1.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.","huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.","Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services","deep source audit","Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.","Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.","SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0001","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","systran/faster-whisper","multi-project","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","1.0","5","71.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.","Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.","Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.","high","model-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"7705","cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","2.0","95.0","95.0","P0","puzzle_simulation_training_donor","puzzle_simulation_training_donor","geometry_renderer_or_binding","donor bench","repurpose","architecture only","Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","cubing/alg.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect cubing/alg.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.","medium","Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.","medium","Will increase only after direct source inspection.","Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.","HyperTwist","HyperTwist","","Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.","cubing/alg.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.","HyperTwist & ScriptoriumAI.txt","0","0","1.0","0.0","HT_cube_semantics","HT_cube_semantics_0002","puzzle_simulation_training_donor","Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.","HyperTwist","puzzle_simulation_training_donor","donor candidate","moderate modification","medium","cubing/alg.js","HyperTwist","supplemental_v6_not_runtime_anchored","","","","","","","","","","","no","","","","v6_unified_source_of_truth","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v6_supplemental_intake","New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).","2.0","1","95.0","Donor Bench","Focused restrictive clean-room donor target","","P2","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"7707","cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","2.0","95.0","95.0","P0","puzzle_simulation_training_donor","puzzle_simulation_training_donor","geometry_renderer_or_binding","donor bench","repurpose","architecture only","Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","cubing/twisty.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect cubing/twisty.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.","medium","Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.","medium","Will increase only after direct source inspection.","Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.","HyperTwist","HyperTwist","","Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.","cubing/twisty.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.","HyperTwist & ScriptoriumAI.txt","0","0","1.0","0.0","HT_cube_semantics","HT_cube_semantics_0003","puzzle_simulation_training_donor","Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.","HyperTwist","puzzle_simulation_training_donor","donor candidate","moderate modification","medium","cubing/twisty.js","HyperTwist","supplemental_v6_not_runtime_anchored","","","","","","","","","","","no","","","","v6_unified_source_of_truth","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v6_supplemental_intake","New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).","2.0","1","95.0","Donor Bench","Focused restrictive clean-room donor target","","P2","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"7709","HactarCE/2x2x2x2-Scrambler","https://github.com/HactarCE/2x2x2x2-Scrambler","HyperTwist","2.0","63.0","63.0","P2","puzzle_simulation_training_donor","puzzle_simulation_training_donor","geometry_renderer_or_binding","donor bench","repurpose","architecture only","Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P2 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","HactarCE/2x2x2x2-Scrambler may hide higher-value reusable components in its HactarCE family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect HactarCE/2x2x2x2-Scrambler at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.","low-to-medium","Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.","low-to-medium","Will increase only after direct source inspection.","Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.","HyperTwist","HyperTwist","","Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.","HactarCE/2x2x2x2-Scrambler enters the corpus through the v6 supplemental intake. It is treated as reserve bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.","HyperTwist & ScriptoriumAI.txt","0","0","1.0","0.0","HT_cube_semantics","HT_cube_semantics_0004","puzzle_simulation_training_donor","Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.","HyperTwist","puzzle_simulation_training_donor","future candidate","architecture only","low-to-medium","hactarce/2x2x2x2-scrambler","HyperTwist","supplemental_v6_not_runtime_anchored","","","","","","","","","","","no","","","","v6_unified_source_of_truth","GPL-3.0","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v6_supplemental_intake","New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).","2.0","3","63.0","Donor Bench","Focused restrictive clean-room donor target","","P2","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier." +"7814","kkoomen/qbr","https://github.com/kkoomen/qbr","HyperTwist","2.0","158.0","191.0","A","vision / perception / AR","foundation engine","vision donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0001","computer vision / AR","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.","multi-project","computer vision / AR","integrate","heavy modification","medium","kkoomen/qbr","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","2.0","5","158.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"7818","coqui-ai/TTS","https://github.com/coqui-ai/TTS","multi-project","2.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","https://github.com/coqui-ai/TTS – Coqui XTTS v2.","Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","https://github.com/coqui-ai/TTS – Coqui XTTS v2.","coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0002","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","coqui-ai/tts","multi-project","","","","","","","","","","","","","","","","Original global operational v3 retained","MPL-2.0 code; mixed model payload licenses","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","2.0","5","71.0","","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.","Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.","Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.","Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.","medium","model-license-selection-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"8543","vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","3.0","158.0","191.0","A","vision / perception / AR","foundation engine","vision donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb","vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.","memo","False","True","0.0","10.0","HT_cube_vision","HT_cube_vision_0002","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","vivaansinghvi07/rubix-cube-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","3.0","5","158.0","Locked Parallel Foundation","Parallel foundation and reconstruction companion donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"8547","ggml-org/whisper.cpp","https://github.com/ggml-org/whisper.cpp","multi-project","3.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.","Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.","Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.","ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0003","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","ggml-org/whisper.cpp","multi-project","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","3.0","5","71.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.","Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.","Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.","high","model-artifact-review-recommended","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"11766","tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","4.0","156.0","189.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","5.0","HT_training_stack","HT_training_stack_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","tao-yu/alg-trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","4.0","5","156.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"11769","rhasspy/piper","https://github.com/rhasspy/piper","multi-project","4.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0004","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","rhasspy/piper","multi-project","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","4.0","5","71.0","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.","Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.","Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.","high","voice-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"11771","cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","5.0","152.0","185.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","medium-high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","1.0","HT_cube_semantics","HT_cube_semantics_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","cubing/cubing.js","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","5.0","5","152.0","Locked Strategic Donor","Boundary-sensitive classic-cubing semantics and rendering donor","","P1","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable." +"11848","cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","6.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0003","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","cahidenes/rubiks-cube-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","6.0","5","148.0","Locked Strategic Donor","Active recognition-heuristics and validation donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11852","tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","7.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 7","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.","memo","False","True","0.0","7.0","HT_cube_vision","HT_cube_vision_0004","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","tentone/rubix-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","7.0","5","148.0","Locked Strategic Donor","Active native-CV donor and comparison bench","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11857","Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","8.0","145.0","171.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0002","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","lykos/cube_trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","8.0","5","145.0","Locked Strategic Donor","Top-tier persistent training-domain donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"11861","poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","9.0","145.0","171.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0016","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","poliva/cubedex","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","9.0","5","145.0","Locked Strategic Donor","Top-tier training UX and smartcube donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"11865","kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","10.0","145.0","171.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked strategic donor","repurpose","architecture only","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source","kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.","memo","False","True","0.0","4.0","HT_hyper_engine","HT_hyper_engine_0002","cubing / algorithm training","Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.","HyperTwist","hypercubing / nD simulation","integrate","direct","medium","kash/cubedesk","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","10.0","5","145.0","Locked Strategic Donor","Restrictive clean-room donor target","","P1","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." +"11869","cutelyaware/magiccube4d","https://github.com/cutelyaware/magiccube4d/tree/master","HyperTwist","11.0","122.0","137.0","A","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","Automatically exported from code.google.com/p/magiccube4d","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","Automatically exported from code.google.com/p/magiccube4d","","cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0003","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","cutelyaware/magiccube4d","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","11.0","5","122.0","Locked Strategic Donor","Top-tier 4D interaction, history, and macro donor with attribution obligations","","P1","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.","Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.","Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.","medium","custom-license-attribution-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly." +"11873","roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","12.0","122.0","137.0","A","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","4D Megaminx Analogue","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","4D Megaminx Analogue","","roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0004","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.","HyperTwist","hypercubing / nD simulation","integrate","heavy modification","medium","roice3/magic120cell","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","12.0","5","122.0","Locked Strategic Donor","Specialized 4D interaction and puzzle-UX donor","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11877","roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","13.0","122.0","137.0","A","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","5D Rubik's Cube Analogue","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","5D Rubik's Cube Analogue","","roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0005","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","roice3/magiccube5d","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","13.0","5","122.0","Locked Strategic Donor","Specialized 5D cube interaction, progress, and macro donor","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11881","cs0x7f/cstimer","https://github.com/cs0x7f/cstimer","HyperTwist","14.0","121.0","147.0","A","gold-standard timer benchmark","benchmark","Gold-standard timer benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.","Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.","Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","behavior and acceptance-test benchmark review","Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.","high","Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","high","Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cs0x7f/cstimer — GPL timer/training platform; keep only as the gold-standard timer benchmark.","cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.","memo","False","True","0.0","5.0","HT_timer_training","HT_timer_training_0001","Gold-standard timer benchmark","Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.","HyperTwist","Gold-standard timer benchmark","future candidate","architecture only","medium","cs0x7f/cstimer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","14.0","5","121.0","Reserve Bench","Gold-standard timer benchmark","Included","P2","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.","high","gpl-timer-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle." +"11889","aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","16.0","119.0","134.0","B","reference-only XR benchmark","benchmark","Reference-only XR benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.","Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.","Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","behavior-level benchmark review","Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.","Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?","Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.","high","Source-backed dossier and license verification collapse the old donor thesis.","high","Source-backed dossier and license verification collapse the old donor thesis.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","aMonteSl/CodeXR — GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.","aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.","memo","False","True","0.0","3.0","HT_cube_vision","HT_cube_vision_0005","Reference-only XR benchmark","Reference-only XR benchmark for HyperTwist; not a donor lane.","HyperTwist","Reference-only XR benchmark","future candidate","architecture only","medium","amontesl/codexr","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0-only","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","16.0","5","119.0","Reserve Bench","Reference-only XR benchmark","Included","P3","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-reference-only-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows." +"11893","brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","17.0","119.0","134.0","B","vision / perception / AR","subsystem donor","vision donor","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 3","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.","memo","False","True","0.0","3.0","HT_cube_vision","HT_cube_vision_0006","cubing / algorithm training","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.","multi-project","computer vision / AR","integrate","heavy modification","medium","brianpeiris/riftsketch","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","17.0","5","119.0","Reserve Bench","XR interaction and spatial-UI bench","","","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.","Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope." +"11897","abunickabhi/5style-Trainer","https://github.com/abunickabhi/5style-Trainer","HyperTwist","18.0","118.0","133.0","B","cubing trainer / solver / timing","subsystem donor","training donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","strong adjacency to identified core stack; memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).","abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0006","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","direct","medium","abunickabhi/5style-trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","18.0","5","118.0","Donor Bench","Focused advanced-training donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"11900","MathewKJ2048/Rubiks-cube-simulator","https://github.com/MathewKJ2048/Rubiks-cube-simulator","HyperTwist","19.0","118.0","133.0","B","clean-room simulator benchmark","benchmark","Clean-room simulator benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.","Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.","Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in text-command grammar, move-history logging, and timed step playback.","Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?","Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.","Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.","high","The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.","high","The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","MathewKJ2048/Rubiks-cube-simulator — GPL-3.0 simulator; keep only as a clean-room simulator benchmark.","MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.","memo","False","True","0.0","2.0","HT_training_clean_room","HT_training_clean_room_0004","Clean-room simulator benchmark","Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room simulator benchmark","future candidate","architecture only","medium","mathewkj2048/rubiks-cube-simulator","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","19.0","5","118.0","Reserve Bench","Clean-room simulator benchmark","Included","P3","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.","Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." +"11903","NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","20.0","118.0","133.0","B","vision / perception / AR","subsystem donor","vision donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.","memo","False","True","0.0","2.0","HT_cube_vision","HT_cube_vision_0007","cubing / algorithm training","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.","multi-project","computer vision / AR","integrate","heavy modification","medium","nuilab/code-vr","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","20.0","5","118.0","Donor Bench","XR pedagogy and code-to-scene representation donor","","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11906","ShellPuppy/RCube","https://github.com/ShellPuppy/RCube","HyperTwist","21.0","118.0","133.0","B","large-N solver benchmark","benchmark","Large-N solver benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.","Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.","Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","algorithm benchmark review","Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.","Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?","Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.","high","Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.","high","Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","ShellPuppy/RCube — GPL large-N cube solver; keep only as a large-N solver benchmark.","ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.","memo","False","True","0.0","2.0","HT_solver_oracles","HT_solver_oracles_0001","Large-N solver benchmark","Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.","HyperTwist","Large-N solver benchmark","future candidate","architecture only","medium","shellpuppy/rcube","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","21.0","5","118.0","Reserve Bench","Large-N solver benchmark","Included","P3","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.","high","gpl-large-n-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." +"11909","brownan/Rubiks-Cube-Solver","https://github.com/brownan/Rubiks-Cube-Solver","HyperTwist","22.0","118.0","133.0","B","cubing trainer / solver / timing","subsystem donor","training donor","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.","brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0007","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","brownan/rubiks-cube-solver","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","22.0","5","118.0","Reserve Bench","Benchmark oracle and clean-room optimal-solver candidate","","P2","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.","Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for any later first-party optimal-solver effort.","high","gpl-oracle-clean-room-review","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." +"11915","newyork-anthonyng/rubiks-cross-trainer","https://github.com/newyork-anthonyng/rubiks-cross-trainer","HyperTwist","24.0","118.0","133.0","B","cubing trainer / solver / timing","subsystem donor","training donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.","newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0008","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","newyork-anthonyng/rubiks-cross-trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","24.0","5","118.0","Donor Bench","Focused donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"11918","vwcwong/CubeSim","https://github.com/vwcwong/CubeSim","HyperTwist","25.0","118.0","133.0","B","clean-room state/history benchmark","benchmark","Clean-room state/history benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: cleaner domain architecture for simulator state/history separation, parser/scramble modules, and replay/history behavior suitable for clean-room reimplementation.","Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party state/history and replay behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in state/history separation, parser/scramble modularity, and replay-oriented architecture.","Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?","Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.","Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL simulator code and should remain only as a clean-room state/history benchmark.","high","The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.","high","The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","vwcwong/CubeSim — GPL simulator; keep only as a clean-room state/history benchmark.","vwcwong/CubeSim is retained only as a clean-room state/history benchmark. Its value is architectural and behavioral, not donor code.","memo","False","True","0.0","2.0","HT_training_clean_room","HT_training_clean_room_0005","Clean-room state/history benchmark","Clean-room state/history benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room state/history benchmark","future candidate","architecture only","medium","vwcwong/cubesim","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","25.0","5","118.0","Reserve Bench","Clean-room state/history benchmark","Included","P3","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.","Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use." +"11921","AviKaufman/Rubix-cube-trainer","https://github.com/AviKaufman/Rubix-cube-trainer","HyperTwist","26.0","117.0","132.0","B","clean-room pedagogy benchmark","benchmark","Clean-room pedagogy benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: beginner-method teaching flow, step guidance, and tutorial-state behavior worth preserving through a clean-room spec.","Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in beginner-method pedagogy flow, guidance cadence, and tutorial-state transitions.","Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?","Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.","Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is explicitly all-rights-reserved and should remain only as a clean-room pedagogy benchmark.","high","The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.","high","The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AviKaufman/Rubix-cube-trainer — all rights reserved; keep only as a clean-room pedagogy benchmark.","AviKaufman/Rubix-cube-trainer is retained only as a clean-room pedagogy benchmark. Its value is in teaching flow and tutorial behavior, not donor code.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0003","Clean-room pedagogy benchmark","Clean-room pedagogy benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room pedagogy benchmark","future candidate","architecture only","medium","avikaufman/rubix-cube-trainer","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","26.0","5","117.0","Reserve Bench","Clean-room pedagogy benchmark","Included","P3","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.","Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source or assets directly without separate rights.","Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary.","high","all-rights-reserved-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design." +"11924","alinen/cube","https://github.com/alinen/cube","HyperTwist","27.0","117.0","132.0","B","clean-room planner benchmark","benchmark","Clean-room planner benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: guided lesson flow, cube-state handling, and bounded planner/search behavior suitable for first-party clean-room reimplementation.","Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only.","Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in bounded planner/search flow and guided lesson state transitions.","Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?","Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.","Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo has no explicit license visible and should remain only as a clean-room planner benchmark.","medium","The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.","medium","The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","alinen/cube — no explicit license visible; keep only as a clean-room planner benchmark.","alinen/cube is retained only as a clean-room planner benchmark. Its useful value is behavioral and architectural, not donor-grade.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0001","Clean-room planner benchmark","Clean-room planner benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room planner benchmark","future candidate","architecture only","medium","alinen/cube","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","27.0","5","117.0","Reserve Bench","Clean-room planner benchmark","Included","P3","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.","Model A may inspect and summarize planner behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source directly without a confirmed license grant.","Yes — this is the preferred path if planner or lesson behavior later proves strategically necessary.","medium","no-license-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room planner benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly." +"11927","ambisinister/blindsolve","https://github.com/ambisinister/blindsolve","HyperTwist","28.0","117.0","132.0","B","clean-room BLD memo benchmark","benchmark","Clean-room BLD memo benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: narrow memo-practice behavior and BLD training flow worth preserving through a clean-room spec.","Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in narrow memo-practice flow and user-feedback behavior.","Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?","Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.","Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo has no explicit license visible and does not justify donor treatment; retain only as a clean-room memo benchmark.","medium","The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.","medium","The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","ambisinister/blindsolve — no explicit license visible; keep only as a clean-room BLD memo benchmark.","ambisinister/blindsolve is retained only as a clean-room BLD memo benchmark. Its value is in a narrow behavior slice, not in donor code.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0002","Clean-room BLD memo benchmark","Clean-room BLD memo benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room BLD memo benchmark","future candidate","architecture only","medium","ambisinister/blindsolve","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","28.0","5","117.0","Reserve Bench","Clean-room BLD memo benchmark","Included","P3","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.","Model A may inspect and summarize memo-practice behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source directly without a confirmed license grant.","Yes — this is the preferred path if a memo-practice micro-mode later proves strategically necessary.","medium","no-license-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room BLD memo benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only." +"11930","efrantar/rob-twophase","https://github.com/efrantar/rob-twophase","HyperTwist","29.0","117.0","132.0","B","solver oracle / robot-metric benchmark","benchmark","Solver oracle and robot-metric benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: correctness oracle, robot/axial-metric comparisons, multiple-solution search expectations, and pruning-table performance baselines.","Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code.","Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests.","Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","oracle benchmark review","Hidden value sits in metric handling, pruning-table organization, CLI oracle behavior, and multi-solution search expectations.","Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?","Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.","Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL solver code and should remain only as a correctness/performance oracle and robot-metric benchmark.","high","Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.","high","Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","efrantar/rob-twophase — GPL two-phase solver; keep only as solver oracle and robot-metric benchmark.","efrantar/rob-twophase remains valuable because it is a strong correctness/performance oracle with robot-metric coverage. That value is benchmark authority, not donor code.","memo","False","True","0.0","1.0","HT_solver_oracles","HT_solver_oracles_0002","Solver oracle and robot-metric benchmark","Solver oracle and robot-metric benchmark for HyperTwist; retained for acceptance testing, not donor use.","HyperTwist","Solver oracle and robot-metric benchmark","future candidate","architecture only","medium","efrantar/rob-twophase","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","29.0","5","117.0","Reserve Bench","Solver oracle and robot-metric benchmark","Included","P2","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code.","Reference only: use as a solver oracle and robot-metric benchmark without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow oracle behavior later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-solver-oracle-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed solver oracle benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code." +"11933","onionhoney/roux-trainers","https://github.com/onionhoney/roux-trainers","HyperTwist","30.0","117.0","132.0","B","method-specific training donor","restrictive donor","clean-room donor","donor bench","repurpose","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Focused restrictive clean-room donor target. Retain the stage-specific training modes, solver-backed analyzer behavior, recognition masking, favorites/batch-drill flow, and 2D/3D training visualization ideas through Model A / Model B separation.","Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code.","Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary.","Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value sits in state-machine-driven training flows, solver-backed analyzer behavior, recognition masking, favorites persistence, and batch-drill mechanics.","Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?","Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","HyperTwist only","Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing.","exclude from direct code use, keep as clean-room donor","The repo is GPLv3 and too method-specific for direct incorporation, but it still contains real training/analyzer subsystem value worth preserving through a clean-room donor path.","high","The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.","high","The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","onionhoney/roux-trainers — GPLv3 Roux trainer; keep as a focused restrictive clean-room donor, not direct donor code.","onionhoney/roux-trainers remains valuable because it contains stage-specific training-state machines, solver-backed analyzer modes, recognition masking, and batch-drill patterns. That value should flow through a clean-room donor path, not direct incorporation.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0006","Focused restrictive clean-room donor target","Focused restrictive clean-room donor target for HyperTwist; stronger than a passive benchmark, but still not direct donor code.","HyperTwist","Focused restrictive clean-room donor target","repurpose","architecture only","medium","onionhoney/roux-trainers","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","30.0","5","117.0","Donor Bench","Focused restrictive clean-room donor target","Included","P2","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPLv3 and should not be used as direct donor code in the HyperTwist core. Its value is in selective behavior and subsystem extraction through a clean-room Model A / Model B process.","Model A inspects the restrictive source; Model B implements only from a scrubbed first-party specification and must not access the repo directly.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for selectively reproducing stage-specific training and analyzer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed focused restrictive clean-room donor status.","implemented_live_clean_room_verified","landed_clean_room_preserve","Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs." +"11936","yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","31.0","117.0","132.0","B","vision / perception / AR","subsystem donor","vision donor","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.","yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.","memo","False","True","0.0","1.0","HT_cube_vision","HT_cube_vision_0008","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","yakupbilen/drl-rubiks-cube","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","31.0","5","117.0","Reserve Bench","Search/training systems bench","","","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.","Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." +"11939","Hypercubers/hypercubing.xyz","https://github.com/Hypercubers/hypercubing.xyz","HyperTwist","32.0","92.0","101.0","C","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","Website for the Hypercubing community","Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","Website for the Hypercubing community","","Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0006","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.","HyperTwist","hypercubing / nD simulation","integrate","heavy modification","medium","hypercubers/hypercubing.xyz","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","32.0","5","92.0","Locked Strategic Donor","Knowledge and curriculum donor","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.","Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.","high","permissive-knowledge-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." +"11945","Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","34.0","88.0","97.0","C","cubing trainer / solver / timing","subsystem donor","training donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium","single-source signal; clear taxonomy; mostly donor/reference role","medium","strong adjacency to identified core stack; memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.","Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0015","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","aarav2709/kubetimr","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","34.0","5","88.0","Donor Bench","Focused subsystem donor","","","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","routine-review-only","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." +"11951","roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","36.0","88.0","97.0","C","infra / runtime / observability / integration","subsystem donor","integration utility","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.","Non-euclidean Rubik's Cube Analogues","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API","deep source audit","Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.","Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","Non-euclidean Rubik's Cube Analogues","","roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0007","cubing / algorithm training","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","roice3/magictile","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","36.0","5","88.0","Locked Strategic Donor","Top-tier non-Euclidean geometry and topology donor","","P1","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11967","PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","41.0","72.0","81.0","C","telemetry / replay / feature governance","subsystem donor","telemetry donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.","","PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.","bookmarks","True","False","1.0","0.0","HT_control_plane","HT_control_plane_0001","cloud / infra / observability / api","Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.","HyperTwist","telemetry / replay / feature governance","repurpose","moderate modification","medium","posthog/posthog","HyperTwist","","","","","","","","","","","","","","","","Original global operational v3 retained","MIT outside ee/; enterprise-restricted in ee/","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","41.0","5","72.0","","Telemetry / replay / feature-governance donor","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.","Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed." +"","met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","donor bench","repurpose","moderate modification","Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.","","Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.","","Repurpose here means: turn it into a browser-side embodied coach or companion layer.","","","","Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0001","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","met4citizen/talkinghead","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser embodied coach surface","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +"","apache/echarts","https://github.com/apache/echarts","HyperTwist","","","","","analytics / visualization / reporting","subsystem donor","interface donor","donor bench","repurpose","moderate modification","Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.","","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.","","Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.","","","","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0002","analytics / visualization / reporting","Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.","HyperTwist","analytics / visualization / reporting","repurpose","moderate modification","medium","apache/echarts","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser analytics and reporting surface","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." +"","ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","visualization donor","merge bench","integrate","moderate modification","Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.","","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.","","Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.","","","","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0003","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","ecomfe/echarts-gl","","","","","","","","","","","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Merge Bench","Browser 3D analytics and explainer surface","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." +"","KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","viewer donor","donor bench","repurpose","moderate modification","Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.","","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.","","Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.","","","","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0004","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","khronosgroup/gltf-sample-viewer","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser asset validation and viewer surface","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer","https://github.com/google/model-viewer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","viewer donor","donor bench","repurpose","moderate modification","Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.","","Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.","","","","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0005","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","google/model-viewer","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser 3D presentation and inspection surface","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.","Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." +"","mrdoob/three.js","https://github.com/mrdoob/three.js","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.","","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.","","Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.","","","","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0006","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","mrdoob/three.js","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser 3D substrate","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.","Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"","pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.","","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.","","Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.","","","","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0007","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/postprocessing","","","","","","","","","","","","","","","","","","Zlib","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Merge Bench","Browser post-processing substrate","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.","Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser post-effect substrate beneath the landed browser spatial owner trio; do not treat it as separately live." +"","pmndrs/react-three-fiber","https://github.com/pmndrs/react-three-fiber","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.","","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.","","Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.","","","","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0008","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","pmndrs/react-three-fiber","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser React 3D substrate","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.","Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"","pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","merge bench","integrate","moderate modification","Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.","","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.","","Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.","","","","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0009","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/drei","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Merge Bench","Browser 3D helper and abstraction layer","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/xr","https://github.com/pmndrs/xr","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interaction donor","donor bench","repurpose","moderate modification","Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.","","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.","","Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.","","","","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0010","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","pmndrs/xr","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser XR and immersive UI substrate","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.","Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"","pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","donor bench","repurpose","moderate modification","Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.","","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.","","Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.","","","","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0011","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","pmndrs/uikit","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Donor Bench","Browser spatial UI surface","Included","P2","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser spatial UI layer beside the landed pmndrs/xr lane; do not treat it as separately live." +"","pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interaction donor","merge bench","integrate","moderate modification","Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.","","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.","","Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.","","","","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0012","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/react-spring","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","","","Merge Bench","Browser motion and animation layer","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side motion substrate inside the landed browser spatial support stack; do not treat it as separately live." +"","screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","","","","","capture / replay / support-plane","subsystem donor","support donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_support_sidecars","HT_support_sidecars_0001","support plane / capture / replay","Repurpose selectively for HyperTwist. Its source-backed role is a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","HyperTwist","support plane / capture / replay","repurpose","moderate modification","medium","screenpipe/screenpipe","","","","","","","","","","","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","","","","Donor Bench","Support-plane capture, history, and replay sidecar","Included","P2","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." +"","remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","","","","","media / rendering / export","subsystem donor","media donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_support_sidecars","HT_support_sidecars_0002","media / rendering / export","Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","HyperTwist","media / rendering / export","repurpose","moderate modification","medium","remotion-dev/remotion","","","","","","","","","","","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","","","","Donor Bench","Commercially licensed media-export and explainer sidecar","Included","P3","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use." +"","ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0001","browser / 2D / visualization","Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","HyperTwist","browser / 2D / visualization","integrate","moderate modification","medium","ecomfe/zrender","","","","","","","","","","","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","","","","Merge Bench","Browser 2D render substrate","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live." +"","pissang/claygl","https://github.com/pissang/claygl","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0002","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pissang/claygl","","","","","","","","","","","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","","","","Merge Bench","Browser WebGL substrate","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"","pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","viewer donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0003","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pissang/clay-viewer","","","","","","","","","","","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","","","","Merge Bench","Browser viewer and editor sidecar","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"","KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0004","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","khronosgroup/gltf-sample-renderer","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","","","","Merge Bench","Browser asset renderer substrate","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." +"","google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","editor donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0005","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","google/model-viewer/packages/space-opera","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","","","","Merge Bench","Browser asset editor and inspection surface","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","","","","","analytics / visualization / reporting","subsystem donor","qa donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0006","browser / QA / visual regression","Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","HyperTwist","browser / QA / visual regression","integrate","moderate modification","medium","google/model-viewer/packages/render-fidelity-tools","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","","","","Merge Bench","Browser fidelity QA harness","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","effect donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0007","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","google/model-viewer/packages/model-viewer-effects","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","","","","Merge Bench","Browser emphasis and post-processing extension","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","docs donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0008","documentation / demos / examples","Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.","HyperTwist","documentation / demos / examples","integrate","moderate modification","medium","google/model-viewer/packages/modelviewer.dev","","","","","","","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","","","","Merge Bench","Browser docs and demo surface","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." +"","google/model-viewer/packages/shared-assets","https://github.com/google/model-viewer/tree/main/packages/shared-assets","HyperTwist","","","","","asset / fixture / sample pack","subsystem donor","fixture donor","donor bench","repurpose","architecture only","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0009","asset / fixture / sample pack","Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.","HyperTwist","asset / fixture / sample pack","integrate","moderate modification","medium","google/model-viewer/packages/shared-assets","","","","","","","","","","","","","","","","","","Apache-2.0 container; mixed per-asset terms","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md","","","","Donor Bench","Boundary-sensitive sample-asset and test-fixture pack","Included","P3","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.","Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.","Preserve container notices and review each selected asset attribution or usage condition separately before shipping.","Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.","high","mixed-asset-whitelist-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use." +"","pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0010","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/react-postprocessing","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","","","","Merge Bench","Browser React effect-wrapper layer","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate React wrapper above pmndrs/postprocessing inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0011","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/three-stdlib","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","","","","Merge Bench","Browser 3D utility substrate","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate shared utility shelf beneath the landed browser spatial owner trio; do not treat it as separately live." +"","pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0012","browser / utilities / math","Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","HyperTwist","browser / utilities / math","integrate","moderate modification","medium","pmndrs/maath","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","","","","Merge Bench","Browser math-helper substrate","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate math-helper layer inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0013","browser / state / interaction","Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","HyperTwist","browser / state / interaction","repurpose","moderate modification","medium","pmndrs/zustand","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","","","","Donor Bench","Browser state-management substrate","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side state substrate inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0014","browser / state / interaction","Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","HyperTwist","browser / state / interaction","integrate","moderate modification","medium","pmndrs/leva","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","","","","Merge Bench","Browser control-panel and parameter UI layer","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate authoring and debug control sidecar inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0015","browser / state / interaction","Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.","HyperTwist","browser / state / interaction","repurpose","moderate modification","medium","pmndrs/use-gesture","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","","","","Donor Bench","Browser gesture and pointer-input substrate","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser gesture and pointer-input substrate inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0016","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","@react-spring/parallax","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","","","","Merge Bench","Browser layered-motion and explainer sidecar","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","Use directly as a bounded browser-side dependency for explainer and narrative surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate layered-motion sidecar beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0017","browser / utilities / scheduling","Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","HyperTwist","browser / utilities / scheduling","integrate","moderate modification","medium","@react-spring/rafz","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","","","","Merge Bench","Browser frame-loop and scheduling utility","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0018","browser / utilities / animation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","HyperTwist","browser / utilities / animation","integrate","moderate modification","medium","@react-spring/animated","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","","","","Merge Bench","Browser animatable-component substrate","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate animatable-component package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0019","browser / utilities / animation","Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","HyperTwist","browser / utilities / animation","repurpose","moderate modification","medium","@react-spring/core","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","","","","Donor Bench","Browser spring-runtime core","Included","P3","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate spring-runtime core beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0020","browser / utilities / animation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","HyperTwist","browser / utilities / animation","integrate","moderate modification","medium","@react-spring/shared","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","","","","Merge Bench","Browser motion utility substrate","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0021","browser / utilities / animation","Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","HyperTwist","browser / utilities / animation","integrate","moderate modification","medium","@react-spring/types","","","","","","","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","","","","Merge Bench","Browser motion type-contract substrate","Included","P4","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","Use directly as a bounded browser-side dependency where those contracts are actually needed.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate type-contract package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." diff --git a/docs/repo_portfolio_unified_phase_g_v6_3.csv b/docs/repo_portfolio_unified_phase_g_v6_3.csv index 8d89030..176be75 100644 --- a/docs/repo_portfolio_unified_phase_g_v6_3.csv +++ b/docs/repo_portfolio_unified_phase_g_v6_3.csv @@ -1,76 +1,76 @@ -execution_queue_order,repo,primary_url,best_fit_project_v2,project_rank,portfolio_priority_score,execution_priority_score_v3,priority_band,taxonomy_hardened,archetype_primary,archetype_secondary,portfolio_role_v3,recommended_action_v2,repurposing_potential_v2,modification_scope_detail_v3,capability_extract,integration_realization_detail,consolidation_detail,repurpose_detail,realization_checklist,inspection_depth_recommendation,hidden_value_hypothesis,source_inspection_questions,source_code_audit_targets,coding_model_instruction_v3,merger_partner_1,merger_type_1,merger_rationale_1,merger_partner_2,merger_type_2,merger_rationale_2,merger_partner_3,merger_type_3,merger_rationale_3,cross_project_transfer_targets,cross_project_transfer_rationale,exclusion_discipline,exclusion_reasoning_v3,confidence_v3,confidence_rationale_v3,confidence_reassessed,confidence_rationale,licensing_filter_status,bookmark_project_sections,bookmark_heading_paths_top,bookmark_description_sample,memo_signal_sample,expanded_reasoning,source_attachments,in_bookmarks,in_memo,bookmark_occurrences,memo_mentions,cluster_tag,source_audit_packet_id,category_guess_v2,reasoning,best_fit_project,category_guess,recommended_action,repurposing_potential,confidence,canonical_repo_key,alias_group_size,phase_g_bucket,phase_g_bucket_rank,phase_g_bucket_reason,phase_g_project_stack_layer,phase_g_inclusion_status,phase_g_source_audit_priority,phase_g_master_list_rationale,phase_g_project_rank,phase_g_conf_rank,phase_g_action_rank,phase_g_global_order,phase_g_project_order,phase_g_anomaly_flag,_repo_norm,v5_primary_eval_project,v5_runtime_project,v5_scriptorium_override_status,v5_scriptorium_phase_g_bucket,v5_scriptorium_phase_g_stack_layer,v5_scriptorium_phase_g_source_audit_priority,v5_scriptorium_current_reality_status,v5_scriptorium_actual_role,v5_scriptorium_evidence_summary,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,audit_rank_num,bucket_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 -1.0,HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,1.0,160.0,193.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs",HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,6.0,HT_hyper_engine,HT_hyper_engine_0001,hypercubing / nD simulation,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.,multi-project,hypercubing / nD simulation,integrate,direct,medium,hactarce/hyperspeedcube,1.0,Locked Foundation,1.0,Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.,nD / hypercubing simulation substrate,Included,P0,"HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,2.0,2.0,,hactarce/hyperspeedcube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,1.0,1,1.0,160.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,"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." -1746.0,SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,1.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.",huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services,deep source audit,"Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.",Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0001,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,systran/faster-whisper,1.0,Donor Bench,4.0,"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.",Cross-project / future-adjacent,Included,P2,"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.",4.0,2.0,2.0,60.0,2.0,,systran/faster-whisper,multi-project,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,1.0,3,4.0,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.,,, -2.0,kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,2.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0001,computer vision / AR,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,kkoomen/qbr,1.0,Locked Foundation,1.0,Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.,Live cube-recognition substrate,Included,P0,"kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,7705.0,4.0,,kkoomen/qbr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2.0,1,1.0,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,"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." -,cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",Validate actual implementation breadth and hidden donor subsystems before promotion.,P0 tier source audit.,cubing/alg.js may contain stronger reusable internals than its surface description suggests.,"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.","Audit cubing/alg.js directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.",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,Many supplemental repos may reveal transferable abstractions after source inspection.,Exclude only after source audit proves weak or purely documentary value.,Supplemental intake row. Current exclusion posture is provisional.,medium,Supplemental intake heuristic.,medium,Pending direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive.,HyperTwist,HyperTwist,,Supplemental intake; reference docs advisory only.,cubing/alg.js is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.,HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0002,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/alg.js,1.0,Donor Bench,4.0,Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.,Focused restrictive clean-room donor target,included_in_v6_supplemental_intake,P2,"Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.",2.0,2.0,2.0,7708.0,1.0,,cubing/alg.js,HyperTwist,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.0,1,4.0,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract. -,cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",Validate actual implementation breadth and hidden donor subsystems before promotion.,P0 tier source audit.,cubing/twisty.js may contain stronger reusable internals than its surface description suggests.,"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.","Audit cubing/twisty.js directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.",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,Many supplemental repos may reveal transferable abstractions after source inspection.,Exclude only after source audit proves weak or purely documentary value.,Supplemental intake row. Current exclusion posture is provisional.,medium,Supplemental intake heuristic.,medium,Pending direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive.,HyperTwist,HyperTwist,,Supplemental intake; reference docs advisory only.,cubing/twisty.js is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.,HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0003,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/twisty.js,1.0,Donor Bench,4.0,Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.,Focused restrictive clean-room donor target,included_in_v6_supplemental_intake,P2,Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.,2.0,2.0,2.0,7710.0,3.0,,cubing/twisty.js,HyperTwist,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.0,1,4.0,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract. -1747.0,coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,2.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0002,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,coqui-ai/tts,1.0,Donor Bench,4.0,"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.",Cross-project / future-adjacent,Included,P2,"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.",4.0,2.0,2.0,7713.0,4.0,,coqui-ai/tts,multi-project,,,,,,,,,,Original global Phase G v4 retained,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2.0,3,4.0,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.,,, -,HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,2.0,63.0,63.0,P2,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",Validate actual implementation breadth and hidden donor subsystems before promotion.,P2 tier source audit.,HactarCE/2x2x2x2-Scrambler may contain stronger reusable internals than its surface description suggests.,"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.","Audit HactarCE/2x2x2x2-Scrambler directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.",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,Many supplemental repos may reveal transferable abstractions after source inspection.,Exclude only after source audit proves weak or purely documentary value.,Supplemental intake row. Current exclusion posture is provisional.,low-to-medium,Supplemental intake heuristic.,low-to-medium,Pending direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive.,HyperTwist,HyperTwist,,Supplemental intake; reference docs advisory only.,HactarCE/2x2x2x2-Scrambler is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.,HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0004,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai.,HyperTwist,puzzle_simulation_training_donor,future candidate,architecture only,low-to-medium,hactarce/2x2x2x2-scrambler,1.0,Donor Bench,6.0,"GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.",Focused restrictive clean-room donor target,included_in_v6_supplemental_intake,P2,"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.",2.0,3.0,3.0,7714.0,5.0,,hactarce/2x2x2x2-scrambler,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2.0,3,6.0,63.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier. -3.0,vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,3.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb",vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.,memo,False,True,0.0,10.0,HT_cube_vision,HT_cube_vision_0002,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,vivaansinghvi07/rubix-cube-solver,1.0,Locked Parallel Foundation,2.0,Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.,Parallel foundation and reconstruction companion donor,Included,P0,"vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,7819.0,110.0,,vivaansinghvi07/rubix-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,3.0,1,2.0,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"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." -1748.0,ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,3.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.,"Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0003,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,ggml-org/whisper.cpp,1.0,Donor Bench,4.0,"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.",Cross-project / future-adjacent,Included,P2,"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.",4.0,2.0,2.0,7850.0,6.0,,ggml-org/whisper.cpp,multi-project,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,3.0,3,4.0,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.,,, -4.0,tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,4.0,156.0,189.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_training_stack,HT_training_stack_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,tao-yu/alg-trainer,1.0,Locked Parallel Foundation,2.0,Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.,Training / timing layer,Included,P0,"tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,8548.0,111.0,,tao-yu/alg-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4.0,1,2.0,156.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -1749.0,rhasspy/piper,https://github.com/rhasspy/piper,multi-project,4.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.",Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.,"Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0004,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,rhasspy/piper,1.0,Donor Bench,4.0,"Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.",Cross-project / future-adjacent,Included,P2,"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.",4.0,2.0,2.0,8565.0,8.0,,rhasspy/piper,multi-project,,,,,,,,,,Original global Phase G v4 retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4.0,3,4.0,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.,,, -5.0,cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,5.0,152.0,185.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.",Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,"Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,medium-high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,1.0,HT_cube_semantics,HT_cube_semantics_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cubing/cubing.js,1.0,Locked Strategic Donor,1.0,"Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.",Boundary-sensitive classic-cubing semantics and rendering donor,Included,P1,"Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.",2.0,4.0,3.0,11771.0,112.0,,cubing/cubing.js,HyperTwist,,,,,,,,,,Original global Phase G v4 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,5.0,1,1.0,152.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.",Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.,Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.,Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.,high,dual-license-boundary-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable. -6.0,cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,6.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0003,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,cahidenes/rubiks-cube-solver,1.0,Locked Strategic Donor,3.0,"High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.",Active recognition-heuristics and validation donor,Included,P1,"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.",2.0,5.0,3.0,11849.0,113.0,,cahidenes/rubiks-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,6.0,2,3.0,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.,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." -7.0,tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,7.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 7,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.",memo,False,True,0.0,7.0,HT_cube_vision,HT_cube_vision_0004,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,tentone/rubix-solver,1.0,Locked Strategic Donor,3.0,High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.,Active native-CV donor and comparison bench,Included,P1,"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.",2.0,5.0,3.0,11852.0,114.0,,tentone/rubix-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,7.0,2,3.0,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.,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." -8.0,Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,8.0,145.0,171.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0002,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,lykos/cube_trainer,1.0,Locked Strategic Donor,3.0,"Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain.",Top-tier persistent training-domain donor,Included,P1,"Lykos/cube_trainer is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier persistent training-domain donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11857.0,115.0,,lykos/cube_trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,8.0,2,3.0,145.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -10.0,poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,9.0,145.0,171.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0016,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,poliva/cubedex,1.0,Locked Strategic Donor,3.0,"Top-tier strategic donor for smartcube-aware, offline-first training UX and practical drill ergonomics, but not the owner of the long-term training backend.",Top-tier training UX and smartcube donor,Included,P1,"poliva/cubedex is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier training UX and smartcube donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11861.0,116.0,,poliva/cubedex,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,9.0,2,3.0,145.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -9.0,kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,10.0,145.0,171.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked strategic donor,repurpose,architecture only,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source,"kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.",memo,False,True,0.0,4.0,HT_hyper_engine,HT_hyper_engine_0002,cubing / algorithm training,"Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.",HyperTwist,hypercubing / nD simulation,integrate,direct,medium,kash/cubedesk,1.0,Locked Strategic Donor,3.0,"Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.",Restrictive clean-room donor target,Included,P1,"Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.",2.0,5.0,3.0,11865.0,117.0,,kash/cubedesk,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,10.0,2,3.0,145.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.",Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.,Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.,Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.,high,license-contradiction-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,"Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." -12.0,cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,11.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Automatically exported from code.google.com/p/magiccube4d,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Automatically exported from code.google.com/p/magiccube4d,,"cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0003,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cutelyaware/magiccube4d,1.0,Locked Strategic Donor,5.0,Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.,"Top-tier 4D interaction, history, and macro donor with attribution obligations",Included,P1,"Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.",2.0,3.0,3.0,11871.0,118.0,,cutelyaware/magiccube4d,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,Custom broad-use license with attribution requested,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,11.0,3,5.0,122.0,mixed_or_boundary_sensitive_known,direct_incorporation_ok,"The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.",Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.,"Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.",Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.,medium,custom-license-attribution-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly. -13.0,roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,12.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",4D Megaminx Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,4D Megaminx Analogue,,"roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0004,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,roice3/magic120cell,1.0,Locked Strategic Donor,5.0,"MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.",Specialized 4D interaction and puzzle-UX donor,Included,P1,Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,2.0,3.0,3.0,11875.0,119.0,,roice3/magic120cell,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,12.0,3,5.0,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"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." -14.0,roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,13.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",5D Rubik's Cube Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,5D Rubik's Cube Analogue,,"roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0005,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magiccube5d,1.0,Locked Strategic Donor,5.0,"MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Specialized 5D cube interaction, progress, and macro donor",Included,P1,Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,2.0,3.0,3.0,11879.0,120.0,,roice3/magiccube5d,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,13.0,3,5.0,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"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." -11.0,cs0x7f/cstimer,https://github.com/cs0x7f/cstimer,HyperTwist,14.0,121.0,147.0,A,gold-standard timer benchmark,benchmark,Gold-standard timer benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.",Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.,"Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,behavior and acceptance-test benchmark review,"Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.,high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.",high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,cs0x7f/cstimer — GPL timer/training platform; keep only as the gold-standard timer benchmark.,"cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.",memo,False,True,0.0,5.0,HT_timer_training,HT_timer_training_0001,Gold-standard timer benchmark,"Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.",HyperTwist,Gold-standard timer benchmark,future candidate,architecture only,medium,cs0x7f/cstimer,1.0,Reserve Bench,3.0,"GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.",Gold-standard timer benchmark,Included,P2,Keep in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.,2.0,5.0,3.0,11881.0,121.0,,cs0x7f/cstimer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,14.0,2,3.0,121.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.,high,gpl-timer-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle. -16.0,aMonteSl/CodeXR,https://github.com/aMonteSl/CodeXR,HyperTwist,16.0,119.0,134.0,B,reference-only XR benchmark,benchmark,Reference-only XR benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.",Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.,"Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.",Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,behavior-level benchmark review,"Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.",Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?,"Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.,high,Source-backed dossier and license verification collapse the old donor thesis.,high,Source-backed dossier and license verification collapse the old donor thesis.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,aMonteSl/CodeXR — GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.,"aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0005,Reference-only XR benchmark,Reference-only XR benchmark for HyperTwist; not a donor lane.,HyperTwist,Reference-only XR benchmark,future candidate,architecture only,medium,amontesl/code-xr,1.0,Reserve Bench,5.0,GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.,Reference-only XR benchmark,Included,P3,"Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.",2.0,3.0,3.0,11890.0,3226.0,,amontesl/codexr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0-only,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,16.0,3,5.0,119.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.,Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-reference-only-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows. -17.0,brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,17.0,119.0,134.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 3,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0006,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,brianpeiris/riftsketch,1.0,Reserve Bench,5.0,"Useful MIT WebXR interaction benchmark for spatial editor panels, world-space monitors, and keyboard-first immersive tooling, but explicitly below the HyperTwist core tier.",XR interaction and spatial-UI bench,Included,P2,"brianpeiris/RiftSketch is placed in Reserve Bench for HyperTwist because it best serves the 'XR interaction and spatial-UI bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11894.0,3227.0,,brianpeiris/riftsketch,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,17.0,3,5.0,119.0,permissive_or_noncopyleft_known,pattern_only_preferred,The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.,Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope. -21.0,abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,18.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0006,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,direct,medium,abunickabhi/5style-trainer,1.0,Donor Bench,5.0,"Focused advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.",Focused advanced-training donor,Included,P2,"abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11898.0,122.0,,abunickabhi/5style-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,18.0,3,5.0,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -18.0,MathewKJ2048/Rubiks-cube-simulator,https://github.com/MathewKJ2048/Rubiks-cube-simulator,HyperTwist,19.0,118.0,133.0,B,clean-room simulator benchmark,benchmark,Clean-room simulator benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.,Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in text-command grammar, move-history logging, and timed step playback.",Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.",Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,MathewKJ2048/Rubiks-cube-simulator — GPL-3.0 simulator; keep only as a clean-room simulator benchmark.,"MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.",memo,False,True,0.0,2.0,HT_training_clean_room,HT_training_clean_room_0004,Clean-room simulator benchmark,Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room simulator benchmark,future candidate,architecture only,medium,mathewkj2048/rubiks-cube-simulator,1.0,Reserve Bench,5.0,GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material.,Clean-room simulator benchmark,Included,P3,Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors.,2.0,3.0,3.0,11901.0,123.0,,mathewkj2048/rubiks-cube-simulator,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,19.0,3,5.0,118.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.",Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." -19.0,NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,20.0,118.0,133.0,B,vision / perception / AR,subsystem donor,vision donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.",NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.,memo,False,True,0.0,2.0,HT_cube_vision,HT_cube_vision_0007,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,nuilab/code-vr,1.0,Donor Bench,5.0,"MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.",XR pedagogy and code-to-scene representation donor,Included,P2,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.,2.0,3.0,3.0,11904.0,3228.0,,nuilab/code-vr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,20.0,3,5.0,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.,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." -20.0,ShellPuppy/RCube,https://github.com/ShellPuppy/RCube,HyperTwist,21.0,118.0,133.0,B,large-N solver benchmark,benchmark,Large-N solver benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.",Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.,Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,algorithm benchmark review,Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.,Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?,"Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,ShellPuppy/RCube — GPL large-N cube solver; keep only as a large-N solver benchmark.,ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.,memo,False,True,0.0,2.0,HT_solver_oracles,HT_solver_oracles_0001,Large-N solver benchmark,"Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.",HyperTwist,Large-N solver benchmark,future candidate,architecture only,medium,shellpuppy/rcube,1.0,Reserve Bench,5.0,GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.,Large-N solver benchmark,Included,P3,Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.,2.0,3.0,3.0,11907.0,124.0,,shellpuppy/rcube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,21.0,3,5.0,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." -22.0,brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,22.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0007,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,brownan/rubiks-cube-solver,1.0,Reserve Bench,5.0,GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.,Benchmark oracle and clean-room optimal-solver candidate,Included,P2,Keep as a primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.,2.0,3.0,3.0,11910.0,125.0,,brownan/rubiks-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,22.0,3,5.0,118.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for any later first-party optimal-solver effort.,high,gpl-oracle-clean-room-review,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." -24.0,newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubiks-cross-trainer,HyperTwist,24.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,newyork-anthonyng/rubiks-cross-trainer,1.0,Donor Bench,5.0,Focused donor for the precomputed cross-difficulty corpus and CFOP micro-drill progression rather than a broader training-platform shell.,Focused donor,Included,P2,"newyork-anthonyng/rubiks-cross-trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11916.0,126.0,,newyork-anthonyng/rubiks-cross-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,24.0,3,5.0,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -25.0,vwcwong/CubeSim,https://github.com/vwcwong/CubeSim,HyperTwist,25.0,118.0,133.0,B,clean-room state/history benchmark,benchmark,Clean-room state/history benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: cleaner domain architecture for simulator state/history separation, parser/scramble modules, and replay/history behavior suitable for clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party state/history and replay behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in state/history separation, parser/scramble modularity, and replay-oriented architecture.",Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.",Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL simulator code and should remain only as a clean-room state/history benchmark.,high,The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.,high,The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,vwcwong/CubeSim — GPL simulator; keep only as a clean-room state/history benchmark.,"vwcwong/CubeSim is retained only as a clean-room state/history benchmark. Its value is architectural and behavioral, not donor code.",memo,False,True,0.0,2.0,HT_training_clean_room,HT_training_clean_room_0005,Clean-room state/history benchmark,Clean-room state/history benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room state/history benchmark,future candidate,architecture only,medium,vwcwong/cubesim,1.0,Reserve Bench,5.0,GPL simulator with unusually clean state/history architecture; retain only as clean-room benchmark material.,Clean-room state/history benchmark,Included,P3,Keep in canon only as a clean-room state/history benchmark for first-party simulator architecture.,2.0,3.0,3.0,11919.0,127.0,,vwcwong/cubesim,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,25.0,3,5.0,118.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.,Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use. -26.0,AviKaufman/Rubix-cube-trainer,https://github.com/AviKaufman/Rubix-cube-trainer,HyperTwist,26.0,117.0,132.0,B,clean-room pedagogy benchmark,benchmark,Clean-room pedagogy benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: beginner-method teaching flow, step guidance, and tutorial-state behavior worth preserving through a clean-room spec.",Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in beginner-method pedagogy flow, guidance cadence, and tutorial-state transitions.",Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.",Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is explicitly all-rights-reserved and should remain only as a clean-room pedagogy benchmark.,high,The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.,high,The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,AviKaufman/Rubix-cube-trainer — all rights reserved; keep only as a clean-room pedagogy benchmark.,"AviKaufman/Rubix-cube-trainer is retained only as a clean-room pedagogy benchmark. Its value is in teaching flow and tutorial behavior, not donor code.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0003,Clean-room pedagogy benchmark,Clean-room pedagogy benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room pedagogy benchmark,future candidate,architecture only,medium,avikaufman/rubix-cube-trainer,1.0,Reserve Bench,5.0,All-rights-reserved repo with narrow teaching-flow value; retain only as clean-room benchmark material.,Clean-room pedagogy benchmark,Included,P3,Keep in canon only as a clean-room pedagogy benchmark for first-party teaching-flow work.,2.0,3.0,3.0,11922.0,128.0,,avikaufman/rubix-cube-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,26.0,3,5.0,117.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.,Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source or assets directly without separate rights.,Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary.,high,all-rights-reserved-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design. -27.0,alinen/cube,https://github.com/alinen/cube,HyperTwist,27.0,117.0,132.0,B,clean-room planner benchmark,benchmark,Clean-room planner benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: guided lesson flow, cube-state handling, and bounded planner/search behavior suitable for first-party clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only.,Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,Hidden value sits in bounded planner/search flow and guided lesson state transitions.,Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.",Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo has no explicit license visible and should remain only as a clean-room planner benchmark.,medium,"The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.",medium,"The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,alinen/cube — no explicit license visible; keep only as a clean-room planner benchmark.,"alinen/cube is retained only as a clean-room planner benchmark. Its useful value is behavioral and architectural, not donor-grade.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0001,Clean-room planner benchmark,Clean-room planner benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room planner benchmark,future candidate,architecture only,medium,alinen/cube,1.0,Reserve Bench,5.0,No explicit license visible and limited scope; retain only for clean-room planner behavior extraction.,Clean-room planner benchmark,Included,P3,Keep in canon only as a clean-room planner benchmark for first-party guided-lesson and planner work.,2.0,3.0,3.0,11925.0,129.0,,alinen/cube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,27.0,3,5.0,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." -28.0,ambisinister/blindsolve,https://github.com/ambisinister/blindsolve,HyperTwist,28.0,117.0,132.0,B,clean-room BLD memo benchmark,benchmark,Clean-room BLD memo benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Benchmark-only retained value: narrow memo-practice behavior and BLD training flow worth preserving through a clean-room spec.,Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,Hidden value sits in narrow memo-practice flow and user-feedback behavior.,Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.",Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo has no explicit license visible and does not justify donor treatment; retain only as a clean-room memo benchmark.,medium,"The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.",medium,"The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,ambisinister/blindsolve — no explicit license visible; keep only as a clean-room BLD memo benchmark.,"ambisinister/blindsolve is retained only as a clean-room BLD memo benchmark. Its value is in a narrow behavior slice, not in donor code.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0002,Clean-room BLD memo benchmark,Clean-room BLD memo benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room BLD memo benchmark,future candidate,architecture only,medium,ambisinister/blindsolve,1.0,Reserve Bench,5.0,No explicit license visible and extremely narrow scope; retain only as clean-room benchmark material.,Clean-room BLD memo benchmark,Included,P3,Keep in canon only as a clean-room BLD memo benchmark for later first-party micro-mode work.,2.0,3.0,3.0,11928.0,130.0,,ambisinister/blindsolve,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,28.0,3,5.0,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." -29.0,efrantar/rob-twophase,https://github.com/efrantar/rob-twophase,HyperTwist,29.0,117.0,132.0,B,solver oracle / robot-metric benchmark,benchmark,Solver oracle and robot-metric benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: correctness oracle, robot/axial-metric comparisons, multiple-solution search expectations, and pruning-table performance baselines.","Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code.",Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests.,Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,oracle benchmark review,"Hidden value sits in metric handling, pruning-table organization, CLI oracle behavior, and multi-solution search expectations.","Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?","Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.","Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL solver code and should remain only as a correctness/performance oracle and robot-metric benchmark.,high,"Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.",high,"Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,efrantar/rob-twophase — GPL two-phase solver; keep only as solver oracle and robot-metric benchmark.,"efrantar/rob-twophase remains valuable because it is a strong correctness/performance oracle with robot-metric coverage. That value is benchmark authority, not donor code.",memo,False,True,0.0,1.0,HT_solver_oracles,HT_solver_oracles_0002,Solver oracle and robot-metric benchmark,"Solver oracle and robot-metric benchmark for HyperTwist; retained for acceptance testing, not donor use.",HyperTwist,Solver oracle and robot-metric benchmark,future candidate,architecture only,medium,efrantar/rob-twophase,1.0,Reserve Bench,5.0,"GPL solver/oracle repo whose retained value is correctness, performance, and metric benchmarking rather than donor use.",Solver oracle and robot-metric benchmark,Included,P2,Keep in canon as a restrictive solver oracle benchmark with robot-metric value.,2.0,3.0,3.0,11931.0,131.0,,efrantar/rob-twophase,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,29.0,3,5.0,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." -30.0,onionhoney/roux-trainers,https://github.com/onionhoney/roux-trainers,HyperTwist,30.0,117.0,132.0,B,method-specific training donor,restrictive donor,clean-room donor,donor bench,repurpose,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Focused restrictive clean-room donor target. Retain the stage-specific training modes, solver-backed analyzer behavior, recognition masking, favorites/batch-drill flow, and 2D/3D training visualization ideas through Model A / Model B separation.","Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code.",Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary.,Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value sits in state-machine-driven training flows, solver-backed analyzer behavior, recognition masking, favorites persistence, and batch-drill mechanics.",Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?,"Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,HyperTwist only,"Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing.","exclude from direct code use, keep as clean-room donor","The repo is GPLv3 and too method-specific for direct incorporation, but it still contains real training/analyzer subsystem value worth preserving through a clean-room donor path.",high,"The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.",high,"The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"onionhoney/roux-trainers — GPLv3 Roux trainer; keep as a focused restrictive clean-room donor, not direct donor code.","onionhoney/roux-trainers remains valuable because it contains stage-specific training-state machines, solver-backed analyzer modes, recognition masking, and batch-drill patterns. That value should flow through a clean-room donor path, not direct incorporation.",memo,False,True,0.0,1.0,HT_training_clean_room,HT_training_clean_room_0006,Focused restrictive clean-room donor target,"Focused restrictive clean-room donor target for HyperTwist; stronger than a passive benchmark, but still not direct donor code.",HyperTwist,Focused restrictive clean-room donor target,repurpose,architecture only,medium,onionhoney/roux-trainers,1.0,Donor Bench,5.0,GPLv3 method-specific trainer with real subsystem value that should be preserved through clean-room extraction rather than donor use.,Focused restrictive clean-room donor target,Included,P2,Keep in canon as a focused restrictive clean-room donor for method-specific training and analyzer behavior.,2.0,3.0,3.0,11934.0,132.0,,onionhoney/roux-trainers,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,30.0,3,5.0,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. -31.0,yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,31.0,117.0,132.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.",memo,False,True,0.0,1.0,HT_cube_vision,HT_cube_vision_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,yakupbilen/drl-rubiks-cube,1.0,Reserve Bench,5.0,"Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.",Search/training systems bench,Included,P2,"yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11937.0,133.0,,yakupbilen/drl-rubiks-cube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,31.0,3,5.0,117.0,permissive_or_noncopyleft_known,pattern_only_preferred,"The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.",Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." -32.0,Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,HyperTwist,32.0,92.0,101.0,C,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Website for the Hypercubing community,"Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Website for the Hypercubing community,,"Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0006,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,hypercubers/hypercubing.xyz,1.0,Locked Strategic Donor,4.0,"MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.",Knowledge and curriculum donor,Included,P1,Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.,2.0,2.0,2.0,11938.0,134.0,Thin-fit assignment; verify project mapping during source audit,hypercubers/hypercubing.xyz,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,32.0,3,4.0,92.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.,"Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.",Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.,high,permissive-knowledge-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." -34.0,Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,34.0,88.0,97.0,C,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium,single-source signal; clear taxonomy; mostly donor/reference role,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0015,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,aarav2709/kubetimr,1.0,Donor Bench,4.0,"Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.",Focused subsystem donor,Included,P2,"Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,2.0,11944.0,135.0,,aarav2709/kubetimr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,34.0,3,4.0,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,routine-review-only,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." -36.0,roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,36.0,88.0,97.0,C,infra / runtime / observability / integration,subsystem donor,integration utility,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",Non-euclidean Rubik's Cube Analogues,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API,deep source audit,"Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Non-euclidean Rubik's Cube Analogues,,"roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0007,cubing / algorithm training,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magictile,1.0,Locked Strategic Donor,4.0,"MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.",Top-tier non-Euclidean geometry and topology donor,Included,P1,Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.,2.0,2.0,2.0,11950.0,136.0,Thin-fit assignment; verify project mapping during source audit,roice3/magictile,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,36.0,3,4.0,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"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." -41.0,PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,41.0,72.0,81.0,C,telemetry / replay / feature governance,subsystem donor,telemetry donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.",,"PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_control_plane,HT_control_plane_0001,cloud / infra / observability / api,"Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.",HyperTwist,telemetry / replay / feature governance,repurpose,moderate modification,medium,posthog/posthog,1.0,Donor Bench,4.0,"Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.",Telemetry / replay / feature-governance donor,Included,P2,"PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.",2.0,2.0,2.0,11966.0,139.0,Thin-fit assignment; verify project mapping during source audit,posthog/posthog,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,41.0,3,4.0,72.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.",Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.,"Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -,met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0001,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,met4citizen/talkinghead,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.",Browser embodied coach surface,Included,P2,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.",,,,,,,met4citizen/talkinghead,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." -,apache/echarts,https://github.com/apache/echarts,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,"Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0002,analytics / visualization / reporting,Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.,HyperTwist,analytics / visualization / reporting,repurpose,moderate modification,medium,apache/echarts,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.",Browser analytics and reporting surface,Included,P2,"apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.",,,,,,,apache/echarts,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-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." -,ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,visualization donor,merge bench,integrate,moderate modification,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,"Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0003,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,ecomfe/echarts-gl,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.",Browser 3D analytics and explainer surface,Included,P3,"ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.",,,,,,,ecomfe/echarts-gl,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,"Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0004,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,khronosgroup/gltf-sample-viewer,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.",Browser asset validation and viewer surface,Included,P3,"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.",,,,,,,khronosgroup/gltf-sample-viewer,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer,https://github.com/google/model-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.",,"Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.",,,,"Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0005,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,google/model-viewer,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.",Browser 3D presentation and inspection surface,Included,P2,"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.",,,,,,,google/model-viewer,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,"Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.",Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." -,mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,,"Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,"Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0006,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,mrdoob/three.js,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.",Browser 3D substrate,Included,P2,"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.",,,,,,,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-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." -,pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,"Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0007,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/postprocessing,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.",Browser post-processing substrate,Included,P3,"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.",,,,,,,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.,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." -,pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,"Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0008,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/react-three-fiber,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.",Browser React 3D substrate,Included,P2,"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.",,,,,,,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-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." -,pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,,"Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,"Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0009,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/drei,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.",Browser 3D helper and abstraction layer,Included,P3,"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.",,,,,,,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.,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." -,pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,donor bench,repurpose,moderate modification,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,"Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0010,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/xr,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.",Browser XR and immersive UI substrate,Included,P2,"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.",,,,,,,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-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." -,pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,"Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0011,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/uikit,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.",Browser spatial UI surface,Included,P2,"pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.",,,,,,,pmndrs/uikit,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,merge bench,integrate,moderate modification,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",,"Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,"Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0012,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-spring,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.",Browser motion and animation layer,Included,P3,"pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.",,,,,,,pmndrs/react-spring,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,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." -,screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,,,,,capture / replay / support-plane,subsystem donor,support donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0001,support plane / capture / replay,"Repurpose selectively for HyperTwist. Its source-backed role is a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.",HyperTwist,support plane / capture / replay,repurpose,moderate modification,medium,screenpipe/screenpipe,,Donor Bench,4.0,"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.","Support-plane capture, history, and replay sidecar",Included,P2,"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.",,,,,,,screenpipe/screenpipe,,,,,,,,,,,,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.,Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.,Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.,"Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." -,remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,,,,,media / rendering / export,subsystem donor,media donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0002,media / rendering / export,"Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.",HyperTwist,media / rendering / export,repurpose,moderate modification,medium,remotion-dev/remotion,,Donor Bench,4.0,"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.",Commercially licensed media-export and explainer sidecar,Included,P3,"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.",,,,,,,remotion-dev/remotion,,,,,,,,,,,,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.,Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.,Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.,Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.,high,commercial-license-sidecar-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use. -,ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0001,browser / 2D / visualization,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",HyperTwist,browser / 2D / visualization,integrate,moderate modification,medium,ecomfe/zrender,,Merge Bench,5.0,"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.",Browser 2D render substrate,Included,P3,"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.",,,,,,,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,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." -,pissang/claygl,https://github.com/pissang/claygl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0002,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/claygl,,Merge Bench,5.0,"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.",Browser WebGL substrate,Included,P3,"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.",,,,,,,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,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." -,pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0003,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/clay-viewer,,Merge Bench,5.0,"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.",Browser viewer and editor sidecar,Included,P3,"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.",,,,,,,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,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." -,KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0004,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,khronosgroup/gltf-sample-renderer,,Merge Bench,5.0,"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.",Browser asset renderer substrate,Included,P3,"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.",,,,,,,khronosgroup/gltf-sample-renderer,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." -,google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,editor donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0005,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/space-opera,,Merge Bench,5.0,"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.",Browser asset editor and inspection surface,Included,P3,"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.",,,,,,,google/model-viewer/packages/space-opera,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,qa donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0006,browser / QA / visual regression,"Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.",HyperTwist,browser / QA / visual regression,integrate,moderate modification,medium,google/model-viewer/packages/render-fidelity-tools,,Merge Bench,5.0,"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.",Browser fidelity QA harness,Included,P3,"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.",,,,,,,google/model-viewer/packages/render-fidelity-tools,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,effect donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0007,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/model-viewer-effects,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.",Browser emphasis and post-processing extension,Included,P3,"google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.",,,,,,,google/model-viewer/packages/model-viewer-effects,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." -,google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,docs donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0008,documentation / demos / examples,"Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.",HyperTwist,documentation / demos / examples,integrate,moderate modification,medium,google/model-viewer/packages/modelviewer.dev,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.",Browser docs and demo surface,Included,P4,"google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.",,,,,,,google/model-viewer/packages/modelviewer.dev,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." -,google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,,,,,asset / fixture / sample pack,subsystem donor,fixture donor,donor bench,repurpose,architecture only,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0009,asset / fixture / sample pack,"Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.",HyperTwist,asset / fixture / sample pack,integrate,moderate modification,medium,google/model-viewer/packages/shared-assets,,Donor Bench,5.0,"Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.",Boundary-sensitive sample-asset and test-fixture pack,Included,P3,"Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.",,,,,,,google/model-viewer/packages/shared-assets,,,,,,,,,,,,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.,Preserve container notices and review each selected asset attribution or usage condition separately before shipping.,"Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.",high,mixed-asset-whitelist-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use. -,pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0010,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-postprocessing,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",Browser React effect-wrapper layer,Included,P4,"pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.",,,,,,,pmndrs/react-postprocessing,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,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." -,pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0011,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/three-stdlib,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",Browser 3D utility substrate,Included,P4,"pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/three-stdlib,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,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." -,pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0012,browser / utilities / math,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",HyperTwist,browser / utilities / math,integrate,moderate modification,medium,pmndrs/maath,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",Browser math-helper substrate,Included,P4,"pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/maath,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,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." -,pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0013,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/zustand,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",Browser state-management substrate,Included,P3,"pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/zustand,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,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." -,pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0014,browser / state / interaction,"Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",HyperTwist,browser / state / interaction,integrate,moderate modification,medium,pmndrs/leva,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",Browser control-panel and parameter UI layer,Included,P4,"pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.",,,,,,,pmndrs/leva,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,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." -,pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0015,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/use-gesture,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.",Browser gesture and pointer-input substrate,Included,P3,"pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/use-gesture,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,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." -,@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0016,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,@react-spring/parallax,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",Browser layered-motion and explainer sidecar,Included,P4,"@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.",,,,,,,@react-spring/parallax,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,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." -,@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0017,browser / utilities / scheduling,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",HyperTwist,browser / utilities / scheduling,integrate,moderate modification,medium,@react-spring/rafz,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",Browser frame-loop and scheduling utility,Included,P4,"@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.",,,,,,,@react-spring/rafz,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,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." -,@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0018,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/animated,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",Browser animatable-component substrate,Included,P4,"@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/animated,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,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." -,@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0019,browser / utilities / animation,"Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",HyperTwist,browser / utilities / animation,repurpose,moderate modification,medium,@react-spring/core,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",Browser spring-runtime core,Included,P3,"@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.",,,,,,,@react-spring/core,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,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." -,@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0020,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/shared,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",Browser motion utility substrate,Included,P4,"@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/shared,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,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." -,@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0021,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/types,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",Browser motion type-contract substrate,Included,P4,"@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/types,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,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." +"execution_queue_order","repo","primary_url","best_fit_project_v2","project_rank","portfolio_priority_score","execution_priority_score_v3","priority_band","taxonomy_hardened","archetype_primary","archetype_secondary","portfolio_role_v3","recommended_action_v2","repurposing_potential_v2","modification_scope_detail_v3","capability_extract","integration_realization_detail","consolidation_detail","repurpose_detail","realization_checklist","inspection_depth_recommendation","hidden_value_hypothesis","source_inspection_questions","source_code_audit_targets","coding_model_instruction_v3","merger_partner_1","merger_type_1","merger_rationale_1","merger_partner_2","merger_type_2","merger_rationale_2","merger_partner_3","merger_type_3","merger_rationale_3","cross_project_transfer_targets","cross_project_transfer_rationale","exclusion_discipline","exclusion_reasoning_v3","confidence_v3","confidence_rationale_v3","confidence_reassessed","confidence_rationale","licensing_filter_status","bookmark_project_sections","bookmark_heading_paths_top","bookmark_description_sample","memo_signal_sample","expanded_reasoning","source_attachments","in_bookmarks","in_memo","bookmark_occurrences","memo_mentions","cluster_tag","source_audit_packet_id","category_guess_v2","reasoning","best_fit_project","category_guess","recommended_action","repurposing_potential","confidence","canonical_repo_key","alias_group_size","phase_g_bucket","phase_g_bucket_rank","phase_g_bucket_reason","phase_g_project_stack_layer","phase_g_inclusion_status","phase_g_source_audit_priority","phase_g_master_list_rationale","phase_g_project_rank","phase_g_conf_rank","phase_g_action_rank","phase_g_global_order","phase_g_project_order","phase_g_anomaly_flag","_repo_norm","v5_primary_eval_project","v5_runtime_project","v5_scriptorium_override_status","v5_scriptorium_phase_g_bucket","v5_scriptorium_phase_g_stack_layer","v5_scriptorium_phase_g_source_audit_priority","v5_scriptorium_current_reality_status","v5_scriptorium_actual_role","v5_scriptorium_evidence_summary","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","audit_rank_num","bucket_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" +"1.0","HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","HyperTwist","1.0","160.0","193.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs","HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","6.0","HT_hyper_engine","HT_hyper_engine_0001","hypercubing / nD simulation","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.","multi-project","hypercubing / nD simulation","integrate","direct","medium","hactarce/hyperspeedcube","1.0","Locked Foundation","1.0","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.","nD / hypercubing simulation substrate","Included","P0","HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","2.0","2.0","","hactarce/hyperspeedcube","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","1.0","1","1.0","160.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"1746.0","SYSTRAN/faster-whisper","https://github.com/SYSTRAN/faster-whisper","multi-project","1.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.","huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.","Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services","deep source audit","Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.","Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.","SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0001","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","systran/faster-whisper","1.0","Donor Bench","4.0","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.","Cross-project / future-adjacent","Included","P2","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.","4.0","2.0","2.0","60.0","2.0","","systran/faster-whisper","multi-project","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","1.0","3","4.0","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.","","","" +"2.0","kkoomen/qbr","https://github.com/kkoomen/qbr","HyperTwist","2.0","158.0","191.0","A","vision / perception / AR","foundation engine","vision donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0001","computer vision / AR","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.","multi-project","computer vision / AR","integrate","heavy modification","medium","kkoomen/qbr","1.0","Locked Foundation","1.0","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.","Live cube-recognition substrate","Included","P0","kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","7705.0","4.0","","kkoomen/qbr","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2.0","1","1.0","158.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"","cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","2.0","95.0","95.0","P0","puzzle_simulation_training_donor","puzzle_simulation_training_donor","geometry_renderer_or_binding","donor bench","repurpose","architecture only","Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Validate actual implementation breadth and hidden donor subsystems before promotion.","P0 tier source audit.","cubing/alg.js may contain stronger reusable internals than its surface description suggests.","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.","Audit cubing/alg.js directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.","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","Many supplemental repos may reveal transferable abstractions after source inspection.","Exclude only after source audit proves weak or purely documentary value.","Supplemental intake row. Current exclusion posture is provisional.","medium","Supplemental intake heuristic.","medium","Pending direct source inspection.","Licensing intentionally ignored as a decision filter per canonical directive.","HyperTwist","HyperTwist","","Supplemental intake; reference docs advisory only.","cubing/alg.js is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.","HyperTwist & ScriptoriumAI.txt","0","0","1.0","0.0","HT_cube_semantics","HT_cube_semantics_0002","puzzle_simulation_training_donor","Supplemental v6 intake from hypertwist_and_scriptoriumai.","HyperTwist","puzzle_simulation_training_donor","donor candidate","moderate modification","medium","cubing/alg.js","1.0","Donor Bench","4.0","Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.","Focused restrictive clean-room donor target","included_in_v6_supplemental_intake","P2","Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.","2.0","2.0","2.0","7708.0","1.0","","cubing/alg.js","HyperTwist","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.0","1","4.0","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"","cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","2.0","95.0","95.0","P0","puzzle_simulation_training_donor","puzzle_simulation_training_donor","geometry_renderer_or_binding","donor bench","repurpose","architecture only","Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Validate actual implementation breadth and hidden donor subsystems before promotion.","P0 tier source audit.","cubing/twisty.js may contain stronger reusable internals than its surface description suggests.","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.","Audit cubing/twisty.js directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.","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","Many supplemental repos may reveal transferable abstractions after source inspection.","Exclude only after source audit proves weak or purely documentary value.","Supplemental intake row. Current exclusion posture is provisional.","medium","Supplemental intake heuristic.","medium","Pending direct source inspection.","Licensing intentionally ignored as a decision filter per canonical directive.","HyperTwist","HyperTwist","","Supplemental intake; reference docs advisory only.","cubing/twisty.js is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.","HyperTwist & ScriptoriumAI.txt","0","0","1.0","0.0","HT_cube_semantics","HT_cube_semantics_0003","puzzle_simulation_training_donor","Supplemental v6 intake from hypertwist_and_scriptoriumai.","HyperTwist","puzzle_simulation_training_donor","donor candidate","moderate modification","medium","cubing/twisty.js","1.0","Donor Bench","4.0","Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.","Focused restrictive clean-room donor target","included_in_v6_supplemental_intake","P2","Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.","2.0","2.0","2.0","7710.0","3.0","","cubing/twisty.js","HyperTwist","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.0","1","4.0","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"1747.0","coqui-ai/TTS","https://github.com/coqui-ai/TTS","multi-project","2.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","https://github.com/coqui-ai/TTS – Coqui XTTS v2.","Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","https://github.com/coqui-ai/TTS – Coqui XTTS v2.","coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0002","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","coqui-ai/tts","1.0","Donor Bench","4.0","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.","Cross-project / future-adjacent","Included","P2","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.","4.0","2.0","2.0","7713.0","4.0","","coqui-ai/tts","multi-project","","","","","","","","","","Original global Phase G v4 retained","MPL-2.0 code; mixed model payload licenses","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2.0","3","4.0","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.","","","" +"","HactarCE/2x2x2x2-Scrambler","https://github.com/HactarCE/2x2x2x2-Scrambler","HyperTwist","2.0","63.0","63.0","P2","puzzle_simulation_training_donor","puzzle_simulation_training_donor","geometry_renderer_or_binding","donor bench","repurpose","architecture only","Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Validate actual implementation breadth and hidden donor subsystems before promotion.","P2 tier source audit.","HactarCE/2x2x2x2-Scrambler may contain stronger reusable internals than its surface description suggests.","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.","Audit HactarCE/2x2x2x2-Scrambler directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.","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","Many supplemental repos may reveal transferable abstractions after source inspection.","Exclude only after source audit proves weak or purely documentary value.","Supplemental intake row. Current exclusion posture is provisional.","low-to-medium","Supplemental intake heuristic.","low-to-medium","Pending direct source inspection.","Licensing intentionally ignored as a decision filter per canonical directive.","HyperTwist","HyperTwist","","Supplemental intake; reference docs advisory only.","HactarCE/2x2x2x2-Scrambler is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.","HyperTwist & ScriptoriumAI.txt","0","0","1.0","0.0","HT_cube_semantics","HT_cube_semantics_0004","puzzle_simulation_training_donor","Supplemental v6 intake from hypertwist_and_scriptoriumai.","HyperTwist","puzzle_simulation_training_donor","future candidate","architecture only","low-to-medium","hactarce/2x2x2x2-scrambler","1.0","Donor Bench","6.0","GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.","Focused restrictive clean-room donor target","included_in_v6_supplemental_intake","P2","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.","2.0","3.0","3.0","7714.0","5.0","","hactarce/2x2x2x2-scrambler","HyperTwist","supplemental_v6_not_runtime_anchored","","","","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2.0","3","6.0","63.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier." +"3.0","vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","3.0","158.0","191.0","A","vision / perception / AR","foundation engine","vision donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb","vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.","memo","False","True","0.0","10.0","HT_cube_vision","HT_cube_vision_0002","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","vivaansinghvi07/rubix-cube-solver","1.0","Locked Parallel Foundation","2.0","Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.","Parallel foundation and reconstruction companion donor","Included","P0","vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","7819.0","110.0","","vivaansinghvi07/rubix-cube-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","3.0","1","2.0","158.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"1748.0","ggml-org/whisper.cpp","https://github.com/ggml-org/whisper.cpp","multi-project","3.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.","Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.","Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.","ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0003","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","ggml-org/whisper.cpp","1.0","Donor Bench","4.0","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.","Cross-project / future-adjacent","Included","P2","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.","4.0","2.0","2.0","7850.0","6.0","","ggml-org/whisper.cpp","multi-project","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","3.0","3","4.0","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.","","","" +"4.0","tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","4.0","156.0","189.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked core candidate","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","5.0","HT_training_stack","HT_training_stack_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","tao-yu/alg-trainer","1.0","Locked Parallel Foundation","2.0","Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.","Training / timing layer","Included","P0","tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","8548.0","111.0","","tao-yu/alg-trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4.0","1","2.0","156.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"1749.0","rhasspy/piper","https://github.com/rhasspy/piper","multi-project","4.0","71.0","80.0","C","voice / multimodal I/O","subsystem donor","multimodal donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer","deep source audit","Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).","rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.","memo","False","True","0.0","1.0","MU_misc","MU_misc_0004","voice / speech / audio","Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.","future/adjacent use","voice / speech / audio","repurpose","moderate modification","medium","rhasspy/piper","1.0","Donor Bench","4.0","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Cross-project / future-adjacent","Included","P2","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.","4.0","2.0","2.0","8565.0","8.0","","rhasspy/piper","multi-project","","","","","","","","","","Original global Phase G v4 retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4.0","3","4.0","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.","","","" +"5.0","cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","5.0","152.0","185.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","medium-high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.","cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.","memo","False","True","0.0","1.0","HT_cube_semantics","HT_cube_semantics_0001","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","cubing/cubing.js","1.0","Locked Strategic Donor","1.0","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Boundary-sensitive classic-cubing semantics and rendering donor","Included","P1","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","2.0","4.0","3.0","11771.0","112.0","","cubing/cubing.js","HyperTwist","","","","","","","","","","Original global Phase G v4 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","5.0","1","1.0","152.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable." +"6.0","cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","6.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 5","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.","memo","False","True","0.0","5.0","HT_cube_vision","HT_cube_vision_0003","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","cahidenes/rubiks-cube-solver","1.0","Locked Strategic Donor","3.0","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Active recognition-heuristics and validation donor","Included","P1","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.","2.0","5.0","3.0","11849.0","113.0","","cahidenes/rubiks-cube-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","6.0","2","3.0","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"7.0","tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","7.0","148.0","174.0","A","vision / perception / AR","foundation engine","vision donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","full subsystem extraction review","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 7","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.","memo","False","True","0.0","7.0","HT_cube_vision","HT_cube_vision_0004","computer vision / AR","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.","HyperTwist","computer vision / AR","integrate","heavy modification","medium","tentone/rubix-solver","1.0","Locked Strategic Donor","3.0","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Active native-CV donor and comparison bench","Included","P1","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.","2.0","5.0","3.0","11852.0","114.0","","tentone/rubix-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","7.0","2","3.0","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"8.0","Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","8.0","145.0","171.0","A","cubing trainer / solver / timing","foundation engine","training donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","full subsystem extraction review","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.","Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0002","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","lykos/cube_trainer","1.0","Locked Strategic Donor","3.0","Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain.","Top-tier persistent training-domain donor","Included","P1","Lykos/cube_trainer is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier persistent training-domain donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11857.0","115.0","","lykos/cube_trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","8.0","2","3.0","145.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"10.0","poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","9.0","145.0","171.0","A","interface / visualization / shell surface","foundation engine","visualization donor","locked strategic donor","integrate","direct","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions","full subsystem extraction review","Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","strong adjacency to identified core stack; memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.","memo","False","True","0.0","4.0","HT_training_stack","HT_training_stack_0016","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","poliva/cubedex","1.0","Locked Strategic Donor","3.0","Top-tier strategic donor for smartcube-aware, offline-first training UX and practical drill ergonomics, but not the owner of the long-term training backend.","Top-tier training UX and smartcube donor","Included","P1","poliva/cubedex is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier training UX and smartcube donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","5.0","3.0","11861.0","116.0","","poliva/cubedex","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","9.0","2","3.0","145.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"9.0","kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","10.0","145.0","171.0","A","hypercubing / nD engine","foundation engine","simulation donor","locked strategic donor","repurpose","architecture only","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","full subsystem extraction review","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","do not exclude","Keep in active merge-set and force full source audit before any demotion.","high","single-source signal; clear taxonomy; active integration value; foundation-level fit","high","memo mentions: 4","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source","kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.","memo","False","True","0.0","4.0","HT_hyper_engine","HT_hyper_engine_0002","cubing / algorithm training","Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.","HyperTwist","hypercubing / nD simulation","integrate","direct","medium","kash/cubedesk","1.0","Locked Strategic Donor","3.0","Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.","Restrictive clean-room donor target","Included","P1","Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.","2.0","5.0","3.0","11865.0","117.0","","kash/cubedesk","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","10.0","2","3.0","145.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." +"12.0","cutelyaware/magiccube4d","https://github.com/cutelyaware/magiccube4d/tree/master","HyperTwist","11.0","122.0","137.0","A","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","Automatically exported from code.google.com/p/magiccube4d","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","Automatically exported from code.google.com/p/magiccube4d","","cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0003","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","cutelyaware/magiccube4d","1.0","Locked Strategic Donor","5.0","Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.","Top-tier 4D interaction, history, and macro donor with attribution obligations","Included","P1","Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.","2.0","3.0","3.0","11871.0","118.0","","cutelyaware/magiccube4d","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","11.0","3","5.0","122.0","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.","Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.","Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.","medium","custom-license-attribution-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly." +"13.0","roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","12.0","122.0","137.0","A","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","4D Megaminx Analogue","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","4D Megaminx Analogue","","roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0004","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.","HyperTwist","hypercubing / nD simulation","integrate","heavy modification","medium","roice3/magic120cell","1.0","Locked Strategic Donor","5.0","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Specialized 4D interaction and puzzle-UX donor","Included","P1","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","2.0","3.0","3.0","11875.0","119.0","","roice3/magic120cell","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","12.0","3","5.0","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"14.0","roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","13.0","122.0","137.0","A","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","5D Rubik's Cube Analogue","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","5D Rubik's Cube Analogue","","roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0005","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","roice3/magiccube5d","1.0","Locked Strategic Donor","5.0","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Specialized 5D cube interaction, progress, and macro donor","Included","P1","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","2.0","3.0","3.0","11879.0","120.0","","roice3/magiccube5d","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","13.0","3","5.0","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"11.0","cs0x7f/cstimer","https://github.com/cs0x7f/cstimer","HyperTwist","14.0","121.0","147.0","A","gold-standard timer benchmark","benchmark","Gold-standard timer benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.","Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.","Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","behavior and acceptance-test benchmark review","Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.","high","Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","high","Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","cs0x7f/cstimer — GPL timer/training platform; keep only as the gold-standard timer benchmark.","cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.","memo","False","True","0.0","5.0","HT_timer_training","HT_timer_training_0001","Gold-standard timer benchmark","Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.","HyperTwist","Gold-standard timer benchmark","future candidate","architecture only","medium","cs0x7f/cstimer","1.0","Reserve Bench","3.0","GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.","Gold-standard timer benchmark","Included","P2","Keep in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.","2.0","5.0","3.0","11881.0","121.0","","cs0x7f/cstimer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","14.0","2","3.0","121.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.","high","gpl-timer-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle." +"16.0","aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","16.0","119.0","134.0","B","reference-only XR benchmark","benchmark","Reference-only XR benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.","Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.","Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","behavior-level benchmark review","Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.","Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?","Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.","high","Source-backed dossier and license verification collapse the old donor thesis.","high","Source-backed dossier and license verification collapse the old donor thesis.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","aMonteSl/CodeXR — GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.","aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.","memo","False","True","0.0","3.0","HT_cube_vision","HT_cube_vision_0005","Reference-only XR benchmark","Reference-only XR benchmark for HyperTwist; not a donor lane.","HyperTwist","Reference-only XR benchmark","future candidate","architecture only","medium","amontesl/code-xr","1.0","Reserve Bench","5.0","GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.","Reference-only XR benchmark","Included","P3","Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.","2.0","3.0","3.0","11890.0","3226.0","","amontesl/codexr","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0-only","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","16.0","3","5.0","119.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-reference-only-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows." +"17.0","brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","17.0","119.0","134.0","B","vision / perception / AR","subsystem donor","vision donor","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 3","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.","memo","False","True","0.0","3.0","HT_cube_vision","HT_cube_vision_0006","cubing / algorithm training","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.","multi-project","computer vision / AR","integrate","heavy modification","medium","brianpeiris/riftsketch","1.0","Reserve Bench","5.0","Useful MIT WebXR interaction benchmark for spatial editor panels, world-space monitors, and keyboard-first immersive tooling, but explicitly below the HyperTwist core tier.","XR interaction and spatial-UI bench","Included","P2","brianpeiris/RiftSketch is placed in Reserve Bench for HyperTwist because it best serves the 'XR interaction and spatial-UI bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","3.0","3.0","11894.0","3227.0","","brianpeiris/riftsketch","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","17.0","3","5.0","119.0","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.","Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope." +"21.0","abunickabhi/5style-Trainer","https://github.com/abunickabhi/5style-Trainer","HyperTwist","18.0","118.0","133.0","B","cubing trainer / solver / timing","subsystem donor","training donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","strong adjacency to identified core stack; memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).","abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0006","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","direct","medium","abunickabhi/5style-trainer","1.0","Donor Bench","5.0","Focused advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.","Focused advanced-training donor","Included","P2","abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","3.0","3.0","11898.0","122.0","","abunickabhi/5style-trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","18.0","3","5.0","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"18.0","MathewKJ2048/Rubiks-cube-simulator","https://github.com/MathewKJ2048/Rubiks-cube-simulator","HyperTwist","19.0","118.0","133.0","B","clean-room simulator benchmark","benchmark","Clean-room simulator benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.","Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.","Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in text-command grammar, move-history logging, and timed step playback.","Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?","Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.","Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.","high","The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.","high","The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","MathewKJ2048/Rubiks-cube-simulator — GPL-3.0 simulator; keep only as a clean-room simulator benchmark.","MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.","memo","False","True","0.0","2.0","HT_training_clean_room","HT_training_clean_room_0004","Clean-room simulator benchmark","Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room simulator benchmark","future candidate","architecture only","medium","mathewkj2048/rubiks-cube-simulator","1.0","Reserve Bench","5.0","GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material.","Clean-room simulator benchmark","Included","P3","Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors.","2.0","3.0","3.0","11901.0","123.0","","mathewkj2048/rubiks-cube-simulator","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","19.0","3","5.0","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.","Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." +"19.0","NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","20.0","118.0","133.0","B","vision / perception / AR","subsystem donor","vision donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.","memo","False","True","0.0","2.0","HT_cube_vision","HT_cube_vision_0007","cubing / algorithm training","Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.","multi-project","computer vision / AR","integrate","heavy modification","medium","nuilab/code-vr","1.0","Donor Bench","5.0","MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.","XR pedagogy and code-to-scene representation donor","Included","P2","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.","2.0","3.0","3.0","11904.0","3228.0","","nuilab/code-vr","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","20.0","3","5.0","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"20.0","ShellPuppy/RCube","https://github.com/ShellPuppy/RCube","HyperTwist","21.0","118.0","133.0","B","large-N solver benchmark","benchmark","Large-N solver benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.","Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.","Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","algorithm benchmark review","Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.","Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?","Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.","high","Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.","high","Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","ShellPuppy/RCube — GPL large-N cube solver; keep only as a large-N solver benchmark.","ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.","memo","False","True","0.0","2.0","HT_solver_oracles","HT_solver_oracles_0001","Large-N solver benchmark","Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.","HyperTwist","Large-N solver benchmark","future candidate","architecture only","medium","shellpuppy/rcube","1.0","Reserve Bench","5.0","GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.","Large-N solver benchmark","Included","P3","Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.","2.0","3.0","3.0","11907.0","124.0","","shellpuppy/rcube","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","21.0","3","5.0","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." +"22.0","brownan/Rubiks-Cube-Solver","https://github.com/brownan/Rubiks-Cube-Solver","HyperTwist","22.0","118.0","133.0","B","cubing trainer / solver / timing","subsystem donor","training donor","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.","brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0007","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","brownan/rubiks-cube-solver","1.0","Reserve Bench","5.0","GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.","Benchmark oracle and clean-room optimal-solver candidate","Included","P2","Keep as a primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.","2.0","3.0","3.0","11910.0","125.0","","brownan/rubiks-cube-solver","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","22.0","3","5.0","118.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.","Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for any later first-party optimal-solver effort.","high","gpl-oracle-clean-room-review","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." +"24.0","newyork-anthonyng/rubiks-cross-trainer","https://github.com/newyork-anthonyng/rubiks-cross-trainer","HyperTwist","24.0","118.0","133.0","B","cubing trainer / solver / timing","subsystem donor","training donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.","newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0008","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","newyork-anthonyng/rubiks-cross-trainer","1.0","Donor Bench","5.0","Focused donor for the precomputed cross-difficulty corpus and CFOP micro-drill progression rather than a broader training-platform shell.","Focused donor","Included","P2","newyork-anthonyng/rubiks-cross-trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","3.0","3.0","11916.0","126.0","","newyork-anthonyng/rubiks-cross-trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","24.0","3","5.0","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"25.0","vwcwong/CubeSim","https://github.com/vwcwong/CubeSim","HyperTwist","25.0","118.0","133.0","B","clean-room state/history benchmark","benchmark","Clean-room state/history benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: cleaner domain architecture for simulator state/history separation, parser/scramble modules, and replay/history behavior suitable for clean-room reimplementation.","Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party state/history and replay behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in state/history separation, parser/scramble modularity, and replay-oriented architecture.","Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?","Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.","Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL simulator code and should remain only as a clean-room state/history benchmark.","high","The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.","high","The dossier-backed classification is stable: retain only the cleaner state/history architecture through a clean-room path.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","vwcwong/CubeSim — GPL simulator; keep only as a clean-room state/history benchmark.","vwcwong/CubeSim is retained only as a clean-room state/history benchmark. Its value is architectural and behavioral, not donor code.","memo","False","True","0.0","2.0","HT_training_clean_room","HT_training_clean_room_0005","Clean-room state/history benchmark","Clean-room state/history benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room state/history benchmark","future candidate","architecture only","medium","vwcwong/cubesim","1.0","Reserve Bench","5.0","GPL simulator with unusually clean state/history architecture; retain only as clean-room benchmark material.","Clean-room state/history benchmark","Included","P3","Keep in canon only as a clean-room state/history benchmark for first-party simulator architecture.","2.0","3.0","3.0","11919.0","127.0","","vwcwong/cubesim","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","25.0","3","5.0","118.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.","Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use." +"26.0","AviKaufman/Rubix-cube-trainer","https://github.com/AviKaufman/Rubix-cube-trainer","HyperTwist","26.0","117.0","132.0","B","clean-room pedagogy benchmark","benchmark","Clean-room pedagogy benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: beginner-method teaching flow, step guidance, and tutorial-state behavior worth preserving through a clean-room spec.","Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in beginner-method pedagogy flow, guidance cadence, and tutorial-state transitions.","Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?","Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.","Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is explicitly all-rights-reserved and should remain only as a clean-room pedagogy benchmark.","high","The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.","high","The all-rights-reserved posture and the narrow pedagogy use case clearly block donor treatment.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","AviKaufman/Rubix-cube-trainer — all rights reserved; keep only as a clean-room pedagogy benchmark.","AviKaufman/Rubix-cube-trainer is retained only as a clean-room pedagogy benchmark. Its value is in teaching flow and tutorial behavior, not donor code.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0003","Clean-room pedagogy benchmark","Clean-room pedagogy benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room pedagogy benchmark","future candidate","architecture only","medium","avikaufman/rubix-cube-trainer","1.0","Reserve Bench","5.0","All-rights-reserved repo with narrow teaching-flow value; retain only as clean-room benchmark material.","Clean-room pedagogy benchmark","Included","P3","Keep in canon only as a clean-room pedagogy benchmark for first-party teaching-flow work.","2.0","3.0","3.0","11922.0","128.0","","avikaufman/rubix-cube-trainer","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","26.0","3","5.0","117.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.","Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source or assets directly without separate rights.","Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary.","high","all-rights-reserved-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design." +"27.0","alinen/cube","https://github.com/alinen/cube","HyperTwist","27.0","117.0","132.0","B","clean-room planner benchmark","benchmark","Clean-room planner benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: guided lesson flow, cube-state handling, and bounded planner/search behavior suitable for first-party clean-room reimplementation.","Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only.","Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in bounded planner/search flow and guided lesson state transitions.","Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?","Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.","Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo has no explicit license visible and should remain only as a clean-room planner benchmark.","medium","The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.","medium","The benchmark thesis is clear, but the repo remains small and non-permissive in practice because no explicit license is visible.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","alinen/cube — no explicit license visible; keep only as a clean-room planner benchmark.","alinen/cube is retained only as a clean-room planner benchmark. Its useful value is behavioral and architectural, not donor-grade.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0001","Clean-room planner benchmark","Clean-room planner benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room planner benchmark","future candidate","architecture only","medium","alinen/cube","1.0","Reserve Bench","5.0","No explicit license visible and limited scope; retain only for clean-room planner behavior extraction.","Clean-room planner benchmark","Included","P3","Keep in canon only as a clean-room planner benchmark for first-party guided-lesson and planner work.","2.0","3.0","3.0","11925.0","129.0","","alinen/cube","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","27.0","3","5.0","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." +"28.0","ambisinister/blindsolve","https://github.com/ambisinister/blindsolve","HyperTwist","28.0","117.0","132.0","B","clean-room BLD memo benchmark","benchmark","Clean-room BLD memo benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: narrow memo-practice behavior and BLD training flow worth preserving through a clean-room spec.","Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","clean-room benchmark review","Hidden value sits in narrow memo-practice flow and user-feedback behavior.","Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?","Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.","Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo has no explicit license visible and does not justify donor treatment; retain only as a clean-room memo benchmark.","medium","The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.","medium","The clean-room benchmark role is clear, but the repo is narrow and license posture remains non-permissive in practice.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","ambisinister/blindsolve — no explicit license visible; keep only as a clean-room BLD memo benchmark.","ambisinister/blindsolve is retained only as a clean-room BLD memo benchmark. Its value is in a narrow behavior slice, not in donor code.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0002","Clean-room BLD memo benchmark","Clean-room BLD memo benchmark for HyperTwist; retained for behavior extraction only.","HyperTwist","Clean-room BLD memo benchmark","future candidate","architecture only","medium","ambisinister/blindsolve","1.0","Reserve Bench","5.0","No explicit license visible and extremely narrow scope; retain only as clean-room benchmark material.","Clean-room BLD memo benchmark","Included","P3","Keep in canon only as a clean-room BLD memo benchmark for later first-party micro-mode work.","2.0","3.0","3.0","11928.0","130.0","","ambisinister/blindsolve","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","28.0","3","5.0","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." +"29.0","efrantar/rob-twophase","https://github.com/efrantar/rob-twophase","HyperTwist","29.0","117.0","132.0","B","solver oracle / robot-metric benchmark","benchmark","Solver oracle and robot-metric benchmark","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: correctness oracle, robot/axial-metric comparisons, multiple-solution search expectations, and pruning-table performance baselines.","Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code.","Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests.","Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","oracle benchmark review","Hidden value sits in metric handling, pruning-table organization, CLI oracle behavior, and multi-solution search expectations.","Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?","Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.","Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","exclude from donor lane","The repo is GPL solver code and should remain only as a correctness/performance oracle and robot-metric benchmark.","high","Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.","high","Dossier-backed classification is stable: the retained value is oracle and metric benchmarking, not direct incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","efrantar/rob-twophase — GPL two-phase solver; keep only as solver oracle and robot-metric benchmark.","efrantar/rob-twophase remains valuable because it is a strong correctness/performance oracle with robot-metric coverage. That value is benchmark authority, not donor code.","memo","False","True","0.0","1.0","HT_solver_oracles","HT_solver_oracles_0002","Solver oracle and robot-metric benchmark","Solver oracle and robot-metric benchmark for HyperTwist; retained for acceptance testing, not donor use.","HyperTwist","Solver oracle and robot-metric benchmark","future candidate","architecture only","medium","efrantar/rob-twophase","1.0","Reserve Bench","5.0","GPL solver/oracle repo whose retained value is correctness, performance, and metric benchmarking rather than donor use.","Solver oracle and robot-metric benchmark","Included","P2","Keep in canon as a restrictive solver oracle benchmark with robot-metric value.","2.0","3.0","3.0","11931.0","131.0","","efrantar/rob-twophase","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","29.0","3","5.0","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." +"30.0","onionhoney/roux-trainers","https://github.com/onionhoney/roux-trainers","HyperTwist","30.0","117.0","132.0","B","method-specific training donor","restrictive donor","clean-room donor","donor bench","repurpose","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Focused restrictive clean-room donor target. Retain the stage-specific training modes, solver-backed analyzer behavior, recognition masking, favorites/batch-drill flow, and 2D/3D training visualization ideas through Model A / Model B separation.","Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code.","Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary.","Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value sits in state-machine-driven training flows, solver-backed analyzer behavior, recognition masking, favorites persistence, and batch-drill mechanics.","Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?","Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","HyperTwist only","Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing.","exclude from direct code use, keep as clean-room donor","The repo is GPLv3 and too method-specific for direct incorporation, but it still contains real training/analyzer subsystem value worth preserving through a clean-room donor path.","high","The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.","high","The dossier-backed classification is stable: stronger than a passive benchmark, but clearly a restrictive clean-room donor rather than direct donor code.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","onionhoney/roux-trainers — GPLv3 Roux trainer; keep as a focused restrictive clean-room donor, not direct donor code.","onionhoney/roux-trainers remains valuable because it contains stage-specific training-state machines, solver-backed analyzer modes, recognition masking, and batch-drill patterns. That value should flow through a clean-room donor path, not direct incorporation.","memo","False","True","0.0","1.0","HT_training_clean_room","HT_training_clean_room_0006","Focused restrictive clean-room donor target","Focused restrictive clean-room donor target for HyperTwist; stronger than a passive benchmark, but still not direct donor code.","HyperTwist","Focused restrictive clean-room donor target","repurpose","architecture only","medium","onionhoney/roux-trainers","1.0","Donor Bench","5.0","GPLv3 method-specific trainer with real subsystem value that should be preserved through clean-room extraction rather than donor use.","Focused restrictive clean-room donor target","Included","P2","Keep in canon as a focused restrictive clean-room donor for method-specific training and analyzer behavior.","2.0","3.0","3.0","11934.0","132.0","","onionhoney/roux-trainers","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","30.0","3","5.0","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." +"31.0","yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","31.0","117.0","132.0","B","vision / perception / AR","subsystem donor","vision donor","Reserve Bench","future candidate","architecture only","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from standalone? no","Not necessarily the final base, but keep as an active subsystem candidate or major donor.","medium","single-source signal; clear taxonomy; active integration value","medium","memo mentions: 1","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.","yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.","memo","False","True","0.0","1.0","HT_cube_vision","HT_cube_vision_0008","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","yakupbilen/drl-rubiks-cube","1.0","Reserve Bench","5.0","Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.","Search/training systems bench","Included","P2","yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","3.0","3.0","11937.0","133.0","","yakupbilen/drl-rubiks-cube","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","31.0","3","5.0","117.0","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.","Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." +"32.0","Hypercubers/hypercubing.xyz","https://github.com/Hypercubers/hypercubing.xyz","HyperTwist","32.0","92.0","101.0","C","hypercubing / nD engine","subsystem donor","simulation donor","locked strategic donor","repurpose","moderate modification","Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","Website for the Hypercubing community","Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format","deep source audit","Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","Website for the Hypercubing community","","Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0006","hypercubing / nD simulation","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.","HyperTwist","hypercubing / nD simulation","integrate","heavy modification","medium","hypercubers/hypercubing.xyz","1.0","Locked Strategic Donor","4.0","MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.","Knowledge and curriculum donor","Included","P1","Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.","2.0","2.0","2.0","11938.0","134.0","Thin-fit assignment; verify project mapping during source audit","hypercubers/hypercubing.xyz","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","32.0","3","4.0","92.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.","Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.","high","permissive-knowledge-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." +"34.0","Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","34.0","88.0","97.0","C","cubing trainer / solver / timing","subsystem donor","training donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks","deep source audit","Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium","single-source signal; clear taxonomy; mostly donor/reference role","medium","strong adjacency to identified core stack; memo mentions: 2","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","","","","Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.","Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.","memo","False","True","0.0","2.0","HT_training_stack","HT_training_stack_0015","cubing / algorithm training","Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","aarav2709/kubetimr","1.0","Donor Bench","4.0","Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.","Focused subsystem donor","Included","P2","Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","2.0","3.0","2.0","11944.0","135.0","","aarav2709/kubetimr","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","34.0","3","4.0","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","routine-review-only","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." +"36.0","roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","36.0","88.0","97.0","C","infra / runtime / observability / integration","subsystem donor","integration utility","locked strategic donor","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.","Non-euclidean Rubik's Cube Analogues","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API","deep source audit","Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.","Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","Non-euclidean Rubik's Cube Analogues","","roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.","bookmarks","True","False","1.0","0.0","HT_hyper_engine","HT_hyper_engine_0007","cubing / algorithm training","Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.","HyperTwist","cubing / algorithm training","integrate","moderate modification","medium","roice3/magictile","1.0","Locked Strategic Donor","4.0","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Top-tier non-Euclidean geometry and topology donor","Included","P1","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","2.0","2.0","2.0","11950.0","136.0","Thin-fit assignment; verify project mapping during source audit","roice3/magictile","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","36.0","3","4.0","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"41.0","PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","41.0","72.0","81.0","C","telemetry / replay / feature governance","subsystem donor","telemetry donor","donor bench","repurpose","moderate modification","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.","Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter","deep source audit","Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.","medium-low","single-source signal; clear taxonomy; mostly donor/reference role","medium","explicit bookmark description available","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.","HyperTwist(1)","HyperTwist Consider","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.","","PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.","bookmarks","True","False","1.0","0.0","HT_control_plane","HT_control_plane_0001","cloud / infra / observability / api","Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.","HyperTwist","telemetry / replay / feature governance","repurpose","moderate modification","medium","posthog/posthog","1.0","Donor Bench","4.0","Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.","Telemetry / replay / feature-governance donor","Included","P2","PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.","2.0","2.0","2.0","11966.0","139.0","Thin-fit assignment; verify project mapping during source audit","posthog/posthog","HyperTwist","","","","","","","","","","Original global Phase G v4 retained","MIT outside ee/; enterprise-restricted in ee/","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","41.0","3","4.0","72.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.","Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed." +"","met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","donor bench","repurpose","moderate modification","Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.","","Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.","","Repurpose here means: turn it into a browser-side embodied coach or companion layer.","","","","Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0001","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","met4citizen/talkinghead","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Browser embodied coach surface","Included","P2","met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","","","","","","","met4citizen/talkinghead","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +"","apache/echarts","https://github.com/apache/echarts","HyperTwist","","","","","analytics / visualization / reporting","subsystem donor","interface donor","donor bench","repurpose","moderate modification","Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.","","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.","","Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.","","","","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0002","analytics / visualization / reporting","Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.","HyperTwist","analytics / visualization / reporting","repurpose","moderate modification","medium","apache/echarts","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Browser analytics and reporting surface","Included","P2","apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","","","","","","","apache/echarts","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." +"","ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","visualization donor","merge bench","integrate","moderate modification","Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.","","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.","","Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.","","","","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0003","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","ecomfe/echarts-gl","","Merge Bench","5.0","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Browser 3D analytics and explainer surface","Included","P3","ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","","","","","","","ecomfe/echarts-gl","","","","","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." +"","KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","viewer donor","donor bench","repurpose","moderate modification","Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.","","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.","","Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.","","","","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0004","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","khronosgroup/gltf-sample-viewer","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Browser asset validation and viewer surface","Included","P3","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.","","","","","","","khronosgroup/gltf-sample-viewer","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer","https://github.com/google/model-viewer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","viewer donor","donor bench","repurpose","moderate modification","Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.","","Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.","","","","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0005","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","google/model-viewer","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.","Browser 3D presentation and inspection surface","Included","P2","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.","","","","","","","google/model-viewer","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.","Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." +"","mrdoob/three.js","https://github.com/mrdoob/three.js","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.","","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.","","Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.","","","","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0006","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","mrdoob/three.js","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.","Browser 3D substrate","Included","P2","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.","","","","","","","mrdoob/three.js","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.","Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"","pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.","","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.","","Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.","","","","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0007","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/postprocessing","","Merge Bench","5.0","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Browser post-processing substrate","Included","P3","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.","","","","","","","pmndrs/postprocessing","","","","","","","","","","","","Zlib","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.","Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser post-effect substrate beneath the landed browser spatial owner trio; do not treat it as separately live." +"","pmndrs/react-three-fiber","https://github.com/pmndrs/react-three-fiber","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.","","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.","","Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.","","","","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0008","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","pmndrs/react-three-fiber","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.","Browser React 3D substrate","Included","P2","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.","","","","","","","pmndrs/react-three-fiber","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.","Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"","pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","merge bench","integrate","moderate modification","Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.","","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.","","Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.","","","","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0009","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/drei","","Merge Bench","5.0","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Browser 3D helper and abstraction layer","Included","P3","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.","","","","","","","pmndrs/drei","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/xr","https://github.com/pmndrs/xr","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interaction donor","donor bench","repurpose","moderate modification","Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.","","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.","","Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.","","","","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0010","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","pmndrs/xr","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.","Browser XR and immersive UI substrate","Included","P2","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.","","","","","","","pmndrs/xr","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.","Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"","pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","donor bench","repurpose","moderate modification","Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.","","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.","","Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.","","","","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0011","browser / 3D / XR / presentation","Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.","HyperTwist","browser / 3D / XR / presentation","repurpose","moderate modification","medium","pmndrs/uikit","","Donor Bench","4.0","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Browser spatial UI surface","Included","P2","pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","","","","","","","pmndrs/uikit","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser spatial UI layer beside the landed pmndrs/xr lane; do not treat it as separately live." +"","pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interaction donor","merge bench","integrate","moderate modification","Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.","","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.","","Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.","","","","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_surface","HT_browser_surface_0012","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/react-spring","","Merge Bench","5.0","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Browser motion and animation layer","Included","P3","pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","","","","","","","pmndrs/react-spring","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side motion substrate inside the landed browser spatial support stack; do not treat it as separately live." +"","screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","","","","","capture / replay / support-plane","subsystem donor","support donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_support_sidecars","HT_support_sidecars_0001","support plane / capture / replay","Repurpose selectively for HyperTwist. Its source-backed role is a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","HyperTwist","support plane / capture / replay","repurpose","moderate modification","medium","screenpipe/screenpipe","","Donor Bench","4.0","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.","Support-plane capture, history, and replay sidecar","Included","P2","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.","","","","","","","screenpipe/screenpipe","","","","","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." +"","remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","","","","","media / rendering / export","subsystem donor","media donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_support_sidecars","HT_support_sidecars_0002","media / rendering / export","Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","HyperTwist","media / rendering / export","repurpose","moderate modification","medium","remotion-dev/remotion","","Donor Bench","4.0","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.","Commercially licensed media-export and explainer sidecar","Included","P3","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.","","","","","","","remotion-dev/remotion","","","","","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use." +"","ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0001","browser / 2D / visualization","Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","HyperTwist","browser / 2D / visualization","integrate","moderate modification","medium","ecomfe/zrender","","Merge Bench","5.0","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.","Browser 2D render substrate","Included","P3","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.","","","","","","","ecomfe/zrender","","","","","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live." +"","pissang/claygl","https://github.com/pissang/claygl","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0002","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pissang/claygl","","Merge Bench","5.0","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.","Browser WebGL substrate","Included","P3","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.","","","","","","","pissang/claygl","","","","","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"","pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","viewer donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0003","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pissang/clay-viewer","","Merge Bench","5.0","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.","Browser viewer and editor sidecar","Included","P3","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.","","","","","","","pissang/clay-viewer","","","","","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"","KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0004","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","khronosgroup/gltf-sample-renderer","","Merge Bench","5.0","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.","Browser asset renderer substrate","Included","P3","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.","","","","","","","khronosgroup/gltf-sample-renderer","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." +"","google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","editor donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0005","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","google/model-viewer/packages/space-opera","","Merge Bench","5.0","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.","Browser asset editor and inspection surface","Included","P3","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.","","","","","","","google/model-viewer/packages/space-opera","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","","","","","analytics / visualization / reporting","subsystem donor","qa donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0006","browser / QA / visual regression","Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","HyperTwist","browser / QA / visual regression","integrate","moderate modification","medium","google/model-viewer/packages/render-fidelity-tools","","Merge Bench","5.0","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.","Browser fidelity QA harness","Included","P3","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.","","","","","","","google/model-viewer/packages/render-fidelity-tools","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","effect donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0007","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","google/model-viewer/packages/model-viewer-effects","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Browser emphasis and post-processing extension","Included","P3","google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","","","","","","","google/model-viewer/packages/model-viewer-effects","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." +"","google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","docs donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0008","documentation / demos / examples","Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.","HyperTwist","documentation / demos / examples","integrate","moderate modification","medium","google/model-viewer/packages/modelviewer.dev","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Browser docs and demo surface","Included","P4","google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","","","","","","","google/model-viewer/packages/modelviewer.dev","","","","","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." +"","google/model-viewer/packages/shared-assets","https://github.com/google/model-viewer/tree/main/packages/shared-assets","HyperTwist","","","","","asset / fixture / sample pack","subsystem donor","fixture donor","donor bench","repurpose","architecture only","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0009","asset / fixture / sample pack","Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.","HyperTwist","asset / fixture / sample pack","integrate","moderate modification","medium","google/model-viewer/packages/shared-assets","","Donor Bench","5.0","Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.","Boundary-sensitive sample-asset and test-fixture pack","Included","P3","Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.","","","","","","","google/model-viewer/packages/shared-assets","","","","","","","","","","","","Apache-2.0 container; mixed per-asset terms","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.","Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.","Preserve container notices and review each selected asset attribution or usage condition separately before shipping.","Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.","high","mixed-asset-whitelist-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use." +"","pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0010","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/react-postprocessing","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Browser React effect-wrapper layer","Included","P4","pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","","","","","","","pmndrs/react-postprocessing","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate React wrapper above pmndrs/postprocessing inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0011","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","pmndrs/three-stdlib","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Browser 3D utility substrate","Included","P4","pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","","","","","","","pmndrs/three-stdlib","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate shared utility shelf beneath the landed browser spatial owner trio; do not treat it as separately live." +"","pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0012","browser / utilities / math","Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","HyperTwist","browser / utilities / math","integrate","moderate modification","medium","pmndrs/maath","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Browser math-helper substrate","Included","P4","pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","","","","","","","pmndrs/maath","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate math-helper layer inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0013","browser / state / interaction","Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","HyperTwist","browser / state / interaction","repurpose","moderate modification","medium","pmndrs/zustand","","Donor Bench","4.0","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Browser state-management substrate","Included","P3","pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","","","","","","","pmndrs/zustand","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side state substrate inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0014","browser / state / interaction","Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","HyperTwist","browser / state / interaction","integrate","moderate modification","medium","pmndrs/leva","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Browser control-panel and parameter UI layer","Included","P4","pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","","","","","","","pmndrs/leva","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate authoring and debug control sidecar inside the landed browser spatial support stack; do not treat it as separately live." +"","pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0015","browser / state / interaction","Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.","HyperTwist","browser / state / interaction","repurpose","moderate modification","medium","pmndrs/use-gesture","","Donor Bench","4.0","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Browser gesture and pointer-input substrate","Included","P3","pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","","","","","","","pmndrs/use-gesture","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser gesture and pointer-input substrate inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","interface donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0016","browser / 3D / XR / presentation","Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","HyperTwist","browser / 3D / XR / presentation","integrate","moderate modification","medium","@react-spring/parallax","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Browser layered-motion and explainer sidecar","Included","P4","@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","","","","","","","@react-spring/parallax","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","Use directly as a bounded browser-side dependency for explainer and narrative surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate layered-motion sidecar beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0017","browser / utilities / scheduling","Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","HyperTwist","browser / utilities / scheduling","integrate","moderate modification","medium","@react-spring/rafz","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Browser frame-loop and scheduling utility","Included","P4","@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","","","","","","","@react-spring/rafz","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0018","browser / utilities / animation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","HyperTwist","browser / utilities / animation","integrate","moderate modification","medium","@react-spring/animated","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Browser animatable-component substrate","Included","P4","@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","","","","","","","@react-spring/animated","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate animatable-component package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","donor bench","repurpose","moderate modification","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0019","browser / utilities / animation","Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","HyperTwist","browser / utilities / animation","repurpose","moderate modification","medium","@react-spring/core","","Donor Bench","4.0","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Browser spring-runtime core","Included","P3","@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","","","","","","","@react-spring/core","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate spring-runtime core beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0020","browser / utilities / animation","Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","HyperTwist","browser / utilities / animation","integrate","moderate modification","medium","@react-spring/shared","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Browser motion utility substrate","Included","P4","@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","","","","","","","@react-spring/shared","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"","@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","","","","","interface / visualization / shell surface","subsystem donor","dependency donor","merge bench","integrate","moderate modification","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","","","","","","","","","","","","","","medium","Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.","medium","Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.","","","","","","","","","","","","HT_browser_support","HT_browser_support_0021","browser / utilities / animation","Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","HyperTwist","browser / utilities / animation","integrate","moderate modification","medium","@react-spring/types","","Merge Bench","5.0","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Browser motion type-contract substrate","Included","P4","@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","","","","","","","@react-spring/types","","","","","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","Use directly as a bounded browser-side dependency where those contracts are actually needed.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate type-contract package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." diff --git a/docs/repo_portfolio_unified_source_audit_v6_3.csv b/docs/repo_portfolio_unified_source_audit_v6_3.csv index 06d32c1..31a1d11 100644 --- a/docs/repo_portfolio_unified_source_audit_v6_3.csv +++ b/docs/repo_portfolio_unified_source_audit_v6_3.csv @@ -1,5 +1,5 @@ -repo,primary_url,project,phase_g_bucket,stack_layer,audit_tier,tier_queue_order,global_order,wave_number,portfolio_priority_score,execution_priority_score_v3,current_confidence,modification_scope_detail_v3,recommended_action_v2,repurposing_potential_v2,audit_goal,inspect_emphasis,source_code_audit_targets,source_inspection_questions,integration_realization_detail,consolidation_detail,repurpose_detail,merger_partner_1,merger_type_1,merger_rationale_1,merger_partner_2,merger_type_2,merger_rationale_2,merger_partner_3,merger_type_3,merger_rationale_3,cross_project_transfer_targets,cross_project_transfer_rationale,reclassify_up_if,reclassify_down_if,deliverable_expected,session_note_template,recommended_context_packet,phase_g_master_list_rationale,phase_g_bucket_reason,coding_model_instruction_v3,source_audit_packet_id,cluster_tag,_repo_norm,v5_runtime_project,v5_scriptorium_override_status,v5_scriptorium_bucket,v5_scriptorium_stack_layer,v5_scriptorium_current_reality_status,v5_scriptorium_supersedes_prior_assessment,v5_source_of_truth,v6_license_annotation,v6_license_annotation_status,v6_license_annotation_source,v6_supplemental_intake_present,v6_supplemental_source_groups,v6_supplemental_source_sections,v6_supplemental_source_files,v6_reference_material_position,v6_kali_agent_access_relevance,v6_branch_seed_prompt_included,v6_branch_seed_scope,v6_intake_wave,v6_notes,v6_source_of_truth,project_rank_num,tier_rank_num,priority_num,copyleft_relevance_v6_1,copyleft_strategy_v6_1,copyleft_rationale_v6_1,preferred_boundary_model_v6_1,open_compliance_if_used_as_is_v6_1,reverse_engineer_if_proprietary_core_needed_v6_1,copyleft_strategy_confidence_v6_1,copyleft_manual_review_trigger_v6_1,as_is_incorporation_sensible_v6_1,v6_2_sre_layer,v6_2_sre_stratum,v6_2_sre_role,v6_2_sre_family,v6_2_related_kali_package,v6_2_related_upstream_repo,v6_2_kali_package_suffices_for_tool_execution,v6_2_upstream_repo_preferred_for_deep_eval,v6_2_index_page_followup_useful,v6_2_index_page_followup_reason,v6_2_sre_notes,v6_2_dnspy_ilspy_relevance,v6_3_source_of_truth,v6_3_merge_note,v6_3_live_state_2026_05_11,v6_3_reset_lane_2026_05_11,v6_3_reset_next_step_2026_05_11 -HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,Locked Foundation,nD / hypercubing simulation substrate,P0,20,9203,2.0,160.0,193.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",integrate,direct,"Validate whether HactarCE/Hyperspeedcube truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.",Architecture note + salvage map + integration recipe + reclassification verdict,"1) Confirmed visible capabilities +"repo","primary_url","project","phase_g_bucket","stack_layer","audit_tier","tier_queue_order","global_order","wave_number","portfolio_priority_score","execution_priority_score_v3","current_confidence","modification_scope_detail_v3","recommended_action_v2","repurposing_potential_v2","audit_goal","inspect_emphasis","source_code_audit_targets","source_inspection_questions","integration_realization_detail","consolidation_detail","repurpose_detail","merger_partner_1","merger_type_1","merger_rationale_1","merger_partner_2","merger_type_2","merger_rationale_2","merger_partner_3","merger_type_3","merger_rationale_3","cross_project_transfer_targets","cross_project_transfer_rationale","reclassify_up_if","reclassify_down_if","deliverable_expected","session_note_template","recommended_context_packet","phase_g_master_list_rationale","phase_g_bucket_reason","coding_model_instruction_v3","source_audit_packet_id","cluster_tag","_repo_norm","v5_runtime_project","v5_scriptorium_override_status","v5_scriptorium_bucket","v5_scriptorium_stack_layer","v5_scriptorium_current_reality_status","v5_scriptorium_supersedes_prior_assessment","v5_source_of_truth","v6_license_annotation","v6_license_annotation_status","v6_license_annotation_source","v6_supplemental_intake_present","v6_supplemental_source_groups","v6_supplemental_source_sections","v6_supplemental_source_files","v6_reference_material_position","v6_kali_agent_access_relevance","v6_branch_seed_prompt_included","v6_branch_seed_scope","v6_intake_wave","v6_notes","v6_source_of_truth","project_rank_num","tier_rank_num","priority_num","copyleft_relevance_v6_1","copyleft_strategy_v6_1","copyleft_rationale_v6_1","preferred_boundary_model_v6_1","open_compliance_if_used_as_is_v6_1","reverse_engineer_if_proprietary_core_needed_v6_1","copyleft_strategy_confidence_v6_1","copyleft_manual_review_trigger_v6_1","as_is_incorporation_sensible_v6_1","v6_2_sre_layer","v6_2_sre_stratum","v6_2_sre_role","v6_2_sre_family","v6_2_related_kali_package","v6_2_related_upstream_repo","v6_2_kali_package_suffices_for_tool_execution","v6_2_upstream_repo_preferred_for_deep_eval","v6_2_index_page_followup_useful","v6_2_index_page_followup_reason","v6_2_sre_notes","v6_2_dnspy_ilspy_relevance","v6_3_source_of_truth","v6_3_merge_note","v6_3_live_state_2026_05_11","v6_3_reset_lane_2026_05_11","v6_3_reset_next_step_2026_05_11" +"HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","HyperTwist","Locked Foundation","nD / hypercubing simulation substrate","P0","20","9203","2.0","160.0","193.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","integrate","direct","Validate whether HactarCE/Hyperspeedcube truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -7,8 +7,8 @@ HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,Lo 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.,"Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0001,HT_hyper_engine,hactarce/hyperspeedcube,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,2,1,160.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,Locked Foundation,Live cube-recognition substrate,P0,21,9204,4.0,158.0,191.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",integrate,direct,"Validate whether kkoomen/qbr truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.",Architecture note + salvage map + integration recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0001","HT_hyper_engine","hactarce/hyperspeedcube","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","2","1","160.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"kkoomen/qbr","https://github.com/kkoomen/qbr","HyperTwist","Locked Foundation","Live cube-recognition substrate","P0","21","9204","4.0","158.0","191.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Validate whether kkoomen/qbr truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -16,8 +16,8 @@ kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,Locked Foundation,Live cub 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.,"Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0001,HT_cube_vision,kkoomen/qbr,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,1,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,Locked Parallel Foundation,Vision / reconstruction donor layer,P0,22,9205,8.0,158.0,191.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",integrate,direct,"Validate whether vivaansinghvi07/rubix-cube-solver truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.",Architecture note + salvage map + integration recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0001","HT_cube_vision","kkoomen/qbr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","1","158.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"vivaansinghvi07/rubix-cube-solver","https://github.com/vivaansinghvi07/rubix-cube-solver","HyperTwist","Locked Parallel Foundation","Vision / reconstruction donor layer","P0","22","9205","8.0","158.0","191.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Validate whether vivaansinghvi07/rubix-cube-solver truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -25,8 +25,8 @@ vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube- 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.,"Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0002,HT_cube_vision,vivaansinghvi07/rubix-cube-solver,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,1,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,Locked Parallel Foundation,Training / timing layer,P0,23,9206,9.0,156.0,189.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",integrate,direct,"Validate whether tao-yu/Alg-Trainer truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.",Architecture note + salvage map + integration recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0002","HT_cube_vision","vivaansinghvi07/rubix-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","1","158.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"tao-yu/Alg-Trainer","https://github.com/tao-yu/Alg-Trainer","HyperTwist","Locked Parallel Foundation","Training / timing layer","P0","23","9206","9.0","156.0","189.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","integrate","direct","Validate whether tao-yu/Alg-Trainer truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -34,8 +34,8 @@ tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,Locked Paral 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.,"Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0001,HT_training_stack,tao-yu/alg-trainer,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,1,156.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,Locked Strategic Donor,Boundary-sensitive classic-cubing semantics and rendering donor,P1,24,9207,7.0,152.0,185.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.",integrate,direct,"Validate whether cubing/cubing.js truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.",Architecture note + salvage map + integration recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0001","HT_training_stack","tao-yu/alg-trainer","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","1","156.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"cubing/cubing.js","https://github.com/cubing/cubing.js","HyperTwist","Locked Strategic Donor","Boundary-sensitive classic-cubing semantics and rendering donor","P1","24","9207","7.0","152.0","185.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","integrate","direct","Validate whether cubing/cubing.js truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems.","state representation, move engine, notation parser, solver interfaces, renderer/projection abstraction, serialization/save formats, input mapping, performance/accuracy tradeoffs","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Architecture note + salvage map + integration recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -43,10 +43,10 @@ cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,Locked Strategic 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_semantics_0001,HT_cube_semantics,cubing/cubing.js,,,,,,,Original global P0-P3 source audit retained,MPL-2.0 OR GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,2,1,152.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.",Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.,Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.,Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.,high,dual-license-boundary-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable. -cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,25,9208,0.0,95.0,95.0,medium,"Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.",repurpose,architecture only,"Determine the real reusable value of cubing/alg.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Audit for hidden abstractions that travel across projects.,"Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.",Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.,Use v6 unified board + P0 tier packet + project design language + relevant family references.,"Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.",Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.,"Inspect cubing/alg.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.",HT_cube_semantics_0002,HT_cube_semantics,cubing/alg.js,supplemental_v6_not_runtime_anchored,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2,1,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract. -cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,27,9210,0.0,95.0,95.0,medium,"Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.",repurpose,architecture only,"Determine the real reusable value of cubing/twisty.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Audit for hidden abstractions that travel across projects.,"Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.",Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.,Use v6 unified board + P0 tier packet + project design language + relevant family references.,Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.,Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.,"Inspect cubing/twisty.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.",HT_cube_semantics_0003,HT_cube_semantics,cubing/twisty.js,supplemental_v6_not_runtime_anchored,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2,1,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract. -cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,Locked Strategic Donor,Vision / reconstruction donor layer,P1,55,9211,4.0,148.0,174.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",integrate,direct,"Confirm the donor thesis for cahidenes/rubiks-cube-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.","Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_semantics_0001","HT_cube_semantics","cubing/cubing.js","","","","","","","Original global P0-P3 source audit retained","MPL-2.0 OR GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","2","1","152.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.","Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.","Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.","Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.","high","dual-license-boundary-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable." +"cubing/alg.js","https://github.com/cubing/alg.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","25","9208","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/alg.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.","Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.","Inspect cubing/alg.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0002","HT_cube_semantics","cubing/alg.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"cubing/twisty.js","https://github.com/cubing/twisty.js","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","27","9210","0.0","95.0","95.0","medium","Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","repurpose","architecture only","Determine the real reusable value of cubing/twisty.js for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P0 tier packet + project design language + relevant family references.","Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.","Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.","Inspect cubing/twisty.js directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0003","HT_cube_semantics","cubing/twisty.js","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0-or-later","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","1","95.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract." +"cahidenes/rubiks-cube-solver","https://github.com/cahidenes/rubiks-cube-solver","HyperTwist","Locked Strategic Donor","Vision / reconstruction donor layer","P1","55","9211","4.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the donor thesis for cahidenes/rubiks-cube-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -54,8 +54,8 @@ cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,Hyp 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0003,HT_cube_vision,cahidenes/rubiks-cube-solver,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,Locked Strategic Donor,Vision / reconstruction donor layer,P1,56,9212,5.0,148.0,174.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",integrate,direct,"Confirm the donor thesis for tentone/rubix-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0003","HT_cube_vision","cahidenes/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"tentone/rubix-solver","https://github.com/tentone/rubix-solver","HyperTwist","Locked Strategic Donor","Vision / reconstruction donor layer","P1","56","9212","5.0","148.0","174.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","integrate","direct","Confirm the donor thesis for tentone/rubix-solver in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -63,8 +63,8 @@ tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,Locked S 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.,"Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0004,HT_cube_vision,tentone/rubix-solver,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,Locked Strategic Donor,Training / timing layer,P1,57,9213,14.0,145.0,171.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",integrate,direct,"Confirm the donor thesis for Lykos/cube_trainer in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0004","HT_cube_vision","tentone/rubix-solver","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","148.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"Lykos/cube_trainer","https://github.com/Lykos/cube_trainer","HyperTwist","Locked Strategic Donor","Training / timing layer","P1","57","9213","14.0","145.0","171.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","integrate","direct","Confirm the donor thesis for Lykos/cube_trainer in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -72,8 +72,8 @@ Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,Locked Strat 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Lykos/cube_trainer is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier persistent training-domain donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0002,HT_training_stack,lykos/cube_trainer,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,145.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,Locked Strategic Donor,Restrictive clean-room donor target,P1,58,9214,16.0,145.0,171.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",repurpose,architecture only,"Confirm the donor thesis for kash/cubedesk in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Lykos/cube_trainer is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier persistent training-domain donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0002","HT_training_stack","lykos/cube_trainer","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","145.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"kash/cubedesk","https://github.com/kash/cubedesk","HyperTwist","Locked Strategic Donor","Restrictive clean-room donor target","P1","58","9214","16.0","145.0","171.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","architecture only","Confirm the donor thesis for kash/cubedesk in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -81,8 +81,8 @@ kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,Locked Strategic Donor 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.","Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0002,HT_hyper_engine,kash/cubedesk,,,,,,,Original global P0-P3 source audit retained,GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,145.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.",Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.,Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.,Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.,high,license-contradiction-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,"Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." -poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,Locked Strategic Donor,Training / timing layer,P1,59,9215,15.0,145.0,171.0,high,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.",integrate,direct,"Confirm the donor thesis for poliva/cubedex in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Donor extraction note + merge recipe + reclassification verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.","Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0002","HT_hyper_engine","kash/cubedesk","","","","","","","Original global P0-P3 source audit retained","GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","145.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.","Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.","Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.","Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.","high","license-contradiction-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." +"poliva/cubedex","https://github.com/poliva/cubedex","HyperTwist","Locked Strategic Donor","Training / timing layer","P1","59","9215","15.0","145.0","171.0","high","Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","integrate","direct","Confirm the donor thesis for poliva/cubedex in HyperTwist: what should be harvested, how tightly it couples to the current stack, and whether it should ever be promoted upward.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Donor extraction note + merge recipe + reclassification verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -90,11 +90,11 @@ poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,Locked Strategic Don 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","poliva/cubedex is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier training UX and smartcube donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Top-tier strategic donor for smartcube-aware, offline-first training UX and practical drill ergonomics, but not the owner of the long-term training backend.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0016,HT_training_stack,poliva/cubedex,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,145.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -cs0x7f/cstimer,https://github.com/cs0x7f/cstimer,HyperTwist,Reserve Bench,Gold-standard timer benchmark,P2,60,9216,22.0,121.0,147.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,"Capture the timer, persistence, statistics, and hardware-support behaviors that make cstimer the gold-standard timer benchmark for HyperTwist.","Timer transitions, persistence, statistics, reconstruction, scramble flow, and smart-device surfaces as benchmark material.","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.",Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.,"Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in cs0x7f/cstimer +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","poliva/cubedex is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier training UX and smartcube donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Top-tier strategic donor for smartcube-aware, offline-first training UX and practical drill ergonomics, but not the owner of the long-term training backend.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0016","HT_training_stack","poliva/cubedex","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","145.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"cs0x7f/cstimer","https://github.com/cs0x7f/cstimer","HyperTwist","Reserve Bench","Gold-standard timer benchmark","P2","60","9216","22.0","121.0","147.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the timer, persistence, statistics, and hardware-support behaviors that make cstimer the gold-standard timer benchmark for HyperTwist.","Timer transitions, persistence, statistics, reconstruction, scramble flow, and smart-device surfaces as benchmark material.","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.","Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.","Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if valuable capability is too entangled to salvage, too shallow, duplicated better elsewhere, or far weaker than the current donor thesis.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in cs0x7f/cstimer 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.,"GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.",HT_timer_training_0001,HT_timer_training,cs0x7f/cstimer,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,2,121.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.,high,gpl-timer-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle. -cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,Locked Strategic Donor,"Top-tier 4D interaction, history, and macro donor with attribution obligations",P1,7463,9218,49.0,122.0,137.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",repurpose,moderate modification,"Determine whether cutelyaware/magiccube4d should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.","GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.","HT_timer_training_0001","HT_timer_training","cs0x7f/cstimer","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","2","121.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.","high","gpl-timer-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle." +"cutelyaware/magiccube4d","https://github.com/cutelyaware/magiccube4d/tree/master","HyperTwist","Locked Strategic Donor","Top-tier 4D interaction, history, and macro donor with attribution obligations","P1","7463","9218","49.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether cutelyaware/magiccube4d should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -102,8 +102,8 @@ cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,H 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.",Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.,"Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0003,HT_hyper_engine,cutelyaware/magiccube4d,,,,,,,Original global P0-P3 source audit retained,Custom broad-use license with attribution requested,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,122.0,mixed_or_boundary_sensitive_known,direct_incorporation_ok,"The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.",Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.,"Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.",Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.,medium,custom-license-attribution-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly. -roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,Locked Strategic Donor,Specialized 4D interaction and puzzle-UX donor,P1,7464,9219,49.0,122.0,137.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",repurpose,moderate modification,"Determine whether roice3/Magic120Cell should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.","Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0003","HT_hyper_engine","cutelyaware/magiccube4d","","","","","","","Original global P0-P3 source audit retained","Custom broad-use license with attribution requested","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","mixed_or_boundary_sensitive_known","direct_incorporation_ok","The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.","Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.","Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.","Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.","medium","custom-license-attribution-review","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly." +"roice3/Magic120Cell","https://github.com/roice3/Magic120Cell","HyperTwist","Locked Strategic Donor","Specialized 4D interaction and puzzle-UX donor","P1","7464","9219","49.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether roice3/Magic120Cell should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -111,8 +111,8 @@ roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,Locked Str 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,"MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0004,HT_hyper_engine,roice3/magic120cell,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,Locked Strategic Donor,"Specialized 5D cube interaction, progress, and macro donor",P1,7465,9220,50.0,122.0,137.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",repurpose,moderate modification,"Determine whether roice3/MagicCube5D should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0004","HT_hyper_engine","roice3/magic120cell","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"roice3/MagicCube5D","https://github.com/roice3/MagicCube5D","HyperTwist","Locked Strategic Donor","Specialized 5D cube interaction, progress, and macro donor","P1","7465","9220","50.0","122.0","137.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether roice3/MagicCube5D should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -120,11 +120,11 @@ roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,Locked Strat 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,"MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0005,HT_hyper_engine,roice3/magiccube5d,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -aMonteSl/CodeXR,https://github.com/aMonteSl/CodeXR,HyperTwist,Reserve Bench,Reference-only XR benchmark,P3,7467,9222,51.0,119.0,134.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",future candidate,architecture only,Validate that CodeXR remains reference-only and record the specific immersive interaction ideas worth preserving without direct source reuse.,"Collaboration-room flow, scene launch, virtual screens, and immersive interaction behavior as benchmark material only.","Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.",Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?,Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.,"Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.",Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.,kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in aMonteSl/CodeXR +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.","MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0005","HT_hyper_engine","roice3/magiccube5d","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","122.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.","Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-specialized-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"aMonteSl/CodeXR","https://github.com/aMonteSl/CodeXR","HyperTwist","Reserve Bench","Reference-only XR benchmark","P3","7467","9222","51.0","119.0","134.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","future candidate","architecture only","Validate that CodeXR remains reference-only and record the specific immersive interaction ideas worth preserving without direct source reuse.","Collaboration-room flow, scene launch, virtual screens, and immersive interaction behavior as benchmark material only.","Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?","Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.","Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.","Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in aMonteSl/CodeXR 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.",GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.,"Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.",HT_cube_vision_0005,HT_cube_vision,amontesl/codexr,,,,,,,Original global P0-P3 source audit retained,GPL-3.0-only,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,119.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.,Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-reference-only-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows. -brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,Reserve Bench,Adjacency / future transfer,P2,7468,9223,51.0,119.0,134.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",future candidate,architecture only,"Determine whether brianpeiris/RiftSketch should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.","GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.","HT_cube_vision_0005","HT_cube_vision","amontesl/codexr","","","","","","","Original global P0-P3 source audit retained","GPL-3.0-only","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","119.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.","Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-reference-only-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows." +"brianpeiris/RiftSketch","https://github.com/brianpeiris/RiftSketch","HyperTwist","Reserve Bench","Adjacency / future transfer","P2","7468","9223","51.0","119.0","134.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","future candidate","architecture only","Determine whether brianpeiris/RiftSketch should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -132,11 +132,11 @@ brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,Rese 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","brianpeiris/RiftSketch is placed in Reserve Bench for HyperTwist because it best serves the 'XR interaction and spatial-UI bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Useful MIT WebXR interaction benchmark for spatial editor panels, world-space monitors, and keyboard-first immersive tooling, but explicitly below the HyperTwist core tier.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0006,HT_cube_vision,brianpeiris/riftsketch,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,119.0,permissive_or_noncopyleft_known,pattern_only_preferred,The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.,Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope. -MathewKJ2048/Rubiks-cube-simulator,https://github.com/MathewKJ2048/Rubiks-cube-simulator,HyperTwist,Reserve Bench,Clean-room simulator benchmark,P3,7469,9224,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,Capture the lightweight simulator behaviors worth preserving from MathewKJ2048/Rubiks-cube-simulator through a scrubbed clean-room spec.,"Command grammar, move-history logging, beginner-solver flow, and timed step playback as clean-room benchmark material.","Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.",Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?,Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.,Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in MathewKJ2048/Rubiks-cube-simulator +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","brianpeiris/RiftSketch is placed in Reserve Bench for HyperTwist because it best serves the 'XR interaction and spatial-UI bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Useful MIT WebXR interaction benchmark for spatial editor panels, world-space monitors, and keyboard-first immersive tooling, but explicitly below the HyperTwist core tier.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0006","HT_cube_vision","brianpeiris/riftsketch","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","119.0","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.","Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope." +"MathewKJ2048/Rubiks-cube-simulator","https://github.com/MathewKJ2048/Rubiks-cube-simulator","HyperTwist","Reserve Bench","Clean-room simulator benchmark","P3","7469","9224","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the lightweight simulator behaviors worth preserving from MathewKJ2048/Rubiks-cube-simulator through a scrubbed clean-room spec.","Command grammar, move-history logging, beginner-solver flow, and timed step playback as clean-room benchmark material.","Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.","Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?","Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.","Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in MathewKJ2048/Rubiks-cube-simulator 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors.,GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material.,Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.,HT_training_clean_room_0004,HT_training_clean_room,mathewkj2048/rubiks-cube-simulator,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.",Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." -NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,Donor Bench,XR pedagogy and code-to-scene representation donor,P2,7470,9225,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",repurpose,moderate modification,"Determine whether NuiLab/code-vr should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors.","GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material.","Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.","HT_training_clean_room_0004","HT_training_clean_room","mathewkj2048/rubiks-cube-simulator","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.","Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." +"NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","Donor Bench","XR pedagogy and code-to-scene representation donor","P2","7470","9225","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Determine whether NuiLab/code-vr should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -144,11 +144,11 @@ NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,Donor Bench,XR pedag 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.,"MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0007,HT_cube_vision,nuilab/code-vr,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.",Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.,high,below-core-mit-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -ShellPuppy/RCube,https://github.com/ShellPuppy/RCube,HyperTwist,Reserve Bench,Large-N solver benchmark,P3,7471,9226,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,Document the large-N orientation and stage-framing ideas that justify retaining RCube only as a benchmark row.,"Large-cube orientation logic, stage framing, and solver behavior as benchmark material.","Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.",Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?,"Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.",Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.,Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in ShellPuppy/RCube +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.","MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0007","HT_cube_vision","nuilab/code-vr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"ShellPuppy/RCube","https://github.com/ShellPuppy/RCube","HyperTwist","Reserve Bench","Large-N solver benchmark","P3","7471","9226","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Document the large-N orientation and stage-framing ideas that justify retaining RCube only as a benchmark row.","Large-cube orientation logic, stage framing, and solver behavior as benchmark material.","Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.","Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.","Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in ShellPuppy/RCube 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.,GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.,"Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.",HT_solver_oracles_0001,HT_solver_oracles,shellpuppy/rcube,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.,high,gpl-large-n-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." -abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,Donor Bench,Training / timing layer,P2,7472,9227,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",repurpose,moderate modification,"Determine whether abunickabhi/5style-Trainer should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.","GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.","HT_solver_oracles_0001","HT_solver_oracles","shellpuppy/rcube","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.","high","gpl-large-n-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." +"abunickabhi/5style-Trainer","https://github.com/abunickabhi/5style-Trainer","HyperTwist","Donor Bench","Training / timing layer","P2","7472","9227","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","repurpose","moderate modification","Determine whether abunickabhi/5style-Trainer should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -156,8 +156,8 @@ abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTw 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Focused advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0006,HT_training_stack,abunickabhi/5style-trainer,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,Reserve Bench,Benchmark oracle and clean-room optimal-solver candidate,P2,7473,9228,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,"Determine whether brownan/Rubiks-Cube-Solver should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Focused advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0006","HT_training_stack","abunickabhi/5style-trainer","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"brownan/Rubiks-Cube-Solver","https://github.com/brownan/Rubiks-Cube-Solver","HyperTwist","Reserve Bench","Benchmark oracle and clean-room optimal-solver candidate","P2","7473","9228","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Determine whether brownan/Rubiks-Cube-Solver should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -165,8 +165,8 @@ brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTw 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep as a primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.,GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.,"Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0007,HT_training_stack,brownan/rubiks-cube-solver,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for any later first-party optimal-solver effort.,high,gpl-oracle-clean-room-review,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." -newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubiks-cross-trainer,HyperTwist,Donor Bench,Training / timing layer,P2,7475,9230,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",repurpose,moderate modification,"Determine whether newyork-anthonyng/rubiks-cross-trainer should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.","GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0007","HT_training_stack","brownan/rubiks-cube-solver","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.","Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for any later first-party optimal-solver effort.","high","gpl-oracle-clean-room-review","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." +"newyork-anthonyng/rubiks-cross-trainer","https://github.com/newyork-anthonyng/rubiks-cross-trainer","HyperTwist","Donor Bench","Training / timing layer","P2","7475","9230","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","repurpose","moderate modification","Determine whether newyork-anthonyng/rubiks-cross-trainer should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","algorithm database, weighted scheduling, spaced repetition, scramble generation, timing/statistics model, case metadata, import/export, smartcube adapters","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -174,26 +174,26 @@ newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubi 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","newyork-anthonyng/rubiks-cross-trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",Focused donor for the precomputed cross-difficulty corpus and CFOP micro-drill progression rather than a broader training-platform shell.,"Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0008,HT_training_stack,newyork-anthonyng/rubiks-cross-trainer,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. -vwcwong/CubeSim,https://github.com/vwcwong/CubeSim,HyperTwist,Reserve Bench,Clean-room state/history benchmark,P3,7476,9231,51.0,118.0,133.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,Capture the state/history and replay behaviors worth preserving from vwcwong/CubeSim through a scrubbed clean-room spec.,"State/history separation, parser/scramble modules, tests, and replay-oriented behavior as clean-room benchmark material.","Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.",Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?,Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party state/history and replay behavior through a clean-room process.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in vwcwong/CubeSim +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","newyork-anthonyng/rubiks-cross-trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Focused donor for the precomputed cross-difficulty corpus and CFOP micro-drill progression rather than a broader training-platform shell.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0008","HT_training_stack","newyork-anthonyng/rubiks-cross-trainer","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work." +"vwcwong/CubeSim","https://github.com/vwcwong/CubeSim","HyperTwist","Reserve Bench","Clean-room state/history benchmark","P3","7476","9231","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the state/history and replay behaviors worth preserving from vwcwong/CubeSim through a scrubbed clean-room spec.","State/history separation, parser/scramble modules, tests, and replay-oriented behavior as clean-room benchmark material.","Inspect cube-state/history split, parser and scramble modules, tests, and replay-oriented behavior as clean-room benchmark material only.","Which state/history and replay behaviors are worth preserving through a scrubbed Model A handoff?","Keep only as a clean-room benchmark. Use it to shape first-party state/history and replay behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful state/history ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party state/history and replay behavior through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in vwcwong/CubeSim 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon only as a clean-room state/history benchmark for first-party simulator architecture.,GPL simulator with unusually clean state/history architecture; retain only as clean-room benchmark material.,Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.,HT_training_clean_room_0005,HT_training_clean_room,vwcwong/cubesim,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,118.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.,Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use. -AviKaufman/Rubix-cube-trainer,https://github.com/AviKaufman/Rubix-cube-trainer,HyperTwist,Reserve Bench,Clean-room pedagogy benchmark,P3,7477,9232,52.0,117.0,132.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,Capture the teaching-flow and tutorial behaviors worth preserving from AviKaufman/Rubix-cube-trainer through a scrubbed clean-room spec.,"Beginner-method sequencing, step guidance, and tutorial-state transitions as clean-room benchmark material.","Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.",Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?,Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in AviKaufman/Rubix-cube-trainer +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a clean-room state/history benchmark for first-party simulator architecture.","GPL simulator with unusually clean state/history architecture; retain only as clean-room benchmark material.","Audit vwcwong/CubeSim only as a clean-room state/history benchmark. Extract architectural behaviors into a scrubbed spec; do not recommend direct source incorporation.","HT_training_clean_room_0005","HT_training_clean_room","vwcwong/cubesim","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL simulator code and remains a readable state/history and beginner-solver decomposition benchmark for later clean-room use.","Model A may inspect and summarize state/history behavior; Model B should implement only from a scrubbed clean-room specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if state/history or replay behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room state/history benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a readable state/history and beginner-solver decomposition benchmark for later clean-room use." +"AviKaufman/Rubix-cube-trainer","https://github.com/AviKaufman/Rubix-cube-trainer","HyperTwist","Reserve Bench","Clean-room pedagogy benchmark","P3","7477","9232","52.0","117.0","132.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the teaching-flow and tutorial behaviors worth preserving from AviKaufman/Rubix-cube-trainer through a scrubbed clean-room spec.","Beginner-method sequencing, step guidance, and tutorial-state transitions as clean-room benchmark material.","Inspect beginner-method sequencing, step guidance, tutorial-state transitions, and 3D teaching behavior as clean-room benchmark material only.","Which teaching-flow and tutorial behaviors are worth preserving through a scrubbed Model A handoff?","Keep only as a clean-room benchmark. Use it to shape first-party pedagogy and tutorial behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful teaching-flow ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party pedagogy and tutorial behavior through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in AviKaufman/Rubix-cube-trainer 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon only as a clean-room pedagogy benchmark for first-party teaching-flow work.,All-rights-reserved repo with narrow teaching-flow value; retain only as clean-room benchmark material.,Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation.,HT_training_clean_room_0003,HT_training_clean_room,avikaufman/rubix-cube-trainer,,,,,,,Original global P0-P3 source audit retained,All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,117.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.,Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source or assets directly without separate rights.,Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary.,high,all-rights-reserved-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design. -alinen/cube,https://github.com/alinen/cube,HyperTwist,Reserve Bench,Clean-room planner benchmark,P3,7478,9233,52.0,117.0,132.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,Capture the planner and guided-lesson behaviors worth preserving from alinen/cube through a scrubbed clean-room spec.,"Planner flow, guided lessons, cube-state handling, and bounded-search behavior as clean-room benchmark material.","Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.",Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?,Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only.,Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in alinen/cube +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a clean-room pedagogy benchmark for first-party teaching-flow work.","All-rights-reserved repo with narrow teaching-flow value; retain only as clean-room benchmark material.","Audit AviKaufman/Rubix-cube-trainer only as a clean-room pedagogy benchmark. Extract tutorial behaviors into a scrubbed spec; do not recommend direct source incorporation.","HT_training_clean_room_0003","HT_training_clean_room","avikaufman/rubix-cube-trainer","","","","","","","Original global P0-P3 source audit retained","All Rights Reserved","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","117.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is all-rights-reserved and remains the strongest guided-pedagogy benchmark in Packet 0R-E. Preserve tutorial behavior only through scrubbed first-party specifications.","Model A may inspect and summarize lesson-state behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source or assets directly without separate rights.","Yes — this is the preferred path if pedagogy and tutorial behavior later prove strategically necessary.","high","all-rights-reserved-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room pedagogy benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as the primary all-rights-reserved guided-pedagogy benchmark for clean-room lesson-state and stepwise solve flow design." +"alinen/cube","https://github.com/alinen/cube","HyperTwist","Reserve Bench","Clean-room planner benchmark","P3","7478","9233","52.0","117.0","132.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the planner and guided-lesson behaviors worth preserving from alinen/cube through a scrubbed clean-room spec.","Planner flow, guided lessons, cube-state handling, and bounded-search behavior as clean-room benchmark material.","Inspect planner logic, lesson flow, cube-state handling, and bounded-search behavior as clean-room benchmark material only.","Which planner and lesson behaviors are worth preserving through a scrubbed Model A handoff?","Keep only as a clean-room benchmark. Use it to shape first-party planner and guided-lesson behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful planner and lesson ideas into scrubbed Model A specifications only.","Repurpose here means: derive first-party planner and guided-lesson behavior through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in alinen/cube 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon only as a clean-room planner benchmark for first-party guided-lesson and planner work.,No explicit license visible and limited scope; retain only for clean-room planner behavior extraction.,Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation.,HT_training_clean_room_0001,HT_training_clean_room,alinen/cube,,,,,,,Original global P0-P3 source audit retained,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,117.0,license_unknown_pending,reverse_engineer_preferred,No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.,Model A may inspect and summarize planner behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source directly without a confirmed license grant.,Yes — this is the preferred path if planner or lesson behavior later proves strategically necessary.,medium,no-license-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room planner benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly." -ambisinister/blindsolve,https://github.com/ambisinister/blindsolve,HyperTwist,Reserve Bench,Clean-room BLD memo benchmark,P3,7479,9234,52.0,117.0,132.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,Capture the memo-practice and feedback behaviors worth preserving from blindsolve through a scrubbed clean-room spec.,"Memo-practice flow, feedback behavior, and narrow training-state transitions as clean-room benchmark material.","Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.",Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?,Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only.,Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in ambisinister/blindsolve +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a clean-room planner benchmark for first-party guided-lesson and planner work.","No explicit license visible and limited scope; retain only for clean-room planner behavior extraction.","Audit alinen/cube only as a clean-room planner benchmark. Extract planner behaviors and guided-lesson flow into a scrubbed spec; do not recommend direct source incorporation.","HT_training_clean_room_0001","HT_training_clean_room","alinen/cube","","","","","","","Original global P0-P3 source audit retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","117.0","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible. Retain this repo only as clean-room planner benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.","Model A may inspect and summarize planner behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source directly without a confirmed license grant.","Yes — this is the preferred path if planner or lesson behavior later proves strategically necessary.","medium","no-license-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room planner benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a no-license clean-room planner benchmark for task segmentation, focus cues, and stepwise teaching flow; do not incorporate source directly." +"ambisinister/blindsolve","https://github.com/ambisinister/blindsolve","HyperTwist","Reserve Bench","Clean-room BLD memo benchmark","P3","7479","9234","52.0","117.0","132.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the memo-practice and feedback behaviors worth preserving from blindsolve through a scrubbed clean-room spec.","Memo-practice flow, feedback behavior, and narrow training-state transitions as clean-room benchmark material.","Inspect memo-practice flow, prompt cadence, scoring/feedback behavior, and narrow training-state transitions as clean-room benchmark material only.","Which memo-practice behaviors are worth preserving through a scrubbed Model A handoff?","Keep only as a clean-room benchmark. Use it to shape a first-party memo-practice micro-mode; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful memo-practice ideas into a scrubbed Model A spec only.","Repurpose here means: derive first-party BLD memo-practice behavior through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in ambisinister/blindsolve 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon only as a clean-room BLD memo benchmark for later first-party micro-mode work.,No explicit license visible and extremely narrow scope; retain only as clean-room benchmark material.,Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation.,HT_training_clean_room_0002,HT_training_clean_room,ambisinister/blindsolve,,,,,,,Original global P0-P3 source audit retained,no explicit license visible,pending_repo_license_audit,not_resolved_from_uploaded_materials,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,117.0,license_unknown_pending,reverse_engineer_preferred,No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.,Model A may inspect and summarize memo-practice behavior; Model B should implement only from a scrubbed clean-room specification.,Do not incorporate source directly without a confirmed license grant.,Yes — this is the preferred path if a memo-practice micro-mode later proves strategically necessary.,medium,no-license-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room BLD memo benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only." -efrantar/rob-twophase,https://github.com/efrantar/rob-twophase,HyperTwist,Reserve Bench,Solver oracle and robot-metric benchmark,P2,7480,9235,52.0,117.0,132.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",future candidate,architecture only,"Capture the correctness, metric, and oracle behaviors that justify keeping rob-twophase only as a benchmark row.","Robot metrics, pruning tables, CLI oracle behavior, and multiple-solution search as benchmark material.","Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.","Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?","Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code.",Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests.,Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Benchmark note + salvage list + clear do-not-incorporate boundary.,"1) What specific benchmark value remains in efrantar/rob-twophase +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a clean-room BLD memo benchmark for later first-party micro-mode work.","No explicit license visible and extremely narrow scope; retain only as clean-room benchmark material.","Audit ambisinister/blindsolve only as a clean-room BLD memo benchmark. Extract memo-practice behavior into a scrubbed spec; do not recommend direct source incorporation.","HT_training_clean_room_0002","HT_training_clean_room","ambisinister/blindsolve","","","","","","","Original global P0-P3 source audit retained","no explicit license visible","pending_repo_license_audit","not_resolved_from_uploaded_materials","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","117.0","license_unknown_pending","reverse_engineer_preferred","No explicit permissive license is visible. Retain this repo only as clean-room BLD memo benchmark material and implement any strategically necessary behavior from scrubbed first-party specifications.","Model A may inspect and summarize memo-practice behavior; Model B should implement only from a scrubbed clean-room specification.","Do not incorporate source directly without a confirmed license grant.","Yes — this is the preferred path if a memo-practice micro-mode later proves strategically necessary.","medium","no-license-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room BLD memo benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a no-license BLD memo benchmark for hide/reveal, letter-pair rehearsal, and feedback cadence; keep it narrow and clean-room only." +"efrantar/rob-twophase","https://github.com/efrantar/rob-twophase","HyperTwist","Reserve Bench","Solver oracle and robot-metric benchmark","P2","7480","9235","52.0","117.0","132.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the correctness, metric, and oracle behaviors that justify keeping rob-twophase only as a benchmark row.","Robot metrics, pruning tables, CLI oracle behavior, and multiple-solution search as benchmark material.","Inspect metric handling, pruning-table structure, CLI oracle behavior, and multiple-solution search as benchmark material only.","Which oracle surfaces, robot metrics, and correctness/performance baselines should be preserved for first-party solver validation?","Keep as a restrictive solver oracle benchmark. Use it for correctness, metric comparison, and performance expectations; do not treat it as donor code.","Do not merge this repo into the HyperTwist core. Translate only oracle behavior and robot-metric expectations into first-party acceptance tests.","Repurpose here means: use as a correctness/performance oracle and robot-metric benchmark.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in efrantar/rob-twophase 2) What must stay benchmark-only or clean-room-only -3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon as a restrictive solver oracle benchmark with robot-metric value.,"GPL solver/oracle repo whose retained value is correctness, performance, and metric benchmarking rather than donor use.","Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.",HT_solver_oracles_0002,HT_solver_oracles,efrantar/rob-twophase,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,117.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code.",Reference only: use as a solver oracle and robot-metric benchmark without direct source incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow oracle behavior later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-solver-oracle-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed solver oracle benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code." -onionhoney/roux-trainers,https://github.com/onionhoney/roux-trainers,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,7481,9236,52.0,117.0,132.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",repurpose,architecture only,"Capture the stage-specific training, analyzer, recognition, and drill-loop behaviors that justify keeping roux-trainers as a clean-room donor target.","Stage-specific training flows, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.",Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?,"Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code.",Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary.,Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,HyperTwist only,"Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Model A salvage map + clean-room boundary note + first-party subsystem extraction plan.,"1) Which stage-specific subsystems are worth preserving +3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon as a restrictive solver oracle benchmark with robot-metric value.","GPL solver/oracle repo whose retained value is correctness, performance, and metric benchmarking rather than donor use.","Audit efrantar/rob-twophase only as a restrictive solver oracle and robot-metric benchmark. Extract acceptance-test expectations and oracle behavior, not donor code.","HT_solver_oracles_0002","HT_solver_oracles","efrantar/rob-twophase","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","117.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL solver/oracle code and remains a secondary metric, pruning, and performance benchmark rather than donor code.","Reference only: use as a solver oracle and robot-metric benchmark without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a narrow oracle behavior later needs first-party recreation; otherwise keep this as a benchmark.","high","gpl-solver-oracle-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed solver oracle benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a secondary solver oracle for metric, pruning, and performance comparison; do not treat as donor code." +"onionhoney/roux-trainers","https://github.com/onionhoney/roux-trainers","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","7481","9236","52.0","117.0","132.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","repurpose","architecture only","Capture the stage-specific training, analyzer, recognition, and drill-loop behaviors that justify keeping roux-trainers as a clean-room donor target.","Stage-specific training flows, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Inspect blockbuilding micro-trainers, stage-specific state machines, solver-backed analyzer logic, recognition masking, favorites/batch-drill persistence, and 2D/3D visualization boundaries.","Which Roux-specific training and analyzer behaviors are strategically worth reproducing in first-party code through a clean-room handoff?","Keep in restrictive custody and route value through clean-room extraction only. Use it as a method-specific training and analyzer donor, not as direct donor code.","Do not merge this repo into the HyperTwist core as source. Convert the valuable training-state-machine and analyzer behaviors into first-party subsystems behind a clean-room boundary.","Repurpose here means: translate stage-specific training and analyzer behaviors into first-party implementations through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","HyperTwist only","Restrictive clean-room donor value is real, but it should flow through Model A to a first-party implementation rather than through direct source sharing.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Model A salvage map + clean-room boundary note + first-party subsystem extraction plan.","1) Which stage-specific subsystems are worth preserving 2) What must stay behind Model A / Model B separation -3) What first-party implementations should replace the GPL source","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep in canon as a focused restrictive clean-room donor for method-specific training and analyzer behavior.,GPLv3 method-specific trainer with real subsystem value that should be preserved through clean-room extraction rather than donor use.,"Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only.",HT_training_clean_room_0006,HT_training_clean_room,onionhoney/roux-trainers,,,,,,,Original global P0-P3 source audit retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,117.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPLv3 and should not be used as direct donor code in the HyperTwist core. Its value is in selective behavior and subsystem extraction through a clean-room Model A / Model B process.,Model A inspects the restrictive source; Model B implements only from a scrubbed first-party specification and must not access the repo directly.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for selectively reproducing stage-specific training and analyzer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed focused restrictive clean-room donor status.,implemented_live_clean_room_verified,landed_clean_room_preserve,Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs. -yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,Reserve Bench,Adjacency / future transfer,P2,7482,9237,53.0,117.0,132.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",future candidate,architecture only,"Determine whether yakupbilen/drl-rubiks-cube should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +3) What first-party implementations should replace the GPL source","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon as a focused restrictive clean-room donor for method-specific training and analyzer behavior.","GPLv3 method-specific trainer with real subsystem value that should be preserved through clean-room extraction rather than donor use.","Audit onionhoney/roux-trainers as a focused restrictive clean-room donor for HyperTwist. Preserve method-specific training-state-machine, analyzer, recognition-masking, and drill-loop behavior in a scrubbed Model A handoff only.","HT_training_clean_room_0006","HT_training_clean_room","onionhoney/roux-trainers","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","117.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPLv3 and should not be used as direct donor code in the HyperTwist core. Its value is in selective behavior and subsystem extraction through a clean-room Model A / Model B process.","Model A inspects the restrictive source; Model B implements only from a scrubbed first-party specification and must not access the repo directly.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — preferred path for selectively reproducing stage-specific training and analyzer behavior in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed focused restrictive clean-room donor status.","implemented_live_clean_room_verified","landed_clean_room_preserve","Phase 1R closed. Preserve as the landed restrictive clean-room precedent; keep the Model A/Model B chain explicit and work only from first-party outputs or scrubbed specs." +"yakupbilen/drl-rubiks-cube","https://github.com/yakupbilen/drl-rubiks-cube","HyperTwist","Reserve Bench","Adjacency / future transfer","P2","7482","9237","53.0","117.0","132.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","future candidate","architecture only","Determine whether yakupbilen/drl-rubiks-cube should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -201,8 +201,8 @@ yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTw 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_cube_vision_0008,HT_cube_vision,yakupbilen/drl-rubiks-cube,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,117.0,permissive_or_noncopyleft_known,pattern_only_preferred,"The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.",Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." -Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,HyperTwist,Locked Strategic Donor,Knowledge and curriculum donor,P1,7483,9238,1.0,92.0,101.0,medium,"Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",repurpose,moderate modification,"Determine whether Hypercubers/hypercubing.xyz should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0008","HT_cube_vision","yakupbilen/drl-rubiks-cube","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","117.0","permissive_or_noncopyleft_known","pattern_only_preferred","The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.","Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." +"Hypercubers/hypercubing.xyz","https://github.com/Hypercubers/hypercubing.xyz","HyperTwist","Locked Strategic Donor","Knowledge and curriculum donor","P1","7483","9238","1.0","92.0","101.0","medium","Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.","repurpose","moderate modification","Determine whether Hypercubers/hypercubing.xyz should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.","Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.","HactarCE/Hyperspeedcube","foundation + donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","cubing/cubing.js","3D engine + notation/state donor","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","tao-yu/Alg-Trainer","training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -210,8 +210,8 @@ Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,Hyper 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.,"MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0006,HT_hyper_engine,hypercubers/hypercubing.xyz,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,92.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.,"Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.",Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.,high,permissive-knowledge-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." -Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,Donor Bench,Adjacency / future transfer,P2,7485,9240,2.0,88.0,97.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",repurpose,moderate modification,"Determine whether Aarav2709/KubeTimr should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.","MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0006","HT_hyper_engine","hypercubers/hypercubing.xyz","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","92.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.","Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.","high","permissive-knowledge-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." +"Aarav2709/KubeTimr","https://github.com/Aarav2709/KubeTimr","HyperTwist","Donor Bench","Adjacency / future transfer","P2","7485","9240","2.0","88.0","97.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","repurpose","moderate modification","Determine whether Aarav2709/KubeTimr should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -219,8 +219,8 @@ Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,Donor Bench, 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_training_stack_0015,HT_training_stack,aarav2709/kubetimr,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,routine-review-only,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." -roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,Locked Strategic Donor,Top-tier non-Euclidean geometry and topology donor,P1,7487,9242,2.0,88.0,97.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",repurpose,moderate modification,"Determine whether roice3/MagicTile should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.","Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_training_stack_0015","HT_training_stack","aarav2709/kubetimr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","routine-review-only","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." +"roice3/MagicTile","https://github.com/roice3/MagicTile","HyperTwist","Locked Strategic Donor","Top-tier non-Euclidean geometry and topology donor","P1","7487","9242","2.0","88.0","97.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.","repurpose","moderate modification","Determine whether roice3/MagicTile should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.","Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -228,8 +228,8 @@ roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,Locked Strategic 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.",Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.,"MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HT_hyper_engine_0007,HT_hyper_engine,roice3/magictile,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,Donor Bench,Adjacency / future transfer,P2,7492,9247,20.0,72.0,81.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",repurpose,moderate modification,"Determine whether PostHog/posthog should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","telemetry and event schemas, replay product boundaries, feature-flag governance, diagnostics, service slices, hidden modules","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.","MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_hyper_engine_0007","HT_hyper_engine","roice3/magictile","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","88.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.","Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.","high","permissive-top-tier-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"PostHog/posthog","https://github.com/PostHog/posthog","HyperTwist","Donor Bench","Adjacency / future transfer","P2","7492","9247","20.0","72.0","81.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Determine whether PostHog/posthog should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","telemetry and event schemas, replay product boundaries, feature-flag governance, diagnostics, service slices, hidden modules","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -237,9 +237,9 @@ PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,Donor Bench,Adjace 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.","Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.",HT_control_plane_0001,HT_control_plane,posthog/posthog,,,,,,,Original global P0-P3 source audit retained,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2,3,72.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.",Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.,"Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,Donor Bench,Focused restrictive clean-room donor target,P2,7496,9251,2.0,63.0,63.0,low-to-medium,"Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.",repurpose,architecture only,"Determine the real reusable value of HactarCE/2x2x2x2-Scrambler for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Audit for hidden abstractions that travel across projects.,"Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.",Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.,Use v6 unified board + P2 tier packet + project design language + relevant family references.,"Keep as a narrow but real clean-room donor for Melinda 2x2x2x2 state encoding, handedness/parity repair, random-state generation, move-family representation, and flat debug/teaching views.","GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.","Inspect HactarCE/2x2x2x2-Scrambler directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.",HT_cube_semantics_0004,HT_cube_semantics,hactarce/2x2x2x2-scrambler,supplemental_v6_not_runtime_anchored,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2,3,63.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier. -SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8351,10345,49.0,71.0,80.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.",repurpose,moderate modification,"Determine whether SYSTRAN/faster-whisper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","STT API surface, VAD chunking, batch inference, timestamps, service boundaries, model/runtime constraints, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.",Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.,"Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.","Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.","HT_control_plane_0001","HT_control_plane","posthog/posthog","","","","","","","Original global P0-P3 source audit retained","MIT outside ee/; enterprise-restricted in ee/","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","72.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.","Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed." +"HactarCE/2x2x2x2-Scrambler","https://github.com/HactarCE/2x2x2x2-Scrambler","HyperTwist","Donor Bench","Focused restrictive clean-room donor target","P2","7496","9251","2.0","63.0","63.0","low-to-medium","Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","repurpose","architecture only","Determine the real reusable value of HactarCE/2x2x2x2-Scrambler for HyperTwist and decide whether it should be promoted, retained, or demoted in the v6 corpus.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","HactarCE/Hyperspeedcube","foundation repo + feature donor","Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","cubing/cubing.js","engine repo + interface donor","Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","kkoomen/qbr","feature extraction only","Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.","multi-project","Audit for hidden abstractions that travel across projects.","Source reveals a strong reusable subsystem, extensibility layer, protocol boundary, renderer core, data model, or automation surface that clearly strengthens one of the project stacks.","Source reveals the repo is mostly documentation, thin wrappers, packaging glue, stale scaffolding, or a weak duplicate with no meaningful transplantable subsystem.","Source-audit note, role recommendation, hidden-value extraction, exact integration path, and reclassification decision.","Implemented capability; hidden reusable modules; strongest integration path; strongest merger path; upgrade triggers; downgrade triggers; final recommended bucket.","Use v6 unified board + P2 tier packet + project design language + relevant family references.","Keep as a narrow but real clean-room donor for Melinda 2x2x2x2 state encoding, handedness/parity repair, random-state generation, move-family representation, and flat debug/teaching views.","GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.","Inspect HactarCE/2x2x2x2-Scrambler directly in source. Do not dismiss for license. Preserve nuanced distinctions between donor, reserve, comparator, and exclusion.","HT_cube_semantics_0004","HT_cube_semantics","hactarce/2x2x2x2-scrambler","supplemental_v6_not_runtime_anchored","","","","","no","v6_unified_source_of_truth_pack","GPL-3.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","","2","3","63.0","mixed_or_boundary_sensitive_known","reverse_engineer_preferred","The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.","Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.","high","gpl-clean-room-donor","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.","selected_not_live_clean_room_candidate","phase0r_clean_room_eval_then_model_a_model_b","Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier." +"SYSTRAN/faster-whisper","https://github.com/SYSTRAN/faster-whisper","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8351","10345","49.0","71.0","80.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.","repurpose","moderate modification","Determine whether SYSTRAN/faster-whisper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","STT API surface, VAD chunking, batch inference, timestamps, service boundaries, model/runtime constraints, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.","Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","project-local first","Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -247,8 +247,8 @@ SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,D 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","SYSTRAN/faster-whisper is placed in Donor Bench for multi-project because it provides the clearest Python STT service-layer path in the voice stack. Recommended action remains repurpose, but the real retained value is batch transcription, VAD-aware chunking, timestamps, and Python-side service integration rather than any code-intelligence or graph role.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current Python STT donor and service-layer candidate in the voice stack.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",MU_misc_0001,MU_misc,systran/faster-whisper,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.",Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.,"Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.",Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.,high,model-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8352,10346,49.0,71.0,80.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",repurpose,moderate modification,"Determine whether coqui-ai/TTS should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","API surface, synthesis orchestration, multilingual and speaker handling, voice conversion, model registry, deployment boundary, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","SYSTRAN/faster-whisper is placed in Donor Bench for multi-project because it provides the clearest Python STT service-layer path in the voice stack. Recommended action remains repurpose, but the real retained value is batch transcription, VAD-aware chunking, timestamps, and Python-side service integration rather than any code-intelligence or graph role.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current Python STT donor and service-layer candidate in the voice stack.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","MU_misc_0001","MU_misc","systran/faster-whisper","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.","Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.","Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.","high","model-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"coqui-ai/TTS","https://github.com/coqui-ai/TTS","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8352","10346","49.0","71.0","80.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","repurpose","moderate modification","Determine whether coqui-ai/TTS should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","API surface, synthesis orchestration, multilingual and speaker handling, voice conversion, model registry, deployment boundary, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -256,8 +256,8 @@ coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,Donor Bench,Cross-pro 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","coqui-ai/TTS is placed in Donor Bench for multi-project because it provides the richest current voice-output and coaching architecture in the stack. Recommended action remains repurpose, but the real retained value is synthesis orchestration, multilingual and speaker handling, XTTS/voice-conversion paths, and model-registry discipline rather than broad assistant scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current voice and coaching donor, but boundary-sensitive because code and model payload licensing must be separated.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",MU_misc_0002,MU_misc,coqui-ai/tts,,,,,,,Original global P0-P3 source audit retained,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.",Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.,"Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.",Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.,medium,model-license-selection-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8353,10347,49.0,71.0,80.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",repurpose,moderate modification,"Determine whether ggml-org/whisper.cpp should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","native STT runtime seam, VAD, grammar-constrained decoding, server boundary, portability, hidden modules","Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.",Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.,"Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","coqui-ai/TTS is placed in Donor Bench for multi-project because it provides the richest current voice-output and coaching architecture in the stack. Recommended action remains repurpose, but the real retained value is synthesis orchestration, multilingual and speaker handling, XTTS/voice-conversion paths, and model-registry discipline rather than broad assistant scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current voice and coaching donor, but boundary-sensitive because code and model payload licensing must be separated.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","MU_misc_0002","MU_misc","coqui-ai/tts","","","","","","","Original global P0-P3 source audit retained","MPL-2.0 code; mixed model payload licenses","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.","Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.","Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.","Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.","medium","model-license-selection-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"ggml-org/whisper.cpp","https://github.com/ggml-org/whisper.cpp","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8353","10347","49.0","71.0","80.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","repurpose","moderate modification","Determine whether ggml-org/whisper.cpp should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","native STT runtime seam, VAD, grammar-constrained decoding, server boundary, portability, hidden modules","Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.","Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -265,8 +265,8 @@ ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,Donor 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","ggml-org/whisper.cpp is placed in Donor Bench for multi-project because it is the clearest native/offline STT anchor in the voice stack. Recommended action remains repurpose, but the real retained value is a bounded speech-input runtime, VAD, grammar-constrained decoding, and portable deployment rather than a full product shell.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current native/offline STT sidecar candidate in the voice stack.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",MU_misc_0003,MU_misc,ggml-org/whisper.cpp,,,,,,,Original global P0-P3 source audit retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.,"Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.",Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.,high,model-artifact-review-recommended,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -rhasspy/piper,https://github.com/rhasspy/piper,multi-project,Donor Bench,Cross-project / future-adjacent,P2,8354,10348,49.0,71.0,80.0,medium,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",repurpose,moderate modification,"Determine whether rhasspy/piper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","local TTS runtime seam, ONNX and eSpeak integration, streaming output, HTTP service boundary, voice catalog, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.",Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.,"Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.",Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.,project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.",Capability inventory + salvage targets + promotion/demotion verdict,"1) Confirmed visible capabilities +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","ggml-org/whisper.cpp is placed in Donor Bench for multi-project because it is the clearest native/offline STT anchor in the voice stack. Recommended action remains repurpose, but the real retained value is a bounded speech-input runtime, VAD, grammar-constrained decoding, and portable deployment rather than a full product shell.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current native/offline STT sidecar candidate in the voice stack.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.","MU_misc_0003","MU_misc","ggml-org/whisper.cpp","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.","Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.","Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.","high","model-artifact-review-recommended","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"rhasspy/piper","https://github.com/rhasspy/piper","multi-project","Donor Bench","Cross-project / future-adjacent","P2","8354","10348","49.0","71.0","80.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.","repurpose","moderate modification","Determine whether rhasspy/piper should stay donor/merge-tier for multi-project, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","local TTS runtime seam, ONNX and eSpeak integration, streaming output, HTTP service boundary, voice catalog, hidden modules","Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.","Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.","project-local anchor","base + donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","shared portfolio utility","augmenter","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cross-project transfer candidate","future merger","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","VectorShell | HyperTwist | ScriptoriumAI","This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project @@ -274,39 +274,39 @@ rhasspy/piper,https://github.com/rhasspy/piper,multi-project,Donor Bench,Cross-p 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit -9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",MU_misc_0004,MU_misc,rhasspy/piper,,,,,,,Original global P0-P3 source audit retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.,"Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.",Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.,high,voice-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,Browser embodied coach surface,P2,,,,,,medium,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",repurpose,moderate modification,Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.,"avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.",Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",HT_browser_surface_0001,HT_browser_surface,met4citizen/talkinghead,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." -apache/echarts,https://github.com/apache/echarts,HyperTwist,Donor Bench,Browser analytics and reporting surface,P2,,,,,,medium,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",repurpose,moderate modification,Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces.,"option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",HT_browser_surface_0002,HT_browser_surface,apache/echarts,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." -ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,Merge Bench,Browser 3D analytics and explainer surface,P3,,,,,,medium,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",integrate,moderate modification,Determine whether echarts-gl should remain the bounded 3D analytics extension beneath echarts and what should stay outside HyperTwist core.,"3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",HT_browser_surface_0003,HT_browser_surface,ecomfe/echarts-gl,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." -KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,Donor Bench,Browser asset validation and viewer surface,P3,,,,,,medium,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",repurpose,moderate modification,Determine whether glTF-Sample-Viewer should remain the primary standards-validation viewer donor for browser asset tooling.,"validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",HT_browser_surface_0004,HT_browser_surface,khronosgroup/gltf-sample-viewer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer,https://github.com/google/model-viewer,HyperTwist,Donor Bench,Browser 3D presentation and inspection surface,P2,,,,,,medium,"Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.",repurpose,moderate modification,Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces.,"custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.",,"Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.",HT_browser_surface_0005,HT_browser_surface,google/model-viewer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,"Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.",Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." -mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,Donor Bench,Browser 3D substrate,P2,,,,,,medium,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,repurpose,moderate modification,Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces.,"renderer, scene, camera, math core, loaders, WebXR manager, addons, editor","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",HT_browser_surface_0006,HT_browser_surface,mrdoob/three.js,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,Merge Bench,Browser post-processing substrate,P3,,,,,,medium,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",integrate,moderate modification,Determine whether postprocessing should remain the bounded browser effect-composer substrate beneath the companion stack.,"EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",HT_browser_surface_0007,HT_browser_surface,pmndrs/postprocessing,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,Donor Bench,Browser React 3D substrate,P2,,,,,,medium,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",repurpose,moderate modification,Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes.,"Canvas, createRoot, reconciler runtime, event system, hooks, native path","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",HT_browser_surface_0008,HT_browser_surface,pmndrs/react-three-fiber,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,Merge Bench,Browser 3D helper and abstraction layer,P3,,,,,,medium,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,integrate,moderate modification,Determine which drei helpers should remain active merge candidates for browser companion surfaces and which should be ignored as generic convenience.,"Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",HT_browser_surface_0009,HT_browser_surface,pmndrs/drei,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,Donor Bench,Browser XR and immersive UI substrate,P2,,,,,,medium,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",repurpose,moderate modification,Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces.,"XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",HT_browser_surface_0010,HT_browser_surface,pmndrs/xr,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,Donor Bench,Browser spatial UI surface,P2,,,,,,medium,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",repurpose,moderate modification,Determine whether pmndrs/uikit should remain the default browser spatial UI donor for HyperTwist companion surfaces.,"flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",HT_browser_surface_0011,HT_browser_surface,pmndrs/uikit,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,Merge Bench,Browser motion and animation layer,P3,,,,,,medium,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",integrate,moderate modification,Determine which react-spring motion surfaces should remain active merge candidates for browser companion views.,"Controller and SpringValue runtime, scheduler, layered explainer behavior, browser motion ergonomics","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",HT_browser_surface_0012,HT_browser_surface,pmndrs/react-spring,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,Donor Bench,"Support-plane capture, history, and replay sidecar",P2,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,"Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_support_sidecars_0001,HT_support_sidecars,screenpipe/screenpipe,,,,,,,,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.,Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.,Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.,"Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." -remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,Donor Bench,Commercially licensed media-export and explainer sidecar,P2,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.,"player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_support_sidecars_0002,HT_support_sidecars,remotion-dev/remotion,,,,,,,,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.,Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.,Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.,Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.,high,commercial-license-sidecar-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use. -ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,Merge Bench,Browser 2D render substrate,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether ecomfe/zrender should remain active in the Browser 2D render substrate lane and which seams should stay bounded.,"scene graph, canvas and SVG painters, event handling, animation primitives","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0001,HT_browser_support,ecomfe/zrender,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live." -pissang/claygl,https://github.com/pissang/claygl,HyperTwist,Merge Bench,Browser WebGL substrate,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pissang/claygl should remain active in the Browser WebGL substrate lane and which seams should stay bounded.,"renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0002,HT_browser_support,pissang/claygl,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,Merge Bench,Browser viewer and editor sidecar,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pissang/clay-viewer should remain active in the Browser viewer and editor sidecar lane and which seams should stay bounded.,"viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0003,HT_browser_support,pissang/clay-viewer,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,Merge Bench,Browser asset renderer substrate,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether KhronosGroup/glTF-Sample-Renderer should remain active in the Browser asset renderer substrate lane and which seams should stay bounded.,"GltfView, GltfState, resource loader, user camera, renderer core","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0004,HT_browser_support,khronosgroup/gltf-sample-renderer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." -google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,Merge Bench,Browser asset editor and inspection surface,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/space-opera should remain active in the Browser asset editor and inspection surface lane and which seams should stay bounded.,"editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0005,HT_browser_support,google/model-viewer/packages/space-opera,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,Merge Bench,Browser fidelity QA harness,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/render-fidelity-tools should remain active in the Browser fidelity QA harness lane and which seams should stay bounded.,"golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0006,HT_browser_support,google/model-viewer/packages/render-fidelity-tools,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,Merge Bench,Browser emphasis and post-processing extension,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/model-viewer-effects should remain active in the Browser emphasis and post-processing extension lane and which seams should stay bounded.,"effect composer integration, outline, SSAO, emphasis behavior, custom-element surface","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0007,HT_browser_support,google/model-viewer/packages/model-viewer-effects,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." -google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,Merge Bench,Browser docs and demo surface,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether google/model-viewer/packages/modelviewer.dev should remain active in the Browser docs and demo surface lane and which seams should stay bounded.,"live docs generation, snippet-to-demo coupling, sidebar and HTML generation","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0008,HT_browser_support,google/model-viewer/packages/modelviewer.dev,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." -google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,Donor Bench,Boundary-sensitive sample-asset and test-fixture pack,P3,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",repurpose,architecture only,Determine whether google/model-viewer/packages/shared-assets should remain active in the Browser sample-asset and fixture pack lane and which seams should stay bounded.,"asset provenance, attribution terms, environment fixtures, sample models, fetch script behavior","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.","Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0009,HT_browser_support,google/model-viewer/packages/shared-assets,,,,,,,,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.,Preserve container notices and review each selected asset attribution or usage condition separately before shipping.,"Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.",high,mixed-asset-whitelist-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use. -pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,Merge Bench,Browser React effect-wrapper layer,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/react-postprocessing should remain active in the Browser React effect-wrapper layer lane and which seams should stay bounded.,"React EffectComposer orchestration, selection model, wrapper ergonomics","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0010,HT_browser_support,pmndrs/react-postprocessing,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,Merge Bench,Browser 3D utility substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/three-stdlib should remain active in the Browser 3D utility substrate lane and which seams should stay bounded.,"controls, loaders, WebXR helpers, post-processing helpers, utility exports","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0011,HT_browser_support,pmndrs/three-stdlib,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,Merge Bench,Browser math-helper substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/maath should remain active in the Browser math-helper substrate lane and which seams should stay bounded.,"easing and damp functions, random helpers, geometry utilities","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0012,HT_browser_support,pmndrs/maath,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,Donor Bench,Browser state-management substrate,P3,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether pmndrs/zustand should remain active in the Browser state-management substrate lane and which seams should stay bounded.,"vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0013,HT_browser_support,pmndrs/zustand,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,Merge Bench,Browser control-panel and parameter UI layer,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether pmndrs/leva should remain active in the Browser control-panel and parameter UI layer lane and which seams should stay bounded.,"control store, schema parsing, useControls, plugin system, headless mode","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0014,HT_browser_support,pmndrs/leva,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,Donor Bench,Browser gesture and pointer-input substrate,P3,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether pmndrs/use-gesture should remain active in the Browser gesture and pointer-input substrate lane and which seams should stay bounded.,"gesture controller, drag engine, pointer capture, scroll prevention, React and vanilla bindings","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0015,HT_browser_support,pmndrs/use-gesture,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,Merge Bench,Browser layered-motion and explainer sidecar,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/parallax should remain active in the Browser layered-motion and explainer sidecar lane and which seams should stay bounded.,"layered page-space runtime, sticky layers, scroll-driven spring behavior, scrollTo","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0016,HT_browser_support,@react-spring/parallax,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,Merge Bench,Browser frame-loop and scheduling utility,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/rafz should remain active in the Browser frame-loop and scheduling utility lane and which seams should stay bounded.,"phased queues, timeout scheduling, throttling, demand versus always loop control","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0017,HT_browser_support,@react-spring/rafz,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,Merge Bench,Browser animatable-component substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/animated should remain active in the Browser animatable-component substrate lane and which seams should stay bounded.,"host creation, animated wrapper behavior, dependency observation, native-update fallback","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0018,HT_browser_support,@react-spring/animated,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,Donor Bench,Browser spring-runtime core,P3,,,,,,medium,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",repurpose,moderate modification,Determine whether @react-spring/core should remain active in the Browser spring-runtime core lane and which seams should stay bounded.,"controller orchestration, SpringValue runtime, useSprings lifecycle, frame advancement","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0019,HT_browser_support,@react-spring/core,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,Merge Bench,Browser motion utility substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/shared should remain active in the Browser motion utility substrate lane and which seams should stay bounded.,"globals customization, frame loop, interpolation helpers, fluid observer substrate","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0020,HT_browser_support,@react-spring/shared,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,Merge Bench,Browser motion type-contract substrate,P4,,,,,,medium,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",integrate,moderate modification,Determine whether @react-spring/types should remain active in the Browser motion type-contract substrate lane and which seams should stay bounded.,"shared type contracts, animatable types, interpolation types, utility types","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.,Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.,"@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",HT_browser_support_0021,HT_browser_support,@react-spring/types,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","MU_misc_0004","MU_misc","rhasspy/piper","","","","","","","Original global P0-P3 source audit retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.","Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.","Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.","high","voice-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","","","" +"met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","Donor Bench","Browser embodied coach surface","P2","","","","","","medium","Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.","repurpose","moderate modification","Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.","avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.","","Repurpose here means: turn it into a browser-side embodied coach or companion layer.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.","HT_browser_surface_0001","HT_browser_surface","met4citizen/talkinghead","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +"apache/echarts","https://github.com/apache/echarts","HyperTwist","Donor Bench","Browser analytics and reporting surface","P2","","","","","","medium","Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.","repurpose","moderate modification","Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces.","option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.","","Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.","HT_browser_surface_0002","HT_browser_surface","apache/echarts","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." +"ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","Merge Bench","Browser 3D analytics and explainer surface","P3","","","","","","medium","Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.","integrate","moderate modification","Determine whether echarts-gl should remain the bounded 3D analytics extension beneath echarts and what should stay outside HyperTwist core.","3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.","","Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.","HT_browser_surface_0003","HT_browser_surface","ecomfe/echarts-gl","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." +"KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","Donor Bench","Browser asset validation and viewer surface","P3","","","","","","medium","Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.","repurpose","moderate modification","Determine whether glTF-Sample-Viewer should remain the primary standards-validation viewer donor for browser asset tooling.","validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.","","Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.","HT_browser_surface_0004","HT_browser_surface","khronosgroup/gltf-sample-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer","https://github.com/google/model-viewer","HyperTwist","Donor Bench","Browser 3D presentation and inspection surface","P2","","","","","","medium","Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.","repurpose","moderate modification","Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces.","custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.","","Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.","HT_browser_surface_0005","HT_browser_surface","google/model-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.","Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." +"mrdoob/three.js","https://github.com/mrdoob/three.js","HyperTwist","Donor Bench","Browser 3D substrate","P2","","","","","","medium","Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.","repurpose","moderate modification","Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces.","renderer, scene, camera, math core, loaders, WebXR manager, addons, editor","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.","","Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.","HT_browser_surface_0006","HT_browser_surface","mrdoob/three.js","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.","Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","Merge Bench","Browser post-processing substrate","P3","","","","","","medium","Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.","integrate","moderate modification","Determine whether postprocessing should remain the bounded browser effect-composer substrate beneath the companion stack.","EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.","","Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.","HT_browser_surface_0007","HT_browser_surface","pmndrs/postprocessing","","","","","","","","Zlib","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.","Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser post-effect substrate beneath the landed browser spatial owner trio; do not treat it as separately live." +"pmndrs/react-three-fiber","https://github.com/pmndrs/react-three-fiber","HyperTwist","Donor Bench","Browser React 3D substrate","P2","","","","","","medium","Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.","repurpose","moderate modification","Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes.","Canvas, createRoot, reconciler runtime, event system, hooks, native path","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.","","Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.","HT_browser_surface_0008","HT_browser_surface","pmndrs/react-three-fiber","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.","Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","Merge Bench","Browser 3D helper and abstraction layer","P3","","","","","","medium","Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.","integrate","moderate modification","Determine which drei helpers should remain active merge candidates for browser companion surfaces and which should be ignored as generic convenience.","Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.","","Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.","HT_browser_surface_0009","HT_browser_surface","pmndrs/drei","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/xr","https://github.com/pmndrs/xr","HyperTwist","Donor Bench","Browser XR and immersive UI substrate","P2","","","","","","medium","Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.","repurpose","moderate modification","Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces.","XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.","","Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.","HT_browser_surface_0010","HT_browser_surface","pmndrs/xr","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.","Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md." +"pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","Donor Bench","Browser spatial UI surface","P2","","","","","","medium","Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.","repurpose","moderate modification","Determine whether pmndrs/uikit should remain the default browser spatial UI donor for HyperTwist companion surfaces.","flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.","","Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.","HT_browser_surface_0011","HT_browser_surface","pmndrs/uikit","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser spatial UI layer beside the landed pmndrs/xr lane; do not treat it as separately live." +"pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","Merge Bench","Browser motion and animation layer","P3","","","","","","medium","Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.","integrate","moderate modification","Determine which react-spring motion surfaces should remain active merge candidates for browser companion views.","Controller and SpringValue runtime, scheduler, layered explainer behavior, browser motion ergonomics","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.","","Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.","HT_browser_surface_0012","HT_browser_surface","pmndrs/react-spring","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side motion substrate inside the landed browser spatial support stack; do not treat it as separately live." +"screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","Donor Bench","Support-plane capture, history, and replay sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0001","HT_support_sidecars","screenpipe/screenpipe","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." +"remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","Donor Bench","Commercially licensed media-export and explainer sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.","player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0002","HT_support_sidecars","remotion-dev/remotion","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use." +"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","Browser 2D render substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether ecomfe/zrender should remain active in the Browser 2D render substrate lane and which seams should stay bounded.","scene graph, canvas and SVG painters, event handling, animation primitives","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0001","HT_browser_support","ecomfe/zrender","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live." +"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Browser WebGL substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pissang/claygl should remain active in the Browser WebGL substrate lane and which seams should stay bounded.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Browser viewer and editor sidecar","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pissang/clay-viewer should remain active in the Browser viewer and editor sidecar lane and which seams should stay bounded.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","Browser asset renderer substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether KhronosGroup/glTF-Sample-Renderer should remain active in the Browser asset renderer substrate lane and which seams should stay bounded.","GltfView, GltfState, resource loader, user camera, renderer core","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0004","HT_browser_support","khronosgroup/gltf-sample-renderer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." +"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","Browser asset editor and inspection surface","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/space-opera should remain active in the Browser asset editor and inspection surface lane and which seams should stay bounded.","editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0005","HT_browser_support","google/model-viewer/packages/space-opera","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","Browser fidelity QA harness","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/render-fidelity-tools should remain active in the Browser fidelity QA harness lane and which seams should stay bounded.","golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0006","HT_browser_support","google/model-viewer/packages/render-fidelity-tools","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","Merge Bench","Browser emphasis and post-processing extension","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/model-viewer-effects should remain active in the Browser emphasis and post-processing extension lane and which seams should stay bounded.","effect composer integration, outline, SSAO, emphasis behavior, custom-element surface","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0007","HT_browser_support","google/model-viewer/packages/model-viewer-effects","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." +"google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","Merge Bench","Browser docs and demo surface","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/modelviewer.dev should remain active in the Browser docs and demo surface lane and which seams should stay bounded.","live docs generation, snippet-to-demo coupling, sidebar and HTML generation","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0008","HT_browser_support","google/model-viewer/packages/modelviewer.dev","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." +"google/model-viewer/packages/shared-assets","https://github.com/google/model-viewer/tree/main/packages/shared-assets","HyperTwist","Donor Bench","Boundary-sensitive sample-asset and test-fixture pack","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","repurpose","architecture only","Determine whether google/model-viewer/packages/shared-assets should remain active in the Browser sample-asset and fixture pack lane and which seams should stay bounded.","asset provenance, attribution terms, environment fixtures, sample models, fetch script behavior","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.","Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0009","HT_browser_support","google/model-viewer/packages/shared-assets","","","","","","","","Apache-2.0 container; mixed per-asset terms","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.","Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.","Preserve container notices and review each selected asset attribution or usage condition separately before shipping.","Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.","high","mixed-asset-whitelist-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.","selected_not_live_boundary_sensitive","phase0r_boundary_sensitive_eval_then_adapter_or_sidecar","Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use." +"pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","Merge Bench","Browser React effect-wrapper layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/react-postprocessing should remain active in the Browser React effect-wrapper layer lane and which seams should stay bounded.","React EffectComposer orchestration, selection model, wrapper ergonomics","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0010","HT_browser_support","pmndrs/react-postprocessing","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate React wrapper above pmndrs/postprocessing inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","Merge Bench","Browser 3D utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/three-stdlib should remain active in the Browser 3D utility substrate lane and which seams should stay bounded.","controls, loaders, WebXR helpers, post-processing helpers, utility exports","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0011","HT_browser_support","pmndrs/three-stdlib","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate shared utility shelf beneath the landed browser spatial owner trio; do not treat it as separately live." +"pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","Merge Bench","Browser math-helper substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/maath should remain active in the Browser math-helper substrate lane and which seams should stay bounded.","easing and damp functions, random helpers, geometry utilities","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0012","HT_browser_support","pmndrs/maath","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate math-helper layer inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","Donor Bench","Browser state-management substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether pmndrs/zustand should remain active in the Browser state-management substrate lane and which seams should stay bounded.","vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0013","HT_browser_support","pmndrs/zustand","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side state substrate inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","Merge Bench","Browser control-panel and parameter UI layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/leva should remain active in the Browser control-panel and parameter UI layer lane and which seams should stay bounded.","control store, schema parsing, useControls, plugin system, headless mode","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0014","HT_browser_support","pmndrs/leva","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate authoring and debug control sidecar inside the landed browser spatial support stack; do not treat it as separately live." +"pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","Donor Bench","Browser gesture and pointer-input substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether pmndrs/use-gesture should remain active in the Browser gesture and pointer-input substrate lane and which seams should stay bounded.","gesture controller, drag engine, pointer capture, scroll prevention, React and vanilla bindings","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0015","HT_browser_support","pmndrs/use-gesture","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate browser gesture and pointer-input substrate inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","Merge Bench","Browser layered-motion and explainer sidecar","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/parallax should remain active in the Browser layered-motion and explainer sidecar lane and which seams should stay bounded.","layered page-space runtime, sticky layers, scroll-driven spring behavior, scrollTo","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0016","HT_browser_support","@react-spring/parallax","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","Use directly as a bounded browser-side dependency for explainer and narrative surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate layered-motion sidecar beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","Merge Bench","Browser frame-loop and scheduling utility","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/rafz should remain active in the Browser frame-loop and scheduling utility lane and which seams should stay bounded.","phased queues, timeout scheduling, throttling, demand versus always loop control","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0017","HT_browser_support","@react-spring/rafz","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","Merge Bench","Browser animatable-component substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/animated should remain active in the Browser animatable-component substrate lane and which seams should stay bounded.","host creation, animated wrapper behavior, dependency observation, native-update fallback","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0018","HT_browser_support","@react-spring/animated","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate animatable-component package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","Donor Bench","Browser spring-runtime core","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether @react-spring/core should remain active in the Browser spring-runtime core lane and which seams should stay bounded.","controller orchestration, SpringValue runtime, useSprings lifecycle, frame advancement","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0019","HT_browser_support","@react-spring/core","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate spring-runtime core beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","Merge Bench","Browser motion utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/shared should remain active in the Browser motion utility substrate lane and which seams should stay bounded.","globals customization, frame loop, interpolation helpers, fluid observer substrate","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0020","HT_browser_support","@react-spring/shared","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." +"@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","Merge Bench","Browser motion type-contract substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/types should remain active in the Browser motion type-contract substrate lane and which seams should stay bounded.","shared type contracts, animatable types, interpolation types, utility types","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0021","HT_browser_support","@react-spring/types","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","Use directly as a bounded browser-side dependency where those contracts are actually needed.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-F closed for the owner trio. Retain as the subordinate type-contract package beneath pmndrs/react-spring inside the landed browser spatial support stack; do not treat it as separately live." diff --git a/docs/repo_portfolio_unified_v6_3_README.txt b/docs/repo_portfolio_unified_v6_3_README.txt index 3cbb5ff..4c25849 100644 --- a/docs/repo_portfolio_unified_v6_3_README.txt +++ b/docs/repo_portfolio_unified_v6_3_README.txt @@ -13,9 +13,9 @@ Why this matters: * the v6.3 pack is excellent at repo selection, donor posture, and legal/architectural strategy * it is **not** by itself a proof of current live implementation state -* HyperTwist currently has `71` shallow-eval rows, but only `7` currently verified live repos in checked `UnrealHyperTwist` surfaces -* `5` of those `6` are permissive `MIT` lanes -* `1` of those `6` is the restrictive `onionhoney/roux-trainers` lane, which must now be treated as the only currently verified restrictive repo that was properly clean-roomed and then implemented +* HyperTwist currently has `71` shallow-eval rows, with `14` currently verified live repos in checked `UnrealHyperTwist` surfaces +* `13` of those `14` are permissive lanes +* `1` of those `14` is the restrictive `onionhoney/roux-trainers` lane, which remains the only currently verified restrictive repo that was properly clean-roomed and then implemented Interpretation rule: @@ -251,7 +251,7 @@ In plain English: this is the **priority and sequencing file for real repo inspe After the 2026-05-11 correction, treat this file as: * the source-audit campaign map -* plus the repo reset lane board for the remaining `65` not-yet-live HyperTwist rows +* plus the repo reset lane board for the remaining `57` not-yet-live HyperTwist rows --- diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md b/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md index 28fc481..19dfb0a 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md @@ -75,8 +75,8 @@ For any HyperTwist repo, the coding model must determine: For HyperTwist, keep this explicit: - current shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `11` -- permissive live lanes: `10` +- currently verified live/implemented in checked Unreal surfaces: `14` +- permissive live lanes: `13` - restrictive live lane: `1` - the restrictive landed lane is `onionhoney/roux-trainers`, and it is to be treated as properly clean-roomed and then implemented @@ -93,8 +93,8 @@ into: ## Reset rule -Before recommending new HyperTwist donor-shaped widening from the remaining `61` current non-live rows: +Before recommending new HyperTwist donor-shaped widening from the remaining `57` current non-live rows: - do not reopen the already closed `Phase 0R`, `Phase 1R`, or `Phase 2R` packets -- preserve the eleven landed rows as current truth -- continue from the closed packet sequence, currently `Phase 3R-F` +- preserve the fourteen landed rows as current truth +- continue from the closed packet sequence, with `Phase 4R-A` as the next non-optional move and the optional `Phase 3R-G` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md index 3c9b01d..0486cd9 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md @@ -15,10 +15,10 @@ Do not reopen broad donor-driven widening as if the whole retained portfolio wer Current truth: -- `11` repos are currently verified live in checked Unreal surfaces -- `10` are permissive `MIT` or `Apache-2.0` +- `14` repos are currently verified live in checked Unreal surfaces +- `13` are permissive `MIT` or `Apache-2.0` - `1` is the restrictive `onionhoney/roux-trainers` lane that is already properly clean-roomed and implemented -- `Phase 0R` is now closed for the remaining `61` non-live rows +- `Phase 0R` is now closed for the remaining `57` non-live rows - `Phase 1R` is now closed as the retained-set contract and handoff overhaul - `Phase 2R` is now closed as the retained-set ownership and acceptance packet sequence - `Phase 3R-A` is now closed as the landed `Aarav2709/KubeTimr` widening packet @@ -26,13 +26,14 @@ Current truth: - `Phase 3R-C` is now closed as the landed `apache/echarts` widening packet - `Phase 3R-D` is now closed as the landed `google/model-viewer` widening packet - `Phase 3R-E` is now closed as the landed `met4citizen/TalkingHead` widening packet +- `Phase 3R-F` is now closed as the landed `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` widening packet Next sequence: -1. preserve the eleven landed lanes +1. preserve the fourteen landed lanes 2. use the retained-set contract as the only legal/roadmap routing surface for non-live rows 3. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, and `met4citizen/TalkingHead` on preserve-and-enhance footing through their landed packets -4. continue broader permissive widening from `Phase 3R-F` +4. continue broader widening from `Phase 4R-A`, with optional `Phase 3R-G` comparison work only if the landed primary browser spatial stack exposes a real gap ## Suggested repo structure diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md b/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md index 501a812..a844ad5 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md @@ -42,17 +42,20 @@ They still must point back to `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md` for At the moment, HyperTwist should be described this way: - current curated shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `11` -- permissive live lanes: `10` +- currently verified live/implemented in checked Unreal surfaces: `14` +- permissive live lanes: `13` - restrictive live lanes: `1` -The ten permissive live lanes are: +The thirteen permissive live lanes are: - `Aarav2709/KubeTimr` - `apache/echarts` - `abunickabhi/5style-Trainer` - `google/model-viewer` - `Hypercubers/hypercubing.xyz` +- `mrdoob/three.js` +- `pmndrs/react-three-fiber` +- `pmndrs/xr` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` - `met4citizen/TalkingHead` @@ -116,7 +119,7 @@ Current practical interpretation: - `Phase 2R-B` is now fully closed for the primary retained permissive support-plane rows in scope - `Phase 2R-C` is now fully closed for the final residual `0R-B` permissive rows - `Phase 2R` is now fully closed for the retained permissive set -- the eleven already-live rows now have source-backed preservation authority in `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` +- the fourteen already-live rows now have source-backed preservation authority in `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` - the retained-set contract now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md` - the core ownership and acceptance packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` - the support-plane ownership and acceptance packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` @@ -126,7 +129,8 @@ Current practical interpretation: - the landed `apache/echarts` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md` - the landed `google/model-viewer` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md` - the landed `met4citizen/TalkingHead` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md` -- the next bounded move is `Phase 3R-F` +- the landed `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md` +- the next bounded move is `Phase 4R-A` Read together with: @@ -155,7 +159,7 @@ These are often strategic donors or comparators rather than foundations. Current HyperTwist correction: -- eight permissive lanes are already live, including the landed analytics/reporting lane and the landed hypercubing knowledge and community-reference lane +- thirteen permissive lanes are already live, including the landed analytics/reporting lane, the landed hypercubing knowledge and community-reference lane, and the landed browser spatial owner trio - `onionhoney/roux-trainers` is the one restrictive training lane already landed through clean-room implementation - timer comparators such as `cstimer` still remain benchmark/reference rows until deep evaluation says otherwise diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md b/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md index 96239bc..2daed55 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md @@ -5,11 +5,11 @@ Before widening new HyperTwist donor-driven implementation beyond the already landed lanes, preserve this current truth: - current shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `11` -- permissive live lanes: `10` +- currently verified live/implemented in checked Unreal surfaces: `14` +- permissive live lanes: `13` - restrictive live lane: `1` - the restrictive landed lane is `onionhoney/roux-trainers`, and it is to be treated as properly clean-roomed and then implemented -- `Phase 0R` is now closed for the remaining `61` non-live rows +- `Phase 0R` is now closed for the remaining `57` non-live rows - `Phase 1R` is now closed as the retained-set contract and handoff overhaul - `Phase 2R` is now closed as the retained-set ownership and acceptance packet sequence - `Phase 3R-A` is now closed as the landed `Aarav2709/KubeTimr` timer subsystem widening packet @@ -17,15 +17,16 @@ Before widening new HyperTwist donor-driven implementation beyond the already la - `Phase 3R-C` is now closed as the landed `apache/echarts` analytics and reporting widening packet - `Phase 3R-D` is now closed as the landed `google/model-viewer` browser presentation, compact editor, and standards-aware asset-QA widening packet - `Phase 3R-E` is now closed as the landed `met4citizen/TalkingHead` embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed widening packet +- `Phase 3R-F` is now closed as the landed `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` browser spatial support widening packet Current routing truth: - retained rows total: `68` - discarded from the active retained set: `3` -- active non-live implementation-board rows: `48` +- active non-live implementation-board rows: `45` - retained benchmark, oracle, or clean-room-later rows outside the active implementation board: `9` -The next bounded move is `Phase 3R-F`, not renewed donor evaluation or pre-packet ratification. +The next bounded move is `Phase 4R-A`, with the optional `Phase 3R-G` browser comparison lane deferred unless the landed primary browser spatial stack exposes a real gap. ## Reset phases