|
|
|
|
@ -136,7 +136,7 @@
|
|
|
|
|
"MathewKJ2048/Rubiks-cube-simulator","https://github.com/MathewKJ2048/Rubiks-cube-simulator","HyperTwist","Reserve Bench","Clean-room simulator benchmark","P3","7469","9224","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Capture the lightweight simulator behaviors worth preserving from MathewKJ2048/Rubiks-cube-simulator through a scrubbed clean-room spec.","Command grammar, move-history logging, beginner-solver flow, and timed step playback as clean-room benchmark material.","Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.","Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?","Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.","Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.","Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in MathewKJ2048/Rubiks-cube-simulator
|
|
|
|
|
2) What must stay benchmark-only or clean-room-only
|
|
|
|
|
3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors.","GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material.","Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.","HT_training_clean_room_0004","HT_training_clean_room","mathewkj2048/rubiks-cube-simulator","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.","Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.","high","gpl-clean-room-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks."
|
|
|
|
|
"NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","Donor Bench","XR pedagogy and code-to-scene representation donor","P2","7470","9225","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Determine whether NuiLab/code-vr should stay donor/merge-tier for HyperTwist, be promoted, or be demoted; identify concrete salvageable modules and best merge path.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
|
|
|
|
|
"NuiLab/code-vr","https://github.com/NuiLab/code-vr","HyperTwist","Donor Bench","Retained symbolic-to-spatial XR pedagogy experiment","P2","7470","9225","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","repurpose","moderate modification","Confirm the retained symbolic-to-spatial pedagogy thesis for NuiLab/code-vr in HyperTwist: what exact narrow logic survives, how it compares against the landed knowledge and browser-spatial/XR stack, and whether any later owner-gap reopening is actually justified.","puzzle model, learning flow, UX loops, data schema, replay/export, plugin/hooks","Inspect symbolic-to-spatial conversion, parse/export/runtime separation, language-aware teaching-sidecar behavior, and bounded pedagogy-experiment seams against the landed knowledge and browser-spatial/XR stack.","Inspect AST or graph-to-scene conversion; parse/export/runtime separation; language-server sidecar boundaries; symbolic-to-spatial pedagogy value; reasons it should stay subordinate to the knowledge shell and browser-spatial/XR owners.","Do not integrate as a practical XR runtime or training subsystem. Retain only as a narrow symbolic-to-spatial pedagogy experiment behind the first-party knowledge shell and landed browser-spatial/XR owners. Any later use should surface abstract-structure spatial teaching or parse/export/runtime experiments without widening the VR runtime shell.","Keep subordinate to the first-party knowledge shell and landed browser-spatial/XR owners. Use only for bounded pedagogy experiments; do not form a separate XR or game-runtime silo.","Repurpose here means: optional code-structure-to-space pedagogy, parse/export/runtime experiment logic, or teaching-sidecar patterns only, not a practical XR runtime or trainer foundation.","kkoomen/qbr","foundation + perception donor","Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.","vivaansinghvi07/rubix-cube-solver","perception + replay donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","cubing/cubing.js","state/render backend","Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.","VectorShell | ScriptoriumAI","VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Capability inventory + salvage targets + promotion/demotion verdict","1) Confirmed visible capabilities
|
|
|
|
|
2) Hidden capabilities found only in source
|
|
|
|
|
3) Best salvageable modules/files/packages
|
|
|
|
|
4) Integration path into target project
|
|
|
|
|
@ -144,7 +144,7 @@
|
|
|
|
|
6) Best merge partners and exact coupling seam
|
|
|
|
|
7) Reasons to promote / retain / demote
|
|
|
|
|
8) Confidence change after source audit
|
|
|
|
|
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.","MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.","HT_cube_vision_0007","HT_cube_vision","nuilab/code-vr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
|
|
|
|
|
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.","MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.","Audit NuiLab/code-vr only as a retained symbolic-to-spatial pedagogy experiment for HyperTwist. Inspect AST or graph-to-scene conversion, parse/export/runtime separation, and language-aware teaching-sidecar behavior. Do not reopen it as a practical XR runtime, gameplay shell, or training foundation owner. Compare only against the first-party knowledge shell and landed browser-spatial/XR stack and report whether any narrower pedagogy gap remains.","HT_cube_vision_0007","HT_cube_vision","nuilab/code-vr","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.","Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.","Preserve MIT notices and attribution where required.","Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.","high","below-core-mit-donor","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.","selected_not_live_permissive_candidate","phase2rc_symbolic_xr_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as a symbolic-to-spatial pedagogy experiment lane beneath the first-party knowledge shell and landed browser-spatial/XR owners; no default widening packet is open."
|
|
|
|
|
"ShellPuppy/RCube","https://github.com/ShellPuppy/RCube","HyperTwist","Reserve Bench","Large-N solver benchmark","P3","7471","9226","51.0","118.0","133.0","medium","Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","future candidate","architecture only","Document the large-N orientation and stage-framing ideas that justify retaining RCube only as a benchmark row.","Large-cube orientation logic, stage framing, and solver behavior as benchmark material.","Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.","Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.","Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.","tao-yu/Alg-Trainer","base + donor swarm","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","poliva/cubedex","specialized training UX donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Lykos/cube_trainer","sampling/analytics donor","Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.","Reference only","Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.","Upgrade if source reveals clean modular architecture, reusable core abstractions, strong adapters/plugins, robust tests, and direct fit to a locked stack.","Demote if reusable value is mostly superficial, undocumented complexity overwhelms salvage value, or higher-ranked repos clearly dominate the same role.","Benchmark note + salvage list + clear do-not-incorporate boundary.","1) What specific benchmark value remains in ShellPuppy/RCube
|
|
|
|
|
2) What must stay benchmark-only or clean-room-only
|
|
|
|
|
3) Acceptance-test, oracle, or behavior targets worth preserving","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.","GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.","HT_solver_oracles_0001","HT_solver_oracles","shellpuppy/rcube","","","","","","","Original global P0-P3 source audit retained","GPL-3.0","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","2","3","118.0","mixed_or_boundary_sensitive_known","pattern_only_preferred","The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.","Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.","Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.","high","gpl-large-n-benchmark","no","","","","","","","","","","","","","v6.3_final_source_of_truth","Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.","not_live_reference_or_discard_candidate","phase0r_reference_benchmark_or_discard_eval","Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor."
|
|
|
|
|
@ -290,8 +290,8 @@
|
|
|
|
|
"screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","Donor Bench","Support-plane capture, history, and replay sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0001","HT_support_sidecars","screenpipe/screenpipe","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-E closed. Preserve as the landed first-party capture/history/replay, deterministic-permission, persistence, vault-lifecycle, timeline-review, and explicit permissive-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-E, then REPO_LICENSE_TRACKING.md."
|
|
|
|
|
"remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","Donor Bench","Commercially licensed media-export and explainer sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.","player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0002","HT_support_sidecars","remotion-dev/remotion","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-F closed. Preserve as the landed first-party media-export, embedded playback, parser, explainer-studio, and package-split commercial-compliance lane; start future widening from the live-lane audit, then Phase 4R-F, then REPO_LICENSE_TRACKING.md; keep the explicit company-license and package-split boundary visible."
|
|
|
|
|
"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","Browser 2D render substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether ecomfe/zrender should remain active in the Browser 2D render substrate lane and which seams should stay bounded.","scene graph, canvas and SVG painters, event handling, animation primitives","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0001","HT_browser_support","ecomfe/zrender","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-C closed for the anchor. Retain as the lower-level subordinate 2D substrate beneath the landed apache/echarts lane; do not treat it as separately live."
|
|
|
|
|
"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Browser WebGL substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pissang/claygl should remain active in the Browser WebGL substrate lane and which seams should stay bounded.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
|
|
|
|
|
"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Browser viewer and editor sidecar","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pissang/clay-viewer should remain active in the Browser viewer and editor sidecar lane and which seams should stay bounded.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R."
|
|
|
|
|
"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Retained alternative browser 3D comparison substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm the retained browser 3D comparison thesis for pissang/claygl in HyperTwist: what exact narrow infrastructure value survives, how it compares against the landed browser spatial stack, and whether any later sidecar-gap reopening is actually justified.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect renderer and scene infrastructure, camera and control patterns, picking and compositor behavior, and bounded browser-side comparison value against the landed browser spatial stack.","Inspect renderer, scene, camera, control, picking, compositor, and App3D patterns; sidecar-only value; reasons it should stay subordinate to the landed browser spatial stack.","Do not integrate as a primary browser spatial runtime. Retain only as an optional comparison substrate beneath the landed three.js, react-three-fiber, and xr stack. Any later use should surface bounded lower-level browser-side 3D control or explainer sidecars only if a real gap remains.","Keep subordinate to the landed browser spatial stack and do not form a separate WebGL runtime silo. Use only for optional comparison or bounded sidecar support.","Repurpose here means: optional lower-level browser 3D comparison or explainer substrate only, not a runtime foundation.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl only as a retained alternative browser 3D comparison substrate for HyperTwist. Inspect renderer, scene, camera, control, picking, compositor, and App3D patterns. Do not reopen it as a primary browser spatial runtime or puzzle-renderer owner. Compare only against the landed three.js, react-three-fiber, and xr stack and report whether any narrower sidecar gap remains.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser 3D comparison lane subordinate to the landed three.js, react-three-fiber, and xr stack; keep 3R-G deferred unless a real sidecar gap remains."
|
|
|
|
|
"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Retained alternative browser viewer/editor comparison sidecar","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm the retained browser viewer/editor comparison thesis for pissang/clay-viewer in HyperTwist: what exact narrow sidecar value survives, how it compares against the landed browser viewer and spatial stack, and whether any later sidecar-gap reopening is actually justified.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect viewer shell, hotspot and animation-preview behavior, environment or lighting presets, compact inspection surfaces, and bounded browser comparison value against google/model-viewer and the landed browser spatial stack.","Inspect hotspot, camera, animation-preview, environment or post-effect preset, and inspection-shell patterns; sidecar-only value; reasons it should stay subordinate to google/model-viewer and the landed browser spatial stack.","Do not integrate as a primary browser viewer or editor runtime. Retain only as an optional comparison sidecar behind the landed google/model-viewer and browser spatial owners. Any later use should surface bounded preview, inspection, or explainer behaviors only if a real gap remains.","Keep subordinate to google/model-viewer and the landed browser spatial stack. Use only for optional comparison or bounded preview or editor sidecars.","Repurpose here means: optional viewer/editor comparison, preview, or inspection sidecar only, not a runtime foundation.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer only as a retained alternative browser viewer/editor comparison sidecar for HyperTwist. Inspect hotspot, animation-preview, environment or post-effect preset, and compact inspection-shell behavior. Do not reopen it as a primary browser viewer, editor, gameplay, or runtime owner. Compare only against the landed google/model-viewer and browser spatial stack and report whether any narrower sidecar gap remains.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser viewer/editor comparison lane subordinate to the landed google/model-viewer and browser spatial stack; keep 3R-G deferred unless a real sidecar gap remains."
|
|
|
|
|
"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","Browser asset renderer substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether KhronosGroup/glTF-Sample-Renderer should remain active in the Browser asset renderer substrate lane and which seams should stay bounded.","GltfView, GltfState, resource loader, user camera, renderer core","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0004","HT_browser_support","khronosgroup/gltf-sample-renderer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","Browser asset editor and inspection surface","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/space-opera should remain active in the Browser asset editor and inspection surface lane and which seams should stay bounded.","editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0005","HT_browser_support","google/model-viewer/packages/space-opera","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","Browser fidelity QA harness","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/render-fidelity-tools should remain active in the Browser fidelity QA harness lane and which seams should stay bounded.","golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0006","HT_browser_support","google/model-viewer/packages/render-fidelity-tools","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase0r_permissive_eval_then_implement","Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live."
|
|
|
|
|
|
axiomlogicnexus