Close HyperTwist Phase 0R packet 0R-D

This commit is contained in:
axiomlogicnexus 2026-05-13 00:26:29 +02:00
parent a0aa65b932
commit e63ab1b4ea
9 changed files with 472 additions and 43 deletions

View file

@ -163,6 +163,19 @@ Practical implication:
- if a future instance is about to integrate `Hyperspeedcube`, `qbr`, `rubix-cube-solver`, `KubeTimr`, `MagicTile`, `Magic120Cell`, or `MagicCube5D`, it should not start from the shallow CSV row or bucket label
- it should start from `0R-A`, then check `REPO_LICENSE_TRACKING.md`, then return to the schedule
`Packet 0R-D` required one more boundary rule because it covers restrictive clean-room rows.
Current correction:
- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md` is now the governance and Model A authority for the four restrictive retained rows
- it records what source was actually read, what value must be salvaged, what was not promoted, and why
- the repo-specific scrubbed files in `C:\Workspaces\HyperTwist\clean-room-specs\` remain the only implementation-safe Model B handoff inputs
Practical implication:
- if a future instance is about to implement `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, or `kash/cubedesk`, it must read `0R-D`, then `REPO_LICENSE_TRACKING.md`, then the repo-specific scrubbed Model A handoff
- it must not treat `0R-D` itself as a substitute for the scrubbed handoff during Model B work
## Restart phase sequence
### Phase `0R` — deep repo source integration evaluation
@ -414,21 +427,24 @@ After this reconciliation:
## Current packet status
`Packet 0R-A`, `Packet 0R-B`, and `Packet 0R-C` are now closed as evaluation packets.
`Packet 0R-A`, `Packet 0R-B`, `Packet 0R-C`, and `Packet 0R-D` are now closed as evaluation packets.
See:
- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md`
- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md`
- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md`
- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`
Result:
- all seven `0R-A` repos remain retained
- all thirty-six `0R-B` repos remain retained
- all six `0R-C` repos remain retained
- all four `0R-D` repos remain retained
- `Packet 0R-B` is now a deep-source integration authority packet, not merely a permissive backlog summary
- `Packet 0R-C` is now the deep-source boundary-use authority for the mixed, attributed, asset-term, and commercial rows
- `Packet 0R-D` is now the governance and Model A authority for the restrictive clean-room rows
- none of those packet rows are currently proven live in checked Unreal surfaces
- `Aarav2709/KubeTimr` is the earliest straight permissive subsystem implementation candidate after `Phase 2R`
- `Hypercubers/hypercubing.xyz` is the retained knowledge/curriculum/community donor
@ -443,6 +459,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
- `Packet 0R-A`, `Packet 0R-B`, and `Packet 0R-C` are the source-value and exclusion-rationale authorities for their retained rows
- `Packet 0R-D` is the governance and Model A authority for its retained rows, but not the Model B handoff artifact
- those packet docs must now also carry concise implementation-facing licensing snapshots so an integrating instance does not miss the legal posture at handoff time
- full license, attribution, notice, asset-term, and provenance obligations still belong in `docs/REPO_LICENSE_TRACKING.md`
@ -451,5 +468,5 @@ License-tracking boundary:
The next bounded move is:
1. keep `Phase 3R+` widening frozen
2. open `Packet 0R-D`
3. continue the remaining non-permissive `Phase 0R` backlog until the broader `Phase 0R` set is actually closed
2. open `Packet 0R-E`
3. continue the remaining reference, benchmark, reserve, and discard `Phase 0R` backlog until the broader `Phase 0R` set is actually closed

View file

