| 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 |
| 46 |
google/model-viewer |
https://github.com/google/model-viewer |
HyperTwist |
Donor Bench |
Browser 3D presentation and inspection surface |
P2 |
|
|
|
|
|
medium |
Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project. |
repurpose |
moderate modification |
Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces. |
custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools |
Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces. |
Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support. |
Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows. |
|
Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime. |
Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack. |
Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction. |
HT_browser_surface_0005 |
HT_browser_surface |
google/model-viewer |
|
|
|
|
|
|
|
Apache-2.0 |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor. |
Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell. |
Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
notice-file-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
implemented_live_permissive |
landed_permissive_preserve |
Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md. |
| 47 |
mrdoob/three.js |
https://github.com/mrdoob/three.js |
HyperTwist |
Donor Bench |
Browser 3D substrate |
P2 |
|
|
|
|
|
medium |
Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction. |
repurpose |
moderate modification |
Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces. |
renderer, scene, camera, math core, loaders, WebXR manager, addons, editor |
Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell. |
Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell. |
Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine. |
|
Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation. |
Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack. |
Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual. |
HT_browser_surface_0006 |
HT_browser_surface |
mrdoob/three.js |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation. |
Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
implemented_live_permissive |
landed_permissive_preserve |
Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md. |
| 48 |
pmndrs/postprocessing |
https://github.com/pmndrs/postprocessing |
HyperTwist |
Merge Bench |
Browser post-processing substrate |
P3 |
|
|
|
|
|
medium |
Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package. |
integrate |
moderate modification |
Determine whether postprocessing should remain the bounded browser effect-composer substrate beneath the companion stack. |
EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions |
Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js. |
Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions. |
Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces. |
|
Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane. |
Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers. |
Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference. |
HT_browser_surface_0007 |
HT_browser_surface |
pmndrs/postprocessing |
|
|
|
|
|
|
|
Zlib |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency. |
Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate browser post-effect substrate beneath the landed browser spatial owner trio; do not treat it as separately live. |
| 49 |
pmndrs/react-three-fiber |
https://github.com/pmndrs/react-three-fiber |
HyperTwist |
Donor Bench |
Browser React 3D substrate |
P2 |
|
|
|
|
|
medium |
Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer. |
repurpose |
moderate modification |
Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes. |
Canvas, createRoot, reconciler runtime, event system, hooks, native path |
Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points. |
Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path. |
Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer. |
|
Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation. |
Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack. |
Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference. |
HT_browser_surface_0008 |
HT_browser_surface |
pmndrs/react-three-fiber |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate. |
Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
implemented_live_permissive |
landed_permissive_preserve |
Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md. |
| 50 |
pmndrs/drei |
https://github.com/pmndrs/drei |
HyperTwist |
Merge Bench |
Browser 3D helper and abstraction layer |
P3 |
|
|
|
|
|
medium |
Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl. |
integrate |
moderate modification |
Determine which drei helpers should remain active merge candidates for browser companion surfaces and which should be ignored as generic convenience. |
Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior |
Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers. |
Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities. |
Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl. |
|
Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation. |
Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions. |
Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl. |
HT_browser_surface_0009 |
HT_browser_surface |
pmndrs/drei |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber. |
Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed browser spatial support stack; do not treat it as separately live. |
| 51 |
pmndrs/xr |
https://github.com/pmndrs/xr |
HyperTwist |
Donor Bench |
Browser XR and immersive UI substrate |
P2 |
|
|
|
|
|
medium |
Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack. |
repurpose |
moderate modification |
Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces. |
XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer |
Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages. |
Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior. |
Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions. |
|
Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership. |
Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack. |
Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual. |
HT_browser_surface_0010 |
HT_browser_surface |
pmndrs/xr |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor. |
Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
implemented_live_permissive |
landed_permissive_preserve |
Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md. |
| 52 |
pmndrs/uikit |
https://github.com/pmndrs/uikit |
HyperTwist |
Donor Bench |
Browser spatial UI surface |
P2 |
|
|
|
|
|
medium |
Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package. |
repurpose |
moderate modification |
Determine whether pmndrs/uikit should remain the default browser spatial UI donor for HyperTwist companion surfaces. |
flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior |
Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code. |
Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior. |
Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design. |
|
Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes. |
Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster. |
pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership. |
Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack. |
Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual. |
HT_browser_surface_0011 |
HT_browser_surface |
pmndrs/uikit |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
|
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor. |
Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-24. |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate browser spatial UI layer beside the landed pmndrs/xr lane; do not treat it as separately live. |
| 54 |
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. |
| 55 |
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. |
| 56 |
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. |
| 57 |
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. |
| 58 |
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. |
| 59 |
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. |
| 60 |
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. |
| 61 |
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. |
| 63 |
google/model-viewer/packages/modelviewer.dev |
https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev |
HyperTwist |
Merge Bench |
Browser docs and demo surface |
P4 |
|
|
|
|
|
medium |
Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly. |
integrate |
moderate modification |
Determine whether google/model-viewer/packages/modelviewer.dev should remain active in the Browser docs and demo surface lane and which seams should stay bounded. |
live docs generation, snippet-to-demo coupling, sidebar and HTML generation |
Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities. |
the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. |
Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime. |
Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane. |
Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0008 |
HT_browser_support |
google/model-viewer/packages/modelviewer.dev |
|
|
|
|
|
|
|
Apache-2.0 |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor. |
Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces. |
Preserve LICENSE and NOTICE materials where required. |
Usually unnecessary unless later product-shaping concerns make selective replacement attractive. |
high |
notice-file-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner. |
| 64 |
google/model-viewer/packages/shared-assets |
https://github.com/google/model-viewer/tree/main/packages/shared-assets |
HyperTwist |
Donor Bench |
Boundary-sensitive sample-asset and test-fixture pack |
P3 |
|
|
|
|
|
medium |
Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly. |
repurpose |
architecture only |
Determine whether google/model-viewer/packages/shared-assets should remain active in the Browser sample-asset and fixture pack lane and which seams should stay bounded. |
asset provenance, attribution terms, environment fixtures, sample models, fetch script behavior |
Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms. |
the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. |
Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source. |
Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture. |
Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0009 |
HT_browser_support |
google/model-viewer/packages/shared-assets |
|
|
|
|
|
|
|
Apache-2.0 container; mixed per-asset terms |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
mixed_or_boundary_sensitive_known |
bounded_sidecar_or_selective_reimplementation |
The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source. |
Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms. |
Preserve container notices and review each selected asset attribution or usage condition separately before shipping. |
Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement. |
high |
mixed-asset-whitelist-review |
no |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status. |
implemented_live_boundary_sensitive |
landed_boundary_sensitive_preserve |
Phase 4R-C closed. Preserve as the landed first-party shared-assets allowlist, provenance-boundary, and fixture-refresh lane; keep per-asset shipping allowlists plus review-only and local-only boundaries explicit. |
| 65 |
pmndrs/react-postprocessing |
https://github.com/pmndrs/react-postprocessing |
HyperTwist |
Merge Bench |
Browser React effect-wrapper layer |
P4 |
|
|
|
|
|
medium |
Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly. |
integrate |
moderate modification |
Determine whether pmndrs/react-postprocessing should remain active in the Browser React effect-wrapper layer lane and which seams should stay bounded. |
React EffectComposer orchestration, selection model, wrapper ergonomics |
Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer. |
the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. |
Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime. |
Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane. |
Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0010 |
HT_browser_support |
pmndrs/react-postprocessing |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing. |
Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless later product-shaping concerns make selective replacement attractive. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate React wrapper above pmndrs/postprocessing inside the landed browser spatial support stack; do not treat it as separately live. |
| 66 |
pmndrs/three-stdlib |
https://github.com/pmndrs/three-stdlib |
HyperTwist |
Merge Bench |
Browser 3D utility substrate |
P4 |
|
|
|
|
|
medium |
Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly. |
integrate |
moderate modification |
Determine whether pmndrs/three-stdlib should remain active in the Browser 3D utility substrate lane and which seams should stay bounded. |
controls, loaders, WebXR helpers, post-processing helpers, utility exports |
Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules. |
the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. |
Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime. |
Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. |
Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0011 |
HT_browser_support |
pmndrs/three-stdlib |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes. |
Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless later product-shaping concerns make selective replacement attractive. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate shared utility shelf beneath the landed browser spatial owner trio; do not treat it as separately live. |
| 67 |
pmndrs/maath |
https://github.com/pmndrs/maath |
HyperTwist |
Merge Bench |
Browser math-helper substrate |
P4 |
|
|
|
|
|
medium |
Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly. |
integrate |
moderate modification |
Determine whether pmndrs/maath should remain active in the Browser math-helper substrate lane and which seams should stay bounded. |
easing and damp functions, random helpers, geometry utilities |
Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules. |
the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. |
Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime. |
Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. |
Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0012 |
HT_browser_support |
pmndrs/maath |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate. |
Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless later product-shaping concerns make selective replacement attractive. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate math-helper layer inside the landed browser spatial support stack; do not treat it as separately live. |
| 68 |
pmndrs/zustand |
https://github.com/pmndrs/zustand |
HyperTwist |
Donor Bench |
Browser state-management substrate |
P3 |
|
|
|
|
|
medium |
Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture. |
repurpose |
moderate modification |
Determine whether pmndrs/zustand should remain active in the Browser state-management substrate lane and which seams should stay bounded. |
vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware |
Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules. |
the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. |
Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime. |
Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. |
Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0013 |
HT_browser_support |
pmndrs/zustand |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate. |
Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless later product-shaping concerns make selective replacement attractive. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate browser-side state substrate inside the landed browser spatial support stack; do not treat it as separately live. |
| 69 |
pmndrs/leva |
https://github.com/pmndrs/leva |
HyperTwist |
Merge Bench |
Browser control-panel and parameter UI layer |
P4 |
|
|
|
|
|
medium |
Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly. |
integrate |
moderate modification |
Determine whether pmndrs/leva should remain active in the Browser control-panel and parameter UI layer lane and which seams should stay bounded. |
control store, schema parsing, useControls, plugin system, headless mode |
Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs. |
the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. |
Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries. |
|
Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack. |
|
|
|
|
|
|
|
|
|
|
|
Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces. |
Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos. |
Capability inventory + salvage targets + donor-tier verdict |
1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes. |
Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster. |
pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime. |
Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. |
Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core. |
HT_browser_support_0014 |
HT_browser_support |
pmndrs/leva |
|
|
|
|
|
|
|
MIT |
known_from_reference_material |
uploaded_reference_docs |
|
|
|
|
|
|
|
|
|
Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md |
v6_unified_source_of_truth_pack |
|
|
|
permissive_or_noncopyleft_known |
direct_incorporation_ok |
The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor. |
Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI. |
Typically preserve notices, attribution, and license text where required. |
Usually unnecessary unless later product-shaping concerns make selective replacement attractive. |
high |
standard-notice-review |
yes |
|
|
|
|
|
|
|
|
|
|
|
|
v6.3_markdown_backfill |
Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md |
selected_not_live_permissive_candidate |
phase0r_permissive_eval_then_implement |
Phase 3R-F closed for the owner trio. Retain as the subordinate authoring and debug control sidecar inside the landed browser spatial support stack; do not treat it as separately live. |
|
axiomlogicnexus