@ -0,0 +1,358 @@
# HyperTwist Phase 0R Packet 0R-D Deep Source Evaluation
Created on `2026-05-13`
## Status
`Packet 0R-D` is now `closed` as a `Phase 0R` evaluation packet.
This packet applies the same deep-source standard already established by `0R-A`, `0R-B`, and `0R-C`:
- read the upstream source directly
- salvage all meaningful value
- omit only when the surface is:
- an inferior duplicate
- superseded by a stronger retained donor
- off topic to HyperTwist's retained product scope
- host-shell glue with no durable architecture value
- record the rationale every time something is not promoted
For these four repos, this document is now the canonical `governance and Model A authority` packet.
Before a future instance implements any `0R-D` repo, it must read:
1. this document for source-value extraction, exclusion rationale, and clean-room lane selection
2. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) for repo-row legal and provenance obligations
3. the repo-specific scrubbed Model A handoff in `C:\Workspaces\HyperTwist\clean-room-specs\`
4. [HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md](C:/HyperTwist/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md:1) for sequencing
## Purpose
This packet redoes `Phase 0R-D` as a true deep source parsing packet for:
- `cubing/alg.js`
- `cubing/twisty.js`
- `HactarCE/2x2x2x2-Scrambler`
- `kash/cubedesk`
It answers, repo by repo:
- what was actually read in source
- what value HyperTwist should salvage
- what is subordinate, duplicate, inferior, or off topic
- why that non-promotion decision was made
- which repo should own a domain when restrictive rows overlap with already-retained permissive or boundary-sensitive lanes
- how the repo should enter `Phase 2R` and later `Phase 5R` clean-room implementation work
## Storage boundary
To stop future confusion, the storage boundary is explicit:
- `this packet doc`: source-value extraction, implementation posture, overlap resolution, exclusion rationale, and refreshed Model A scope
- [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1): repo-row license, attribution, notice, publication, subtree, and provenance obligations
- `C:\Workspaces\HyperTwist\clean-room-specs\*.model-a.md`: the only scrubbed Model B handoff inputs for later clean-room implementation
- [HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md](C:/HyperTwist/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md:1): row state and next-step board
- [HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md](C:/HyperTwist/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md:1): packet sequencing and restart phases
- [HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md:1): cross-location authority routing
This packet is a `governance and Model A` authority doc, not a Model B implementation handoff.
Model B must not treat this document as a substitute for the scrubbed clean-room specs.
## Packet licensing snapshot
- `cubing/alg.js`: `GPL-3.0-or-later`
- `cubing/twisty.js`: `GPL-3.0-or-later`
- `HactarCE/2x2x2x2-Scrambler`: `GPL-3.0`
- `kash/cubedesk`: `GPLv3-or-later` in `README.md` and `LICENSE.md`, but `package.json` says `All Rights Reserved`
## Inputs used
This rewrite used:
- current reset docs in `C:\HyperTwist\docs`
- current restrictive mirrors under:
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\twisty.js`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\HactarCE\2x2x2x2-Scrambler`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\kash\cubedesk`
- the preexisting Model A handoffs under:
- `C:\Workspaces\HyperTwist\clean-room-specs\cubing-alg-js.model-a.md`
- `C:\Workspaces\HyperTwist\clean-room-specs\cubing-twisty-js.model-a.md`
- `C:\Workspaces\HyperTwist\clean-room-specs\hactarce-2x2x2x2-scrambler.model-a.md`
- `C:\Workspaces\HyperTwist\clean-room-specs\kash-cubedesk.model-a.md`
- checked live Unreal surfaces under:
- `C:\HyperTwist\UnrealHyperTwist\Source`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog`
## Live-state result
Current live-evidence check result for all four `0R-D` repos:
- no exact live-surface match found in checked Unreal source or materialized catalog
Important nuance:
- first-party Unreal code does contain generic `2x2x2x2` topology identifiers
- that is not proof that `HactarCE/2x2x2x2-Scrambler` source or a direct donor implementation is already live
That means:
- none of these four are currently proven live in checked Unreal surfaces
- all four remain retained clean-room candidates, not landed implementation lanes
## Packet-wide hierarchy
This packet does not treat all four restrictive rows as equal.
| Domain | Primary retained owner | Secondary retained owner | Non-promotion rule |
| --- | --- | --- | --- |
| Algorithm language, parser, AST, validation, and interchange semantics | `cubing/alg.js` | none in `0R-D` | Do not let this row collapse into `cubing/cubing.js` custody. Keep it as a focused clean-room lane for algorithm-language behavior only. |
| Compact embedded viewer/player shell and observer-driven playback behavior | `cubing/twisty.js` | none in `0R-D` | Do not let this row displace `cubing/cubing.js` for classic-cubing semantics or `Hyperspeedcube` for the hyper runtime. Keep it as a compact playback clean-room lane. |
| Melinda `2x2x2x2` random-state, solvability, and flat debug semantics | `HactarCE/2x2x2x2-Scrambler` | none in `0R-D` | Keep it narrow. Do not widen it into a general runtime, trainer shell, or full hyper-puzzle foundation. |
| Broad timer/trainer/stats/smartcube/match product-pattern extraction | `kash/cubedesk` | none in `0R-D` | Do not let the full CubeDesk app shell displace `Hyperspeedcube`, `qbr`, or the already-retained permissive trainer stack. Mine it selectively as a strategic clean-room donor. |
## Packet outcome summary
- retained: `4`
- discarded: `0`
- newly proven live: `0`
Most important scheduling consequences:
- the restrictive clean-room candidate backlog is now closed as a `Phase 0R` evaluation class
- all four rows remain `clean-room only`; none is approved for direct donor use
- all four Model A handoffs were refreshed from the deeper source read and remain the only Model B input surface
- the next clean packet is `0R-E`
## Repo evaluations
### `cubing/alg.js`
Inspected source surfaces:
- [README.md](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/README.md:1)
- [package.json](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/package.json:1)
- [src/parser.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/parser.ts:1)
- [src/json.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/json.ts:1)
- [src/algorithm/alg-part.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/algorithm/alg-part.ts:1)
- [src/algorithm/block-move.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/algorithm/block-move.ts:1)
- [src/algorithm/index.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/algorithm/index.ts:1)
- [src/traversal.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/traversal.ts:1)
- [src/validation.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/validation.ts:1)
- [src/keyboard.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/keyboard.ts:1)
- [src/url.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/alg.js/src/url.ts:1)
Licensing posture:
- `GPL-3.0-or-later`
- retain only as a focused clean-room parser and interchange donor
- Model B may only consume [cubing-alg-js.model-a.md](C:/Workspaces/HyperTwist/clean-room-specs/cubing-alg-js.model-a.md:1)
High-value salvage:
- the parse pipeline is cleanly layered: text input, parser output, JSON-to-object reconstruction, then optional validator passes
- the AST family is durable donor value: immutable `Sequence`, `Group`, `BlockMove`, `Commutator`, `Conjugate`, `Pause`, newline, and comment nodes
- `BlockMove` captures plain, inner-layer, and ranged-layer semantics in one compact move representation
- the traversal layer is much stronger than a basic parse tree walker; it already encodes invert, expand, structural equality, move coalescing, and canonical text serialization patterns
- `json.ts` adds a second interchange boundary beyond the parser itself, which matters if HyperTwist later wants serialized algorithm payloads independent of text form
- the validation layer carries real semantic rules for SiGN families, flat-alg restrictions, and layer-range legality
- keyboard-to-move mapping is an intentionally separate boundary rather than an accidental parser side effect
- the URL layer shows a production-shaped serialization scheme plus link generation for alg playback/editor endpoints
Subordinate or later value:
- example, debug, HTML test, and webpack packaging surfaces are not the retained center of gravity
- the specific keycode map is useful, but should remain remappable rather than becoming a canonical first-party constant
- the `alg.cubing.net` link surface is valuable as an interchange pattern, not as a primary runtime owner
Non-promotion decisions and rationale:
- do not collapse this repo into the broader `cubing/cubing.js` lane for custody purposes: `boundary discipline`
- do not use the exact parser or grammar source directly in a proprietary core: `clean-room only`
- do not promote browser/demo scaffolding as donor value: `host-shell glue`
- do not treat `alg.js` as a runtime or viewer owner: `off topic` relative to its strongest parser/AST/interchange value
Integration call:
- retain as the primary restrictive clean-room donor for algorithm-language behavior
- use it in `Phase 2R` to freeze first-party parser, AST, validation, serialization, keyboard-input, and URL/interchange contracts
- refresh the Model A handoff with the deeper node-family and traversal findings
- if later implementation proceeds, schedule Model B work in `Phase 5R`, not as direct donor use
### `cubing/twisty.js`
Inspected source surfaces:
- [README.md](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/README.md:1)
- [package.json](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/package.json:1)
- [src/twisty.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/twisty.ts:1)
- [src/widget.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/widget.ts:1)
- [src/anim.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/anim.ts:1)
- [src/puzzle.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/puzzle.ts:1)
- [src/cursor.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/cursor.ts:1)
- [src/3D/twisty3D.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/3D/twisty3D.ts:1)
- [src/3D/cube3D.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/cubing/twisty.js/src/3D/cube3D.ts:1)
Licensing posture:
- `GPL-3.0-or-later`
- the README now says the functionality moved into `cubing.js`, but this mirror still remains a separate restrictive custody lane
- Model B may only consume [cubing-twisty-js.model-a.md](C:/Workspaces/HyperTwist/clean-room-specs/cubing-twisty-js.model-a.md:1)
High-value salvage:
- `twisty.ts` shows a clean embedded surface: auto-initialized `<twisty>` elements, explicit `custom` initialization escape hatch, and attribute-to-config extraction
- the player shell is a clear composition of animation model, scrubber, control bar, and visualization views
- `anim.ts` contributes a real observer-driven playback core with cursor, direction, and jump dispatch rather than ad hoc callbacks
- `cursor.ts` is strong donor value because it turns expanded algorithm sequences into timestamped playback state, move fractions, and move-boundary stepping
- `puzzle.ts` contributes a compact abstract puzzle contract plus the `KPuzzle`-backed adapter boundary that keeps playback separate from any one concrete puzzle implementation
- `widget.ts` shows how to layer 2D SVG, 3D view, scrubber, control bar, and readout into a single embeddable player
- the 3D layer is narrower than a general renderer, but it still shows bounded camera/vantage management and `333`-specific animated cube presentation
Subordinate or later value:
- debug text views, HTML demo pages, and standalone packaging are not primary donor value
- the hardcoded `333` cube rendering path is useful as a clean-room reference surface, but not the main retained value compared with the player and cursor contracts
- the repository's deprecated standalone identity is context, not a reason to merge custody with other rows
Non-promotion decisions and rationale:
- do not treat this repo as a general runtime owner: `superseded by stronger retained donor`
- do not promote the exact `three.js` `333` rendering implementation into first-party core as-is: `implementation detail better reauthored first-party`
- do not flatten it into the broader `cubing/cubing.js` lane for governance purposes: `boundary discipline`
- do not elevate demo scaffolding and debug overlays into donor value: `host-shell glue`
Integration call:
- retain as the primary restrictive clean-room donor for compact embedded viewer/player behavior
- use it in `Phase 2R` to freeze element bootstrapping, observer-driven playback, scrubber/control semantics, and puzzle-adapter contracts
- refresh the Model A handoff with the deeper cursor, observer, and visualization-fallback findings
- if later implementation proceeds, schedule Model B work in `Phase 5R`, not as direct donor use
### `HactarCE/2x2x2x2-Scrambler`
Inspected source surfaces:
- [README.md](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/README.md:1)
- [src/cljc/scrambler/puzzle/core.cljc](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/src/cljc/scrambler/puzzle/core.cljc:1)
- [src/cljc/scrambler/puzzle/moves.cljc](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/src/cljc/scrambler/puzzle/moves.cljc:1)
- [src/cljc/scrambler/puzzle/state_generator.cljc](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/src/cljc/scrambler/puzzle/state_generator.cljc:1)
- [src/cljc/scrambler/puzzle/permutation_utils.cljc](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/src/cljc/scrambler/puzzle/permutation_utils.cljc:1)
- [src/cljs/scrambler/ui/flat_view.cljs](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/src/cljs/scrambler/ui/flat_view.cljs:1)
- [src/cljs/scrambler/ui/main.cljs](C:/Workspaces/HyperTwist/mirrors/restrictive/HactarCE/2x2x2x2-Scrambler/src/cljs/scrambler/ui/main.cljs:1)
Licensing posture:
- `GPL-3.0`
- upstream source explicitly records a ported lineage from `pentaquark394` and says some algorithms and comments were copied nearly verbatim
- Model B may only consume [hactarce-2x2x2x2-scrambler.model-a.md](C:/Workspaces/HyperTwist/clean-room-specs/hactarce-2x2x2x2-scrambler.model-a.md:1)
High-value salvage:
- the solved-state representation is compact and real: piece-position vector plus per-piece orientation vectors
- `core.cljc` carries durable piece-string and sticker-color derivation semantics, not just random generation
- handedness and corner-twist semantics are first-class, which is the real reason this repo stays useful despite its narrow scope
- `state_generator.cljc` gives a full solvable-state pipeline: parity-preserving piece shuffle, random orientation shuffle, corner-twist repair, and handedness repair
- `moves.cljc` is strong donor value because moves are represented as transformed solved-state objects and then composed, inverted, and grouped into named move families
- `flat_view.cljs` provides a lightweight but informative front/back flat debug view with piece labels and sticker peeks
Subordinate or later value:
- the current button shell and placeholder `"Scramble goes here"` output are not the retained value
- the planned solver, serialization, and simulator ideas are roadmap hints rather than current strong donor surfaces
- the exact Clojure data shapes are not important beyond the behavioral contracts they imply
Non-promotion decisions and rationale:
- do not treat this row as a general hyper runtime donor: `off topic`
- do not preserve the exact copied-port algorithms, comments, or docstrings: `clean-room only`
- do not elevate the minimal web shell into a product pattern donor: `host-shell glue`
- do not widen this repo into a major trainer or viewer owner: `narrow retained micro-domain`
Integration call:
- retain as the primary restrictive clean-room donor for Melinda `2x2x2x2` state generation and solvability semantics
- use it in `Phase 2R` to freeze the state format, solvability rules, move-family behavior, and debug-view acceptance criteria
- refresh the Model A handoff with the fuller state, parity, and view findings
- if later implementation proceeds, schedule Model B work in `Phase 5R`, not as direct donor use
### `kash/cubedesk`
Inspected source surfaces:
- [README.md](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/README.md:1)
- [LICENSE.md](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/LICENSE.md:1)
- [package.json](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/package.json:1)
- [schema.prisma](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/schema.prisma:1)
- [server/app.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/app.ts:1)
- [shared/solve.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/shared/solve.ts:1)
- [shared/integration.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/shared/integration.ts:1)
- [client/util/cubes/cube_types.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/util/cubes/cube_types.ts:1)
- [client/util/cubes/cube_scrambles.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/util/cubes/cube_scrambles.ts:1)
- [client/util/smart_scramble.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/util/smart_scramble.ts:1)
- [client/components/timer/Timer.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/timer/Timer.tsx:1)
- [client/components/timer/smart_cube/SmartCube.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/timer/smart_cube/SmartCube.tsx:1)
- [client/components/timer/smart_cube/visual/index.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/timer/smart_cube/visual/index.ts:1)
- [client/components/timer/smart_cube/visual/core/RubiksCube.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/timer/smart_cube/visual/core/RubiksCube.ts:1)
- [client/components/trainer/Trainer.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/trainer/Trainer.tsx:1)
- [client/components/trainer/util/init.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/trainer/util/init.ts:1)
- [client/db/trainer/query.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/db/trainer/query.ts:1)
- [client/db/solves/query.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/db/solves/query.ts:1)
- [client/components/solve_info/SolveInfo.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/solve_info/SolveInfo.tsx:1)
- [client/components/solve_info/util/solution.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/solve_info/util/solution.ts:1)
- [client/components/solve_info/stats_info/recognition_chart/RecognitionChart.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/solve_info/stats_info/recognition_chart/RecognitionChart.tsx:1)
- [client/components/solve_info/stats_info/ll_trainer/LLTrainer.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/solve_info/stats_info/ll_trainer/LLTrainer.tsx:1)
- [client/components/stats/Stats.tsx](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/client/components/stats/Stats.tsx:1)
- [server/resolvers/Stats.resolver.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/resolvers/Stats.resolver.ts:1)
- [server/resolvers/Leaderboards.resolver.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/resolvers/Leaderboards.resolver.ts:1)
- [server/match/init.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/init.ts:1)
- [server/match/util.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/util.ts:1)
- [server/match/update/standings.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/update/standings.ts:1)
- [server/match/pair/pair_logic.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/pair/pair_logic.ts:1)
- [server/match/pair/elo/elo_matching.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/pair/elo/elo_matching.ts:1)
- [server/match/match_types/head_to_head.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/match_types/head_to_head.ts:1)
- [server/match/match_types/elimination.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/match/match_types/elimination.ts:1)
- [server/util/solve/turns.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/util/solve/turns.ts:1)
- [server/util/solve/ll_states.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/util/solve/ll_states.ts:1)
- [server/util/pro.ts](C:/Workspaces/HyperTwist/mirrors/restrictive/kash/cubedesk/server/util/pro.ts:1)
Licensing posture:
- `README.md` and `LICENSE.md` say `GPLv3-or-later`
- `package.json` says `CubeDesk, Inc. All Rights Reserved`
- direct donor use is blocked by the contradiction even before the broader GPL constraints are considered
- Model B may only consume [kash-cubedesk.model-a.md](C:/Workspaces/HyperTwist/clean-room-specs/kash-cubedesk.model-a.md:1)
High-value salvage:
- `schema.prisma` is major donor value because it makes solve, session, user, integration, notification, trainer, and match boundaries explicit rather than leaving them implicit in UI code
- `server/app.ts` shows a real service composition pattern for GraphQL, Prisma, uploads, webhooks, Redis, search, socket setup, and template initialization without pretending the whole app is one blob
- the timer lane is broader than a stopwatch: layout/focus-mode shell, multiple timing backends, scramble surfaces, timer modules, and modal-safe embedding
- the smart-cube lane is especially valuable: turn queueing, preflight scramble completion, automatic timer start after scramble completion, inspection-time capture, solved-state management, and synchronized visual playback
- the trainer lane is strong donor value because it combines deterministic seeded algorithm selection, hydrated local trainer DBs, favorites/customization, and timer-modal composition for drill sessions
- the solve/session/stats lane is a real product system, not just charts: solve sanitation, solve/session/training-session/game-session distinctions, recognition and execution panels, LL-case extraction, shareable solve detail, and filtered local DB queries
- the multiplayer lane is strong retained value: Redis-backed socket room topology, lobby pairing, widening ELO windows, standings updates, disconnect handling, and match-type abstraction
- the repo also preserves later-value surfaces for linked services, feature gating, notification preferences, and leaderboard publication patterns
Subordinate or later value:
- community shell, landing pages, merch/ads, legal pages, profile cosmetics, and general site chrome are not the retained center of gravity
- Stripe/Pro membership, Discord/WCA specifics, and broader account-management flows are later product-shell concerns, not core donor value
- generic GraphQL boilerplate, CSS system, and commodity common components are implementation scaffolding, not the main reason this row is retained
- many cube-type enumerations and classic speedcubing assumptions are useful context, but should not dictate HyperTwist's final hyper-focused domain model
Non-promotion decisions and rationale:
- do not attempt a whole-app clean-room clone of CubeDesk: `host-shell glue`, `off topic`, and `boundary cost exceeds naive use`
- do not pull billing, paid-feature, Discord-role, or WCA-account flows into the early HyperTwist core: `off topic`
- do not let CubeDesk displace `Hyperspeedcube`, `qbr`, or the already-retained permissive trainer donors for foundation ownership: `superseded by stronger retained donor`
- do not treat the contradictory package metadata as a paperwork nuisance: `license contradiction must remain explicit`
- do not promote marketing, admin, ads, or merch surfaces into donor value: `off topic`
Integration call:
- retain as the broad strategic clean-room donor for timer, trainer, solve/session/stats, smart-cube, and multiplayer product-pattern extraction
- use it in `Phase 2R` to freeze product workflow, data-model, timer-backend, smart-cube, drill-session, solve-detail, stats, and match-logic contracts
- refresh the Model A handoff so later Model B work is selective subsystem implementation rather than an accidental whole-app recreation
- if later implementation proceeds, schedule only bounded subsystem Model B work in `Phase 5R`, not a full app-shell clean-room clone

View file

@ -143,6 +143,45 @@ Mandatory read rule before implementing any `0R-C` repo:
2. read `docs/REPO_LICENSE_TRACKING.md`
3. then apply the phase schedule in this document
## 2026-05-13 Packet 0R-D status
The fourth `Phase 0R` packet is now also closed as an evaluation packet:
- `Packet 0R-D` result doc:
- `docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`
That result doc is now the `governance and Model A authority` packet for all four `0R-D` repos.
Packet result:
- evaluated rows: `4`
- retained: `4`
- discarded: `0`
- newly proven live: `0`
Most important scheduling result:
- the restrictive clean-room candidate backlog is now closed as a `Phase 0R` evaluation class
- `cubing/alg.js` is retained as the focused algorithm-language clean-room lane
- `cubing/twisty.js` is retained as the focused embedded viewer/player clean-room lane
- `HactarCE/2x2x2x2-Scrambler` is retained as the narrow Melinda `2x2x2x2` clean-room lane
- `kash/cubedesk` is retained as the strategic timer/trainer/stats/smart-cube/match product-pattern clean-room lane
- all four rows remain `clean-room only`
- the scrubbed Model A handoffs in `C:\Workspaces\HyperTwist\clean-room-specs\` were refreshed and remain the only Model B implementation inputs for those rows
Combined `Phase 0R` packet status so far:
- packet-evaluated non-live rows: `53` of `65`
- remaining non-live rows still awaiting `Phase 0R` closure: `12`
- next packet: `0R-E`
Mandatory read rule before implementing any `0R-D` repo:
1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`
2. read `docs/REPO_LICENSE_TRACKING.md`
3. read the repo-specific scrubbed Model A handoff in `C:\Workspaces\HyperTwist\clean-room-specs\`
4. then apply the phase schedule in this document
Use it when a future model, operator, or reviewer needs one unambiguous answer to all of the following:
- what is already implemented right now
@ -238,7 +277,7 @@ HyperTwist should now proceed from the following rule:
- preserve the six live lanes
- do not reopen the `onionhoney/roux-trainers` lane as if it were an unresolved accidental donor import
- do not widen new donor-shaped implementation from the remaining unevaluated rows yet
- continue repo deep source integration evaluation for the remaining `22`
- continue repo deep source integration evaluation for the remaining `12`
- re-baseline implementation phases from that retained set
In practical terms:
@ -255,7 +294,7 @@ In practical terms:
Goal:
- repo-by-repo deep source evaluation for the not-yet-live rows retained after the live-state reset
- after `0R-A`, `0R-B`, and `0R-C`, `16` rows still remain to be closed
- after `0R-A`, `0R-B`, `0R-C`, and `0R-D`, `12` rows still remain to be closed
Required method from this point forward:
@ -511,7 +550,7 @@ Current packet result:
- the actual result was `retained with sharply bounded use`, not `broad donor promotion`
- next clean packet is `0R-D`
### Wave `4` — restrictive clean-room candidates still pending
### Wave `4` — restrictive clean-room candidates
These are the restrictive rows still retained for possible implementation after proper deep evaluation and refreshed Model A / Model B handling:
@ -531,6 +570,17 @@ Important note:
- `onionhoney/roux-trainers` is **not** in this pending set.
- it is already the landed clean-room restrictive lane.
Current packet result:
- `Packet 0R-D` is now closed for:
- `cubing/alg.js`
- `cubing/twisty.js`
- `HactarCE/2x2x2x2-Scrambler`
- `kash/cubedesk`
- none of those rows are newly proven live in checked Unreal surfaces
- the actual result was `retained clean-room only with refreshed Model A dossiers`, not `direct donor promotion`
- next clean packet is `0R-E`
### Wave `5` — benchmark, reserve, and discard candidates
These should be deep-evaluated specifically to answer whether they remain useful at all:

View file

@ -10,9 +10,9 @@ This board is the readable row-by-row companion to the v6.3 CSVs. It is derived
- Currently verified live in checked `UnrealHyperTwist` surfaces: `6` repos
- Live permissive lanes: `5`
- Live restrictive clean-room lanes: `1`
- Remaining rows requiring `Phase 0R` deep repo evaluation: `16`
- Remaining rows requiring `Phase 0R` deep repo evaluation: `12`
## 2026-05-12 packet overlay
## 2026-05-13 packet overlay
The baseline live-state counts above still do not change, but the permissive and boundary-sensitive `Phase 0R` evaluation backlogs are now closed.
@ -21,6 +21,7 @@ Read together with:
- [HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md:1)
- [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)
- [HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md:1)
- [HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md:1)
That overlay closes evaluation for:
@ -38,18 +39,20 @@ Important authority correction:
- `Packet 0R-A` is now the deep-source value-extraction and exclusion-rationale authority for its seven repos
- `Packet 0R-B` is now the deep-source value-extraction and exclusion-rationale authority for its thirty-six repos
- `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
- future implementation of those seven repos should start from `Packet 0R-A`, not from this board alone
- future implementation of those thirty-six repos should start from `Packet 0R-B`, not from this board alone
- future implementation of those six boundary-sensitive repos should start from `Packet 0R-C`, not from this board alone
- future implementation of those four restrictive repos should start from `Packet 0R-D`, then `REPO_LICENSE_TRACKING.md`, then the repo-specific scrubbed Model A handoff
- this board remains the readable row-state companion, not the place for full source-value extraction
Packet overlay result:
- all `43` non-live permissive rows have now been packet-evaluated
- all `6` boundary-sensitive rows have now been packet-evaluated
- none of those `49` packet-evaluated rows are newly proven live in checked Unreal surfaces
- the remaining `Phase 0R` backlog is now `16` rows:
- `4` restrictive clean-room candidates
- all `4` restrictive clean-room rows have now been packet-evaluated
- none of those `53` packet-evaluated rows are newly proven live in checked Unreal surfaces
- the remaining `Phase 0R` backlog is now `12` rows:
- `12` reference, benchmark, reserve, or discard candidates
## Count by live-state class
@ -92,9 +95,9 @@ Count: `1`
| --- | --- | --- | --- | --- | --- | --- |
| `onionhoney/roux-trainers` | `GPL-3.0` | Donor Bench | `repurpose` | `implemented_live_clean_room_verified` | `landed_clean_room_preserve` | Preserve the only currently verified restrictive clean-room landed lane, keep the Model A/Model B chain explicit, and do not treat it as an unresolved direct-donor import. |
## Permissive Candidates Pending Phase 0R
## Retained Permissive Candidates
These rows are retained, not currently proven live, and should go through deep source evaluation before direct permissive implementation or adapter work.
These rows are retained, not currently proven live, and have now cleared `Phase 0R` deep evaluation. They remain candidates for later direct permissive implementation or bounded adapter work.
Count: `43`
@ -144,9 +147,9 @@ Count: `43`
| `tentone/rubix-solver` | `MIT` | Locked Strategic Donor | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane. |
| `vivaansinghvi07/rubix-cube-solver` | `MIT` | Locked Parallel Foundation | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane. |
## Boundary-Sensitive Candidates Pending Phase 0R
## Retained Boundary-Sensitive Candidates
These rows are not currently proven live and need deeper license or packaging boundary decisions before implementation.
These rows are not currently proven live and have now cleared `Phase 0R` deep evaluation. They remain bounded adapter, sidecar, or notice-sensitive candidates rather than broad donor lanes.
Count: `6`
@ -159,18 +162,18 @@ Count: `6`
| `remotion-dev/remotion` | `Custom two-tier commercial license` | Donor Bench | `repurpose` | `selected_not_live_boundary_sensitive` | `phase0r_boundary_sensitive_eval_then_adapter_or_sidecar` | `Packet 0R-C` closed. Retain only as a commercially sensitive media-export and explainer sidecar/reference lane after an explicit package-level license decision. |
| `screenpipe/screenpipe` | `MIT OR Apache-2.0 core; enterprise-restricted ee/` | Donor Bench | `repurpose` | `selected_not_live_boundary_sensitive` | `phase0r_boundary_sensitive_eval_then_adapter_or_sidecar` | `Packet 0R-C` closed. Retain only as a bounded capture/history/replay, deterministic permissions, and vault donor with `ee/` excluded and permissive-core use kept narrowly allowlisted. |
## Restrictive Clean-Room Candidates Pending Phase 0R
## Retained Restrictive Clean-Room Candidates
These rows are retained restrictive lanes that still need deep evaluation, refreshed Model A dossiers, and later Model B clean-room implementation if kept.
These rows are retained restrictive lanes that have now cleared `Phase 0R` deep evaluation. They remain non-live and may only move forward through refreshed Model A dossiers and later Model B clean-room implementation.
Count: `4`
| Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step |
| --- | --- | --- | --- | --- | --- | --- |
| `cubing/alg.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. |
| `cubing/twisty.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. |
| `HactarCE/2x2x2x2-Scrambler` | `GPL-3.0` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. |
| `kash/cubedesk` | `GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved` | Locked Strategic Donor | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. |
| `cubing/alg.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only algorithm-language donor; later implementation must start from the scrubbed Model A dossier rather than donor source. |
| `cubing/twisty.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only embedded viewer/player donor; later implementation must start from the scrubbed Model A dossier rather than donor source. |
| `HactarCE/2x2x2x2-Scrambler` | `GPL-3.0` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only Melinda `2x2x2x2` donor; keep the copied-port lineage explicit and implement later only from the scrubbed Model A dossier. |
| `kash/cubedesk` | `GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved` | Locked Strategic Donor | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only timer/trainer/stats/smart-cube product-pattern donor; later work must stay bounded and start from the scrubbed Model A dossier. |
## Reference, Benchmark, Or Discard Candidates Pending Phase 0R

View file

@ -1,9 +1,9 @@
"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"
"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","Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane."
"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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Packet 0R-D closed. Retain as the clean-room-only algorithm-language donor; later implementation must start from the scrubbed Model A dossier rather than donor source."
"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","Packet 0R-D closed. Retain as the clean-room-only embedded viewer/player donor; later implementation must start from the scrubbed Model A dossier rather than donor source."
"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","Packet 0R-D closed. Retain as the clean-room-only Melinda 2x2x2x2 donor; keep the copied-port lineage explicit and implement later 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","Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane."
"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","Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane."
@ -15,7 +15,7 @@
"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","Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane."
"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","Preserve the landed permissive lane, keep notices and attribution visible, and revisit only for enhancement planning after Phase 0R closes for remaining rows."
"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","Preserve the landed permissive lane, keep notices and attribution visible, and revisit only for enhancement planning after Phase 0R closes for remaining rows."
"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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Packet 0R-D closed. Retain as the clean-room-only timer/trainer/stats/smart-cube product-pattern donor; later work must stay bounded and start 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","Deep source evaluate now; if retained, use as an attributed direct donor with preserved notices and provenance rather than as a clean-room lane."
"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","Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane."
"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","Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane."

1 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
2 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
3 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
4 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 Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. Packet 0R-D closed. Retain as the clean-room-only algorithm-language donor; later implementation must start from the scrubbed Model A dossier rather than donor source.
5 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 Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. Packet 0R-D closed. Retain as the clean-room-only embedded viewer/player donor; later implementation must start from the scrubbed Model A dossier rather than donor source.
6 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 Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. Packet 0R-D closed. Retain as the clean-room-only Melinda 2x2x2x2 donor; keep the copied-port lineage explicit and implement later only from the scrubbed Model A dossier.
7 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
8 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
9 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
15 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
16 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 Preserve the landed permissive lane, keep notices and attribution visible, and revisit only for enhancement planning after Phase 0R closes for remaining rows.
17 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 Preserve the landed permissive lane, keep notices and attribution visible, and revisit only for enhancement planning after Phase 0R closes for remaining rows.
18 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 Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use. Packet 0R-D closed. Retain as the clean-room-only timer/trainer/stats/smart-cube product-pattern donor; later work must stay bounded and start from the scrubbed Model A dossier.
19 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 Deep source evaluate now; if retained, use as an attributed direct donor with preserved notices and provenance rather than as a clean-room lane.
20 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
21 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View file

@ -1,4 +1,4 @@
"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"
"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
@ -44,8 +44,8 @@
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","Deep source evaluate now; if retained, prefer MPL-side dependency or adapter consumption and 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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Packet 0R-D closed. Retain as the clean-room-only algorithm-language donor; later implementation must start from the scrubbed Model A dossier rather than donor source."
"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","Packet 0R-D closed. Retain as the clean-room-only embedded viewer/player donor; later implementation must start from the scrubbed Model A dossier rather than donor source."
"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
@ -81,7 +81,7 @@
6) Best merge partners and exact coupling seam
7) Reasons to promote / retain / demote
8) Confidence change after source audit
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
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","Packet 0R-D closed. Retain as the clean-room-only timer/trainer/stats/smart-cube product-pattern donor; later work must stay bounded and start 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
@ -238,7 +238,7 @@
7) Reasons to promote / retain / demote
8) Confidence change after source audit
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","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","Deep source evaluate now; if retained, keep ee/ excluded and prefer bounded donor or sidecar seams rather than broad shell inheritance."
"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","Deep source evaluate now; if retained, refresh or create the Model A dossier and schedule Model B clean-room implementation instead of direct donor use."
"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","Packet 0R-D closed. Retain as the clean-room-only Melinda 2x2x2x2 donor; keep the copied-port lineage explicit and implement later 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

1 repo primary_url project phase_g_bucket stack_layer audit_tier tier_queue_order global_order wave_number portfolio_priority_score execution_priority_score_v3 current_confidence modification_scope_detail_v3 recommended_action_v2 repurposing_potential_v2 audit_goal inspect_emphasis source_code_audit_targets source_inspection_questions integration_realization_detail consolidation_detail repurpose_detail merger_partner_1 merger_type_1 merger_rationale_1 merger_partner_2 merger_type_2 merger_rationale_2 merger_partner_3 merger_type_3 merger_rationale_3 cross_project_transfer_targets cross_project_transfer_rationale reclassify_up_if reclassify_down_if deliverable_expected session_note_template recommended_context_packet phase_g_master_list_rationale phase_g_bucket_reason coding_model_instruction_v3 source_audit_packet_id cluster_tag _repo_norm v5_runtime_project v5_scriptorium_override_status v5_scriptorium_bucket v5_scriptorium_stack_layer v5_scriptorium_current_reality_status v5_scriptorium_supersedes_prior_assessment v5_source_of_truth v6_license_annotation v6_license_annotation_status v6_license_annotation_source v6_supplemental_intake_present v6_supplemental_source_groups v6_supplemental_source_sections v6_supplemental_source_files v6_reference_material_position v6_kali_agent_access_relevance v6_branch_seed_prompt_included v6_branch_seed_scope v6_intake_wave v6_notes v6_source_of_truth project_rank_num tier_rank_num priority_num copyleft_relevance_v6_1 copyleft_strategy_v6_1 copyleft_rationale_v6_1 preferred_boundary_model_v6_1 open_compliance_if_used_as_is_v6_1 reverse_engineer_if_proprietary_core_needed_v6_1 copyleft_strategy_confidence_v6_1 copyleft_manual_review_trigger_v6_1 as_is_incorporation_sensible_v6_1 v6_2_sre_layer v6_2_sre_stratum v6_2_sre_role v6_2_sre_family v6_2_related_kali_package v6_2_related_upstream_repo v6_2_kali_package_suffices_for_tool_execution v6_2_upstream_repo_preferred_for_deep_eval v6_2_index_page_followup_useful v6_2_index_page_followup_reason v6_2_sre_notes v6_2_dnspy_ilspy_relevance v6_3_source_of_truth v6_3_merge_note v6_3_live_state_2026_05_11 v6_3_reset_lane_2026_05_11 v6_3_reset_next_step_2026_05_11
2 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 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
3 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 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
4 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 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
44 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
45 KhronosGroup/glTF-Sample-Viewer https://github.com/KhronosGroup/glTF-Sample-Viewer HyperTwist Donor Bench Browser asset validation and viewer surface P3 medium Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer. repurpose moderate modification 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
46 google/model-viewer https://github.com/google/model-viewer HyperTwist Donor Bench Browser 3D presentation and inspection surface P2 medium Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project. repurpose moderate modification Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces. custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces. Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support. Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows. Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack. Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction. HT_browser_surface_0005 HT_browser_surface google/model-viewer Apache-2.0 known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor. Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell. Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high notice-file-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase0r_permissive_eval_then_implement Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
47 mrdoob/three.js https://github.com/mrdoob/three.js HyperTwist Donor Bench Browser 3D substrate P2 medium Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction. repurpose moderate modification Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces. renderer, scene, camera, math core, loaders, WebXR manager, addons, editor Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell. Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell. Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine. Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack. Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual. HT_browser_surface_0006 HT_browser_surface mrdoob/three.js MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation. Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase0r_permissive_eval_then_implement Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
48 pmndrs/postprocessing https://github.com/pmndrs/postprocessing HyperTwist Merge Bench Browser post-processing substrate P3 medium Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package. integrate moderate modification 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
49 pmndrs/react-three-fiber https://github.com/pmndrs/react-three-fiber HyperTwist Donor Bench Browser React 3D substrate P2 medium Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer. repurpose moderate modification Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes. Canvas, createRoot, reconciler runtime, event system, hooks, native path Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points. Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path. Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer. Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack. Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference. HT_browser_surface_0008 HT_browser_surface pmndrs/react-three-fiber MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate. Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase0r_permissive_eval_then_implement Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
50 pmndrs/drei https://github.com/pmndrs/drei HyperTwist Merge Bench Browser 3D helper and abstraction layer P3 medium Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl. integrate moderate modification 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 Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
51 pmndrs/xr https://github.com/pmndrs/xr HyperTwist Donor Bench Browser XR and immersive UI substrate P2 medium Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack. repurpose moderate modification Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces. XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages. Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior. Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions. Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces. Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. Capability inventory + salvage targets + donor-tier verdict 1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership. Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack. Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual. HT_browser_surface_0010 HT_browser_surface pmndrs/xr MIT known_from_reference_material uploaded_reference_docs v6_unified_source_of_truth_pack permissive_or_noncopyleft_known direct_incorporation_ok The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor. Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack. Typically preserve notices, attribution, and license text where required. Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. high standard-notice-review yes v6.3_markdown_backfill Backfilled from canonized Markdown dossier pass on 2026-04-24. selected_not_live_permissive_candidate phase0r_permissive_eval_then_implement Deep source evaluate now; if retained, schedule direct permissive implementation or bounded adapter work without opening a new clean-room lane.
81
82
83
84
85
86
87
238
239
240
241
242
243
244

View file

@ -98,8 +98,9 @@ Current `Phase 0R` packet status:
- `0R-A` is closed
- `0R-B` is closed
- `0R-C` is closed
- non-live rows already packet-evaluated: `49`
- non-live rows still awaiting packet evaluation: `16`
- `0R-D` is closed
- non-live rows already packet-evaluated: `53`
- non-live rows still awaiting packet evaluation: `12`
Read together with: